Multi-account API

Multi-Account API for Platforms and SaaS Products

Your AI Connector is a multi-account API for AI agents: create one account per customer, run its agents on WhatsApp, Instagram and thirteen more channels with your own key by passing sub_account_id, hand out scoped keys, and get signed webhooks that name the account.

  • AccountsPOST /subaccounts
  • Act assub_account_id
  • Keysscoped per account
  • Eventssigned webhooks
List an account's agents
curl -G https://api.youraiconnector.com/v1/agents \
  -d sub_account_id=$SUB_ACCOUNT_ID \
  -H "X-API-Key: $API_KEY"
POST/subaccountsCreate an account
GET/subaccountsList accounts
GET/agents?sub_account_id=Act on an account
POST/webhooksOne endpoint, every account

Run Every Account from One Key

  • One account per customer. /subaccounts creates, lists and removes them.
  • Act on an account. Add sub_account_id to any call: agents, channels, contacts, broadcasts, bookings.
  • Separate data. Ownership is checked on every request, so one account never reads another.
  • Signed webhooks. Each event names the account it belongs to, so one endpoint can serve every account.

Keys You Can Hand to a Customer

Give a customer, a dashboard or an integration a key that only reaches what it needs: read only, a few sections of the API, or a list of accounts. Rotate a key without downtime and revoke one that should stop working. Build your own UI on the API, or use the ready inbox where a person can take over any chat. See the keys and access overview and the comparison with respond.io.

FAQ

Multi-Account API Questions

What is a multi-account messaging API?

An API where every customer of your product gets its own account: its own agents, channels, contacts and inbox. You run all of them with one key by passing sub_account_id, and each account's data stays separate.

How do I manage a customer's account over the API?

Create the account with POST /subaccounts, then pass sub_account_id on any call to act on that account's agents, channels and inbox. Ownership is checked on every request.

Can I give a customer their own API key?

Yes. Scoped API keys can be limited to read only, to certain sections of the API, or to a list of accounts, so a key scoped to one account cannot touch your data or another account's.

How do webhooks work with many accounts?

Every event is signed and names the account it belongs to, so one endpoint can serve every account and route each event in your own code.

Can I build my own UI?

Yes. Everything the inbox does is in the API, so you can build your own front end and use webhooks for real time updates.

Build Your Product on One API

Tell us what you are building and we reply by email with access.