Making API calls for connected accounts

You can make API calls for your connected accounts:

• Server-side with the Stripe-Account header and the connected account ID, per request
• Client-side by passing the connected account ID as an argument to the client library

To optimize performance and reliability, Stripe has established rate limits and allocations for API endpoints.

Adding the Stripe-Account header server-side

For server-side API calls, you can make requests as connected accounts using the special header Stripe-Account with the Stripe account identifier (it starts with the prefix acct_) of your platform user. Here’s an example that shows how to Create a PaymentIntent with your platform’s API secret key and your user’s Account identifier.

curl https://api.stripe.com/v1/payment_intents \
  -u "
sk_test_4eC39HqLyjWDarjtT1zdp7dc
:" \
  -H "Stripe-Account: 
{{CONNECTED_ACCOUNT_ID}}
" \
  -d amount=1000 \
  -d currency=usd \
  -d "automatic_payment_methods[enabled]"=true

In the latest version of the API, specifying the automatic_payment_methods parameter is optional because Stripe enables its functionality by default.

The Stripe-Account header approach is implied in any API request that includes the Stripe account ID in the URL. Here’s an example that shows how to Retrieve an account with your user’s Account identifier in the URL.

curl https://api.stripe.com/v1/accounts/
{{CONNECTED_ACCOUNT_ID}} \
  -u "
sk_test_4eC39HqLyjWDarjtT1zdp7dc
:"

All of Stripe’s server-side libraries support this approach on a per-request basis:

curl https://api.stripe.com/v1/customers \
  -u "
sk_test_4eC39HqLyjWDarjtT1zdp7dc
:" \
  -H "Stripe-Account: 
{{CONNECTED_ACCOUNT_ID}}
" \
  --data-urlencode email="person@example.com"

Adding the connected account ID to a client-side application

Client-side libraries set the connected account ID as an argument to the client application:

var stripe = Stripe('{{PLATFORM_PUBLISHABLE_KEY}}', {
  stripeAccount: '{{CONNECTED_STRIPE_ACCOUNT_ID}}',
});