Stripe publishes its OpenAPI specifications in the stripe/openapi GitHub repository. Here, “3.0” refers to the OpenAPI Specification standard—not to a Stripe API version. For a new integration that needs generally available (GA) coverage, Stripe recommends the repository’s /latest/ collection.
Where to find Stripe’s OpenAPI specification
Open Stripe’s stripe/openapi repository and choose the specification files for your use case. Stripe describes the repository as containing OpenAPI specifications for its API and says they can be used to generate SDKs or client libraries.
The repository separates files by release status and coverage. The directory names matter: they indicate which endpoint sets and features a specification represents.
What “version 3.0” means
OpenAPI 3.0 is a version of the API-description standard. It is not Stripe API version 3.0. The OpenAPI Initiative lists standard releases including 3.0.0 through 3.0.4, as well as 3.1 and 3.2. Its schema catalogue associates schemas with a minor version and revision date; within a minor release, the latest schema iteration is the most correct for that line. See the OpenAPI Specification versions.
Recommended Free Tools
#1 Best Overall
Stripe versions its API separately. In an announcement dated October 1, 2024, Stripe described a system of twice-yearly major API releases and monthly compatible feature releases. Major releases use plant names; monthly updates retain the current major release’s name. Acacia was the first major API release under that system. These Stripe API release labels should not be confused with OpenAPI’s 3.x standard versions. Read Stripe’s API versioning announcement.
Which Stripe specification directory should you use?
| Directory | Coverage and status | Best fit |
|---|---|---|
/latest/ |
Stripe’s recommended GA collection; combines v1 and v2 endpoints and events in a single file. | New integrations that need generally available v1 and v2 coverage. |
/preview/ |
Contains public preview API features, which are distinct from GA functionality. | When you specifically need early access to a public preview feature and can account for its preview status. |
/openapi/ |
Legacy v1-only layout. Stripe says it remains updated with each release. | Existing workflows built around the older v1-only layout; migration is not required solely because the layout is described as legacy. |
Stripe recommends /latest/ for new projects seeking complete coverage. Choose preview only for a reason: its contents are not the same as generally available functionality. The older /openapi/ layout continues to be updated, so “legacy” does not mean abandoned. These directory descriptions are in the repository README.
Public spec files versus SDK-specific files
For most uses, start with the public spec3 JSON or YAML files. The SDK-specific files include additional annotations and may include deprecated endpoints and pre-release features to support Stripe library generation. They are not simply interchangeable with the public specifications.
Do not assume that a Stripe file will work unchanged with every OpenAPI generator. Stripe says its specifications are produced with a custom closed-source generator and are not explicitly targeted at openapi-generator. If you are generating a client with a different tool, check the output and any tool-specific adjustments rather than treating the spec3 name as a compatibility guarantee. Stripe explains these distinctions in its repository documentation.
How to check the current Stripe spec release
Repository release labels change over time, so verify them in GitHub when selecting or pinning a file. At the time reflected by the repository release information in this article’s date context, its latest displayed tag was v2524; the SDK specification was labeled 2026-09-30.endive, and preview variants were labeled 2026-09-30.preview. These are repository release and specification labels, not a Stripe API version called “3.0.” Check the Stripe OpenAPI releases page for the current labels before implementation.
Quick Recap
Rank #4
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
