Request IDs

Each API request has an associated request identifier. You can find this value in the response headers, under Request-Id. You can also find request identifiers in the URLs of individual request logs in your Dashboard.

To expedite the resolution process, provide the request identifier when you contact us about a specific request.

curl https://api.stripe.com/v1/customers \
  -u sk_test_Hrs6SAo...0bZXSN3f6ELNsk_test_Hrs6SAopgFPF0bZXSN3f6ELN: \
  -D "-" \
  -X POST

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

Per-Request Account

curl https://api.stripe.com/v1/charges/ch_3LmjFA2eZvKYlo2C09TLIsrw \
  -u sk_test_Hrs6SAo...0bZXSN3f6ELNsk_test_Hrs6SAopgFPF0bZXSN3f6ELN: \
  -H "Stripe-Account: acct_1032D82eZvKYlo2C" \
  -G

Versioning

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 2025-12-15.clover. 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.