Sub-Accounts
Update a Subaccount
Update any fields on a Vobiz subaccount - rename it, toggle enabled status, adjust rate limits, or modify permissions. Unset fields remain unchanged.
PUT
Update a sub-account
Authentication required:
X-Auth-ID- Your account Auth IDX-Auth-Token- Your account Auth TokenContent-Type: application/json
Parameters
| Field | Type | Required | Description |
|---|---|---|---|
name | string | No | Name of the sub-account. |
email | string | No | Email address associated with the subaccount. |
phone | string | No | Phone number associated with the subaccount. |
description | string | No | Description of the sub-account purpose or usage. |
rate_limit | integer | No | API rate limit for this sub-account (requests per time period). |
permissions | object | No | Permissions object defining what the sub-account can access. Contains boolean fields like calls and cdr. |
enabled | boolean | No | Whether the subaccount is active and enabled for use. |
kyc_mode | string | No | Change the verification mode: personal_use or customer_use. Promoting to customer_use requires the sub-account to already have an email. On any change, kyc_calls_blocked is re-derived from the sub-account’s current KYC state. |
Request
Response Example
Success Response (200 OK)
Changing kyc_mode
Promoting a sub-account from personal_use to customer_use requires it to already have an email — otherwise the call fails with 400. On any kyc_mode change, kyc_calls_blocked is re-derived from the sub-account’s current KYC state:
- Promote to
customer_useon a sub-account that has not completed its own KYC →kyc_calls_blockedbecomestrueand calls are blocked until it verifies. - Demote to
personal_use→ the sub-account inherits the parent’s KYC andkyc_calls_blockedbecomesfalse.
Authorizations
Your Vobiz account Auth ID
Your Vobiz account Auth Token
Path Parameters
Your account Auth ID
Example:
"MA_XXXXXX"
Body
application/json
Response
200 - application/json
Sub-account updated