What Stripe changed, 17 March 2026 to 26 August 2026
587 operations became 594. None were removed, 0 were newly deprecated, 7 were added, and 0 request fields became required.
Read from stripe/openapi at cfe95bf and 30d3391 (version 2026-08-26.dahlia). Generated 17 September 2026 by the same code that runs in your CI, so this page and your report cannot disagree.
Every account is pinned to a dated API version, so a specification change is an upgrade question rather than an outage. Findings here are worded as upgrade impact.
Removed — these return 404 now
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.
Nothing was newly deprecated in this window.
Deprecated as of the current specification (6)
Everything the vendor currently marks deprecated, whether or not it changed recently. If you call one of these, it has a clock on it.
- 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
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.