Create a connected account
Create a connected account (tenant) owned by your platform organization. Act on its behalf on any other endpoint by sending your key plus the Invoice-Account: <id> header. Connected accounts do not get their own API keys.
Authorizations
API key: Authorization: Bearer sk_test_... or sk_live_....
Headers
Pin a dated API release (Stripe-style). Omit to use the current version. An unknown value returns 400 request.invalid_version. Echoed back on every response.
"2026-07-10"
Connect: act on behalf of one of your connected accounts (its acct_…/org_… id). Omit to act as your own organization. Not honored on /v1/api_keys.
"org_2P9connectedacct"
Safely retry any POST. The first response is stored for 24h and replayed byte-for-byte for identical retries (the replay adds an idempotent-replayed: true header). Reusing the key with a different body is 409 idempotency.key_reuse; an in-flight duplicate is 409 idempotency.key_processing. This makes retrying a 502/429 safe — no duplicate stamp.
"a1b2c3d4-e5f6-4789-8abc-1234567890ab"
Body
Response
Default Response
Always "account".
account Connected-account id, e.g. "org_2P9K3sample".
Display name of the connected account.
The platform org that owns this connected account.
True once the account has been disabled/offboarded (acting as it is rejected).
Integrator-owned key-value map echoed back.
Creation timestamp, ISO-8601 UTC.