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 help with performance and reliability, Stripe has established rate limits and allocations for API endpoints.

Add the Stripe-Account header server-side

To make server-side API calls for connected accounts, use the Stripe-Account header with the account identifier, which begins with the prefix acct_. Here are four examples using your platform’s API secret key and the connected account’s Account identifier:

curl https://api.stripe.com/v1/payment_intents \
  -u "
sk_test_BQokikJOvBiI2HlWgH4olfQ2
:" \
  -H "Stripe-Account: 
{{CONNECTED_ACCOUNT_ID}}
" \
  -d amount=1000 \
  -d currency=usd

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_BQokikJOvBiI2HlWgH4olfQ2
:"

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_BQokikJOvBiI2HlWgH4olfQ2
:" \
  -H "Stripe-Account: 
{{CONNECTED_ACCOUNT_ID}}
" \
  --data-urlencode email="person@example.com"

Add 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(
'pk_test_TYooMQauvdEDq54NiTphI7jx', {
  stripeAccount: 
{{CONNECTED_ACCOUNT_ID}},
});

Use Connect embedded components

Instead of directly integrating with Stripe’s APIs, you can use Connect embedded components to provide Stripe functionality to your connected accounts in your platform’s UI. These components require less code to implement and handle all API calls internally.

For example, to show payments data to your connected accounts, embed the Payments component in your platform’s UI. This eliminates the need to make separate calls to the Charges, Payment Intents, Refunds, and Disputes API.

For a complete list of the available embedded components, see Supported components.