List sub-accounts
List sub-accounts
List your sub-accounts with their state, owner, tasks, leads, and the leads each one contacted this period against your plan.
GET
List sub-accounts
A sub-account is a separate Nexor account that belongs to your account. It has its own team, agents, numbers, conversations, and leads, and every lead it contacts counts toward your plan. See Sub-accounts.
The main account is always the account that owns the API key. There is no parameter to act on behalf of another account.
Read the response
agents_activeandagents_totalcount tasks (workflowin the API), not agents.contacted_periodis what one sub-account contacted this period.family.usedadds up the main account and all its sub-accounts, and is the number compared withfamily.quota.nullinperiod,family, orcontacted_periodmeans the usage meter could not be read. It does not mean zero.
Before you start
- Sub-accounts are an optional feature that Nexor enables on request. Without it, every endpoint in this section returns 403
sub_accounts_not_enabled. Contact Nexor Support to request it. - Use an API key of the main account. A key that belongs to a sub-account gets 403
sub_account_cannot_manage_sub_accounts, because a sub-account cannot have sub-accounts of its own. - MCP keys need
sub-accounts:readto list andsub-accounts:writefor every other operation. Full-access API keys need nothing else. - Every change requires
"confirm": truein the body. Without it, the API returns 400confirmation_requiredand changes nothing. - An ID that is not one of your sub-accounts returns 403
not_parent_of_client. - Errors return a stable code in
error, such asowner_email_invalid. Map the code to your own message.
Authorizations
API key for authentication. Keys are prefixed with nxr_live_.
Last modified on October 1, 2026