Skip to main content
POST
Create a sub-account
Provision isolated subaccounts under your main account for multi-tenant SaaS applications, reseller models, or departmental resource segregation.
Authentication required:
  • X-Auth-ID - Your account Auth ID
  • X-Auth-Token - Your account Auth Token
  • Content-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)
Success! The response contains three sections:
  • sub_account - The created sub-account object with all details.
  • auth_credentials - The sub-account’s own auth_id and auth_token. These are its primary API credentials - used as the X-Auth-ID / X-Auth-Token headers on every REST and telephony API call, exactly like a main account. Save them securely.
  • tokens - Optional JWT access/refresh tokens for signing the sub-account into the console/dashboard. They are not required to call the REST or telephony API - use the auth_id / auth_token above for that.
Security Note: The auth_token is only returned once during creation. Store it securely - you will not be able to retrieve it again. If lost, you will need to regenerate credentials.

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

X-Auth-ID
string
header
required

Your Vobiz account Auth ID

X-Auth-Token
string
header
required

Your Vobiz account Auth Token

Path Parameters

auth_id
string
required

Your account Auth ID

Example:

"MA_XXXXXX"

Body

application/json
name
string
required

Human-readable name for the sub-account.

email
string<email>

Required when kyc_mode is customer_use.

password
string

Login password for the sub-account.

kyc_mode
enum<string>
default:personal_use

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
business_type
enum<string>

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
enabled
boolean

Response

Success

message
string
required
sub_account
object
required
auth_credentials
object
required
tokens
object
required