Sub-Accounts
Create a Subaccount
Provision an isolated Vobiz subaccount with its own auth credentials for multi-tenant SaaS apps, white-label resellers, or departmental resource separation.
POST
Create a sub-account
Authentication required:
X-Auth-ID- Your account Auth IDX-Auth-Token- Your account Auth TokenContent-Type: application/json
Parameters
Authenticate as the parent. Send your parent main account’s
X-Auth-ID / X-Auth-Token; the {auth_id} in the path is your parent (MA_…) account. The sub-account does not have credentials until this call returns them.Creating a sub-account with
kyc_mode: "customer_use" returns it with kyc_calls_blocked: true - the sub-account cannot place calls until it completes KYC. If you omit email while setting customer_use, the request fails with 400. See Sub-Account KYC for the full create → KYC → unblock recipe.Request
Response Example
Success Response (201 Created)
business_type and required documents
For a customer_use sub-account, business_type sets which KYC documents the sub-account must clear before kyc_calls_blocked flips to false:
You can set
business_type at creation or later via Update. See Sub-Account KYC for the per-document endpoints.
Common errors
Authorizations
Your Vobiz account Auth ID
Your Vobiz account Auth Token
Path Parameters
Your account Auth ID
Example:
"MA_XXXXXX"
Body
application/json
Human-readable name for the sub-account.
Required when kyc_mode is customer_use.
Login password for the sub-account.
personal_use inherits parent KYC. customer_use requires
the sub-account to complete its own KYC and requires email.
Available options:
personal_use, customer_use Legal constitution of the customer. Drives which KYC documents are required.
Available options:
individual, proprietorship, private_limited, llp, partnership, public_limited, trust, society, huf, government