Skip to main content
Most Vobiz REST API requests use the account Auth ID and Auth Token headers. The CPS and concurrency capacity endpoints also accept an account access token in the standard Bearer header.
Account API credentials:
  • X-Auth-ID - Your account Auth ID
  • X-Auth-Token - Your account Auth Token

​
Where to find your credentials

After signing in to the Vobiz Console, your Auth ID and Auth Token are displayed directly on the main dashboard. Copy both - you’ll pass them as headers on every API call.
Vobiz dashboard showing Auth ID, Auth Token, and account balance
Your Auth ID looks like MA_XXXXXXXX. Treat your Auth Token like a password - anyone with both values can act on your account.

​
Making an authenticated request

cURL
A successful call to /auth/me returns your full account object, including verification status and pricing tier - a good way to confirm your credentials work before building further. See Retrieve Account Details for the full response shape.

​
Bearer access tokens for capacity endpoints

The capacity pricing preview and capacity purchase endpoints also accept an account access token:
This Bearer-token option applies only where an endpoint explicitly documents it. Continue using X-Auth-ID and X-Auth-Token for other Vobiz API operations. For the full error response format and all status codes, see Error Handling.

​
Security notes

  • Never expose X-Auth-Token in client-side code (browser JS, mobile apps). Route API calls through your own backend.
  • Protect Bearer access tokens with the same controls as the account Auth Token.
  • If a token is compromised, regenerate it from the Console dashboard immediately - the old token stops working as soon as you do.