openapi
openapi copied to clipboard
stripe
An OpenAPI specification for the Stripe API.
It would be great if Stripe could provide language support for Rust. The unofficial Rust stripe client libraries are incomplete. I've tried generating a rust client from the openapi specification,...
This extension seems to have been used before to extend the OpenAPI v2 format, but it is not used anymore as OpenAPI v3 offers a mechanism for polymorphic objects.
Both "public" and "internal" OpenAPI specs seem to be missing the documented [`three_d_secure`](https://stripe.com/docs/api/payment_intents/confirm#confirm_payment_intent-payment_method_options-card-three_d_secure) property for the schema `payment_intent_payment_method_options_card`. Is there a plan for adding it? Or am I missing something?
Along the lines of my previous requests, it'd be good to have the ranges of values for various definitions. For example: ```yml tax_percent: description: A non-negative decimal (with at most...
It would be nice if `period` was split up into two types, one might be called `period` and the the other `closed_period`. This would allow us to differentiate between :...
In OpenAPI 3.0 there is already a "callbacks" parameter describing the webhooks triggered by an API call. In the new OpenAPI 3.1 there is also a webhooks root description for...
Both the Customer and Subscription schema have a `metadata` property: ```json "metadata": { "additionalProperties": { "maxLength": 500, "type": "string" }, "description": "...", "type": "object" }, ``` But the Subscription lists...
When using the [upcoming invoice](https://stripe.com/docs/api/invoices/upcoming) endpoint, the response represents an invoice that doesn't exist yet, and does not have an `id`. > Note that when you are viewing an upcoming...
Hey There! I have a few questions about the OpenAPI spec: 1. I noticed the `Create Charge` endpoint (`POST /v1/charges`) in the spec had an extra parameter defined in the...
Hi there! I'm wrapping my head around x-expandableFields and x-expansionResources. I thought I got this right but there's a case that confuses me. Let's take invoice.subscription. it's not an expandableFIeld...
