Documentation Index
Fetch the complete documentation index at: https://docs.vobiz.ai/llms.txt
Use this file to discover all available pages before exploring further.
Overview
Sub-account KYC enables partners and resellers to enforce identity verification on each of their customers (sub-accounts) before allowing outbound calls. When a sub-account is created incustomer_use mode, Vobiz automatically blocks all outbound calls until the required KYC checks are approved.
Real KYC
Perfios-backed PAN, GST, CIN, Aadhaar, and DigiLocker verification
Hosted Sessions
Email-link flow - customer completes KYC on the Vobiz-hosted widget
Test Mode
Mock endpoints with magic inputs for sandbox testing
KYC modes
Every sub-account has akyc_mode field that controls whether KYC is enforced.
| Mode | Behaviour | Use case |
|---|---|---|
personal_use | KYC not required; calls are never blocked for KYC reasons. Default. | Internal teams, dev/test sub-accounts |
customer_use | KYC required; kyc_calls_blocked is set to true until all required verifications pass | Customer-facing sub-accounts on a reseller platform |
Setting kyc_mode on create
Passkyc_mode in the request body when creating a sub-account. customer_use also requires an email field.
kyc_calls_blocked: true for a fresh customer_use sub-account.
Promoting an existing sub-account
Business types
When creating or updating a sub-account incustomer_use mode, pass one of the following values for business_type:
| Value | Entity |
|---|---|
individual | Individual / sole trader |
proprietorship | Sole proprietorship |
private_limited | Private limited company |
llp | Limited Liability Partnership |
partnership | Partnership firm |
public_limited | Public limited company |
trust | Trust |
society | Society |
huf | Hindu Undivided Family |
government | Government body |
KYC status
Fetch the aggregated KYC state for a sub-account. The caller must be the parent main account (or an admin).| Field | Description |
|---|---|
kyc_calls_blocked | true when required verifications are incomplete; outbound calls are blocked |
verifications | Per-method status - verified, failed, pending, or null (not attempted) |
Verification methods
Choose the verification methods appropriate for your customer’s business type:| Method | Endpoint | Best for |
|---|---|---|
| PAN | POST /kyc/verify-pan | All entities |
| GST | POST /kyc/verify-gst | GST-registered businesses |
| CIN | POST /kyc/cin/search + /cin/confirm | Registered companies |
| Aadhaar (OTP) | POST /kyc/aadhaar/consent + /kyc/verify-aadhaar | Individuals |
| DigiLocker | POST /kyc/digilocker/initiate + /kyc/digilocker/verify | Individuals (Aadhaar via OAuth) |
Authentication
All KYC endpoints authenticate as the parent main account using a JWT bearer token:{sub_auth_id} in the URL path, not by the auth header.
Next steps
Verification methods
PAN, GST, CIN, Aadhaar, and DigiLocker API reference
Hosted KYC session
Let customers complete KYC via a Vobiz-hosted email link
Test mode
Magic inputs for sandbox and CI testing
Sub-Accounts API
Full sub-account object reference