Skip to main content
Set account scope for each API MCP request. The Straddle-Account-Id header names the embedded account a platform acts for; whether to send it depends on your integration model and the operation. Set the account in your MCP request separately from the account selected in the Straddle CLI.

​
Choose the account

For a platform request, use the Straddle account ID from your application’s tenant mapping or an exact account lookup. Resolve an ambiguous match before continuing. For the account model itself, see Manage embedded accounts. Keep the following facts together when reviewing a request: Confirm the integration model in your platform configuration and integration plan.

​
Apply the header rule

Use the following rules for the request you discovered: When a SaaS or marketplace row says “send when an account is selected,” omit the header if no account is selected. Select the account explicitly for a task about one tenant. Marketplace customers and paykeys belong to the platform, so their requests omit the header. Charges and payouts identify the seller’s account when the operation requires it.

​
Pass scope to API MCP

For an account-scoped request, include the selected ID in execute-request’s headers. Replace the placeholder with the account you confirmed:
For account-management operations such as GET /v1/accounts/{account_id}, the path identifies the account and the header stays omitted.

​
Switch to another account

Confirm the new account ID, review the operation’s header rule, and rebuild the request before sending it. Any write preview must show the new target before you approve it. For a first authenticated read, follow Read an account through API MCP.