Stripe-Context header

By default, API requests execute on the Stripe account that generated the accompanying API key. However, you can use the Stripe-Context header to perform an API request in the context of a related account.

API request scope

You can make API requests to operate within different scopes:

• Your own account
• Any connected account in your platform
• Any v2 account with at least the merchant or recipient configuration

When you make an API request targeting an account other than that of the API key, you must identify the intended account by including the Stripe-Context header. The value depends on the relative relationship of the intended account to the API key used to make the request.

For example, consider an organization with multiple platform accounts representing different business lines. Each platform has connected accounts and one connected account has a recipient account.

Given this business structure, it’s possible to perform API requests using several different scopes. The following table shows the Stripe-Context format for each different scope that requires context based on its relationship to the account the requesting API key belongs to.

Example use cases

The following code sample shows a request where the Rocket US platform retrieves the available bank accounts for the recipient of its connected account. The recipient is the grandchild of the platform, so the context uses the format <connected account ID>/<recipient ID>.

curl https://api.stripe.com/v2/core/vault/us_bank_accounts \
  -H "Authorization: Bearer {{PLAT_SECRET_KEY}}" \
  -H "Stripe-Version: 2025-03-31.preview" \
  -H "Stripe-Context: acct_111a/acct_111b"