Skip to main content
GET
List customer accounts
← Partner API Reference The core of the Partner API. Provision SIP-enabled sub-accounts for your clients, inspect their profiles, and monitor their real-time wallet balances. Each customer receives an auth_id that serves as the primary key for all subsequent operations.
All Partner API requests use X-Auth-ID and X-Auth-Token headers. See Authentication for details.

Overview

Create Customer Account

Provisions a new SIP-enabled Vobiz account under your partner umbrella. The customer is created instantly and can start receiving calls as soon as you assign a phone number and fund their wallet.

Request Body

The minimum verified field set is name, email, phone, password, and country. company is the only documented optional field guaranteed by the API contract; the remaining optional fields above are accepted on a best-effort basis - if your call rejects one, drop it and set it later via the Console.
Validation rules
  • email must be unique across the whole Vobiz platform - reusing an email returns 422.
  • password must be at least 8 characters and contain a number and a special character. A weaker password returns 422.
  • phone must be E.164 (leading + and country code).
  • country must be a valid ISO 3166-1 alpha-2 code. The customer’s wallet currency is derived from it (ININR).
  • Creating a customer counts against your max_accounts limit (see Profile). Exceeding it returns 403.

Response

A successful create returns 201 Created. The new customer starts with balance: 0.00 and status: active, but kyc_status is pending and the wallet is empty - you must transfer balance and (for India) run KYC before the account is fully usable.
Store both auth_id and auth_token immediately - the auth_token is shown only once. The auth_id is the customer’s permanent identifier for every partner operation (balance transfers, CDR lookups, transaction queries, number assignments). The auth_token is the customer’s own API secret - the only way to retrieve it again later is Get Customer Account. Treat the auth_token like a password: store it encrypted server-side and never expose it in client-side code, URLs, or logs.

Errors

List Customer Accounts

Returns a paginated list of all customer accounts under your partner umbrella. Use search to find a specific customer by name or email.

Query Parameters

The request uses per_page, but the response echoes it back as size. They are the same value under two different keys.

Get Customer Account

Returns the full technical profile for a specific customer, including their auth token (required to make API calls on their behalf), billing configuration, GST details, and current status.

Get Customer Balance

Returns the real-time wallet balance for a specific customer. Check this before deciding whether to top up a customer’s wallet. A customer with zero or near-zero balance will start experiencing call failures.

Provisioning Workflow

Follow this sequence when onboarding a new customer:
  • Create the account - Provision the sub-account. Store the returned auth_id in your database.
  • Fund the wallet - Transfer an opening balance from your master account. The customer cannot make calls without balance.
  • Assign phone numbers - Assign one or more DID phone numbers to the customer account. Customers need a DID to receive inbound calls.
  • Monitor usage - Pull CDRs and transaction logs regularly for billing and quality monitoring.

Authorizations

X-Auth-ID
string
header
required

Your Vobiz account Auth ID

X-Auth-Token
string
header
required

Your Vobiz account Auth Token

Query Parameters

page
integer
default:1
per_page
integer
default:20

Substring match on name or email.

Response

200 - application/json

Customer accounts

accounts
object[]
required
total
integer
required
page
integer
required
size
integer
required