Making API calls for connected accounts
Learn how to add the right information to your API calls so you can make calls for your 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:
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.
All of Stripeâs server-side libraries support this approach on a per-request basis:
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:
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.