vobiz-partner-api
Vobiz Partner API skill
Use this for reseller workflows where one partner master account owns multiple partner child accounts (the docs also call them customer accounts or customer sub-accounts). Each child is a full Vobiz main account (MA_…) with its own wallet, KYC, numbers, CPS, and concurrency. Auth uses the same X-Auth-ID / X-Auth-Token headers as the main API - there is no separate Bearer JWT for server-to-server calls. Just use your partner-tier credentials. (POST /login exchanges email + password for a JWT, but the docs reserve it for interactive sessions; it is doc-only and not in openapi.yaml.)
Not sure whether the user needs partner child accounts or sub-accounts? See concepts/sub-accounts-vs-partner-accounts and the vobiz-sub-accounts skill.
Base path
https://api.vobiz.ai/api/v1/partner/*
(Routes do NOT live under /partner/v1/ - that path returns 404.) Send Accept: application/json, and Content-Type: application/json on bodies.
Partner profile + dashboard
GET /api/v1/partner/me- your partner profile:id(UUID),auth_id(PA_…),balance(string, 5 decimals),currency,max_accounts,account_count,is_verified, and the capability flagscan_create_accounts,can_transfer_balance,can_view_cdrs,can_create_pricing_tiers.GET /api/v1/partner/dashboard- aggregated metrics over aperiod:accounts {total, active, customers[]},total_balance(string),currency,calls,traffic {inbound, outbound},by_product {sip_trunking, voice_api},time_series[].partner.balanceisnullhere.GET /api/v1/partner/analytics?from_date=&to_date=- same shape over a custom window (defaults to the last 30 days). Doc-only (partner/api/analytics), not in the spec.
Auth model in one line: partner creds (PA_…) drive /api/v1/partner/*; the customer's own creds (MA_…) drive /api/v1/Account/{customer_auth_id}/* voice ops. Your partner token cannot drive a customer's voice resources. Sending the wrong pair against the wrong base path returns 401/403.