Each major release, such as Acacia, includes changes that aren’t backward-compatible with previous releases. Upgrading to a new major release can require updates to existing code. Each monthly release includes only backward-compatible changes, and uses the same name as the last major release. You can safely upgrade to a new monthly release without breaking any existing code. The current version is 2026-07-29.dahlia. For information on all API versions, view our API changelog.

You can upgrade your API version in Workbench. As a precaution, use API versioning to test a new API version before committing to an upgrade.

Some properties on API resources use a fixed set of possible string values, which are known as enums. Enums can be closed or open:

• Closed: The set of values for the enum is fixed and won’t grow or change over time.
• Open: The set of values for the enum can grow or change over time. Stripe can add new values as a backward-compatible change without requiring an API version upgrade. Each enum’s reference entry indicates whether it is open.

Handling open enums in responses

Don’t assume that the values documented for an open enum are exhaustive. When you read an open enum from an API response, your code should include a safe fallback—such as a default branch in a switch statement—to gracefully handle values your integration doesn’t yet recognize.

Sending enum values in requests

When sending an enum value in a request, use only the values documented for the parameter you’re setting. Even if an enum is open, Stripe validates request values against the set of values that are currently supported.