What is the current Stripe API version, and how often does it change?

Stripe's versioning page gives the current version as 2026-09-30.endive. Since the 2024-09-30.acacia release, Stripe publishes new API versions monthly with no breaking changes, and twice a year issues a major release (for example Basil) that starts with an API version containing breaking changes.

Is there a Stripe API deprecation I need to act on?

Between 23 March 2026 and 25 September 2026, Stripe's published OpenAPI specification went from 587 to 612 operations, with 0 operations removed, 0 operations newly deprecated, and 6 marked deprecated in the current specification. Breaking changes are announced per release in Stripe's changelog, so check it for the version you are upgrading to. This page counts only what the OpenAPI specification shows.

Where are the Stripe changelog and release notes?

Stripe's API changelog lists every release by version name and date, for example 2026-09-30.endive, covering breaking and non-breaking changes across its products. The upgrade guide tells you how to move a pinned version forward.

Where is the Stripe OpenAPI spec?

Stripe publishes it in the stripe/openapi repository on GitHub, in JSON and YAML. The latest directory holds the latest GA release with v1 and v2 endpoints, preview adds public preview endpoints, and openapi is the legacy v1-only set, still updated every release. This page reads openapi/spec3.json from that repository.

How do I test a newer Stripe API version before upgrading?

Stripe recommends specifying the API version in your code rather than relying on your account's default, and testing a newer version by setting the Stripe-Version header, in live or test environments. Server-side SDKs use the version that was current when the SDK was released, and in strongly typed languages such as Java, Go and .NET you cannot target a different version.

What Stripe changed, 23 March 2026 to 25 September 2026

587 operations became 612. None were removed, 0 were newly deprecated, 25 were added, and 0 request fields became required.

Read from stripe/openapi at a54c388 and 2bab976 (version 2026-09-30.endive). Generated 27 September 2026 by the same code that runs in your CI, so this page and your report cannot disagree.

Each Stripe account has a default API version, and a request uses it unless the Stripe-Version header or the SDK sets another, so a specification change is an upgrade question rather than an outage. Findings here are worded as upgrade impact.

Removed from the specification

Nothing was removed in this window. That is a real result, not a gap in the check.

Newly deprecated in this window

A deprecation is the notice period. It is the cheapest moment to act and the easiest one to miss. This list compares operations present at the baseline.

No compared operation (one paired with a baseline operation) gained the deprecated flag in this window.

Deprecated as of the current specification (6)

Everything the vendor currently marks deprecated, whether or not it changed recently. The vendor has flagged each of these for possible removal, with or without a date attached.

GET /v1/customers/{customer}/bank_accounts
GET /v1/customers/{customer}/bank_accounts/{id}
GET /v1/customers/{customer}/cards
GET /v1/customers/{customer}/cards/{id}
POST /v1/issuing/authorizations/{authorization}/approve
POST /v1/issuing/authorizations/{authorization}/decline

Entries without a link were already marked deprecated at a54c388 · 23 March 2026, the baseline compared here.

Request fields removed from the specification

The current specification no longer lists these request fields, which the baseline did. A caller that still sends one is sending a parameter the new version does not define; whether Stripe rejects or ignores it at runtime is not something a specification diff can show, and what it means for an integration depends on how Stripe versions — see the note at the top of this page.

POST /v1/accounts no longer lists documents.proof_of_registration (application/x-www-form-urlencoded)
POST /v1/checkout/sessions no longer lists line_items[].dynamic_tax_rates (application/x-www-form-urlencoded)
POST /v1/checkout/sessions no longer lists payment_method_types (application/x-www-form-urlencoded)
POST /v1/financial_connections/sessions no longer lists filters.countries (application/x-www-form-urlencoded)
POST /v1/link_account_sessions no longer lists filters.countries (application/x-www-form-urlencoded)
POST /v1/payment_intents no longer lists payment_method_types (application/x-www-form-urlencoded)
POST /v1/payment_intents/{intent} no longer lists payment_method_types (application/x-www-form-urlencoded)
POST /v1/payment_intents/{intent}/confirm no longer lists payment_method_types (application/x-www-form-urlencoded)
POST /v1/payment_methods/{payment_method} no longer lists payto (application/x-www-form-urlencoded)
POST /v1/setup_intents no longer lists payment_method_types (application/x-www-form-urlencoded)
POST /v1/setup_intents/{intent} no longer lists payment_method_types (application/x-www-form-urlencoded)
POST /v1/terminal/refunds no longer lists amount (application/x-www-form-urlencoded)
POST /v1/terminal/refunds no longer lists charge (application/x-www-form-urlencoded)
POST /v1/terminal/refunds no longer lists metadata (application/x-www-form-urlencoded)
POST /v1/terminal/refunds no longer lists payment_intent (application/x-www-form-urlencoded)
POST /v1/terminal/refunds no longer lists reason (application/x-www-form-urlencoded)
POST /v1/terminal/refunds no longer lists refund_application_fee (application/x-www-form-urlencoded)
POST /v1/terminal/refunds no longer lists reverse_transfer (application/x-www-form-urlencoded)

Stripe API questions

Vendor facts below were checked against the linked official pages on 22 October 2026. Counts come from the snapshot above.

What is the current Stripe API version, and how often does it change?: Stripe's versioning page gives the current version as 2026-09-30.endive. Since the 2024-09-30.acacia release, Stripe publishes new API versions monthly with no breaking changes, and twice a year issues a major release (for example Basil) that starts with an API version containing breaking changes.; Source: Stripe API versioning
Is there a Stripe API deprecation I need to act on?: Between 23 March 2026 and 25 September 2026, Stripe's published OpenAPI specification went from 587 to 612 operations, with 0 operations removed, 0 operations newly deprecated, and 6 marked deprecated in the current specification. Breaking changes are announced per release in Stripe's changelog, so check it for the version you are upgrading to. This page counts only what the OpenAPI specification shows.; Source: Stripe API changelog
Where are the Stripe changelog and release notes?: Stripe's API changelog lists every release by version name and date, for example 2026-09-30.endive, covering breaking and non-breaking changes across its products. The upgrade guide tells you how to move a pinned version forward.; Source: Stripe API changelog
Where is the Stripe OpenAPI spec?: Stripe publishes it in the stripe/openapi repository on GitHub, in JSON and YAML. The latest directory holds the latest GA release with v1 and v2 endpoints, preview adds public preview endpoints, and openapi is the legacy v1-only set, still updated every release. This page reads openapi/spec3.json from that repository.; Source: stripe/openapi on GitHub
How do I test a newer Stripe API version before upgrading?: Stripe recommends specifying the API version in your code rather than relying on your account's default, and testing a newer version by setting the Stripe-Version header, in live or test environments. Server-side SDKs use the version that was current when the SDK was released, and in strongly typed languages such as Java, Go and .NET you cannot target a different version.; Source: Stripe: upgrade your integration

This list is not your list

Most of what is above does not matter to you, and the two lines that do are hard to find by eye. The check takes the endpoints you declare and reports only their intersection with this page.

How the check works · a real report