Connected Accounts

If you use Stripe Connect, you can issue requests on behalf of your connected accounts. To act as a connected account, include a Stripe-Account header containing the connected account ID, which typically starts with the acct_ prefix.

The connected account ID is set per-request. Methods on the returned object reuse the same account ID.

Related guide: Making API calls for connected accounts

Was this section helpful? Yes No

Per-Request Account

Versioning

Starting with the 2024-09-30.acacia release, Stripe follows a new API release process where we release new API versions monthly with no breaking changes. Twice a year, we issue a new major release (for example, Basil) that starts with an API version containing breaking changes. You can safely upgrade to any monthly release without updating your code. Upgrading to a new major release can require changes to your existing integration.

The current version is 2026-08-26.dahlia. For information on all API updates, view our API changelog. To upgrade your API version, see API upgrades.

Requests made with curl use your Stripe account’s default API version (controlled in Workbench) unless you override it by setting the Stripe-Version header.

Webhook events also use your account’s default API version unless you set an API version during endpoint creation.

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.

Was this section helpful? Yes No

Enums

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.

Was this section helpful? Yes No