openapi
openapi copied to clipboard
stripe
An OpenAPI specification for the Stripe API.
Hi, in at least the v2 spec, in JSON Pointer speak this: ``` /paths/~1v1~1accounts/post/parameters/0/schema/properties/legal_entity/additional_owners/properties ``` has string keys of "0", "1", ... and each of those values is identical: ```...
The [charge.source](https://github.com/stripe/openapi/blob/master/openapi/spec2.json#L2103) property is {"$ref": "#/definitions/account_debit_account"}, should that be some other type, e.g. `card` or a oneOf type?
The following lines: https://github.com/stripe/openapi/blob/107afb558a844c516f562946602eeab86aae40f9/openapi/fixtures3.json#L531 https://github.com/stripe/openapi/blob/107afb558a844c516f562946602eeab86aae40f9/openapi/fixtures3.json#L535 ...show that we're returning customer data for an event which has an `object: "invoice"`, when it should be `object: "customer"`. This is causing an unexpected...
The PII token types appear to be missing from the `token` object. It looks like the `type` is missing the possibility of there being a `pii` type. The online API...
I noticed that the `plan` schema appears to be missing a `trial_period_days`, and while the Stripe documentation does not reference this key, it does appear to exist in the example...
Spotted a typo, not sure if this is the right place to open a PR — let me know if there's somewhere else I should report/fix this. Thanks! https://stripe.com/docs/api/payment_methods/object#payment_method_object-card-three_d_secure_usage
https://stripe.com/docs/sources/sepa-debit Source creation for SEPA Direct Debit payments may return any of the following errors: invalid_owner_name invalid_bank_account_iban processing_error payment_method_not_available seems loss invalid_owner_name\invalid_bank_account_iban will cause error in rust https://github.com/arlyon/async-stripe/issues/479 ### Describe...
[this guy](https://stripe.com/docs/api/terminal/readers/list#list_terminal_reader-serial_number) I noticed this when using `stripe-node` - not sure how the openapi spec gets updated as it all seems to be done by a bot? Is there a...
According to this documentation, https://stripe.com/docs/api/subscriptions/create When doing a `POST` to `/v1/subscriptions` the `customer` and `items` parameters are both required. But in `spec3.json` it merely specifies, ``` "required": [ "customer" ],...
Similar vein to https://github.com/stripe/openapi/issues/72 - there is now a `LICENSE` file in the repo which is great, but if it's not too much hassle it would be nice to include...
