Base URL:
https://unpod.ai/api/v2/platform/
Every request needs an Authorization: Token <your-api-key> header and an Org-Handle
header. See Authentication.The three building blocks
Numbers
Your phone numbers (DIDs). List the pool available to your org and attach a number
to an agent so inbound calls reach it.
Trunks
A trunk is your SIP carrier credential. Create one, map numbers to it, and get back
the carrier ingress (the origin endpoint).
Calls
Observe the lifecycle: which numbers are linked, to which agent or carrier, and the
projection sync state - plus full call logs.
How it fits together
There is one primary termination path:
| Path | What it does | Endpoint |
|---|---|---|
| Leg A - BYO carrier | Map a number to your SIP trunk; the carrier sends inbound calls to your origin endpoint. | Attach Numbers to Trunk |
Key concepts
- DID/Number - a phone number in E.164 format (e.g.
+15551234567). - Trunk - a SIP carrier credential (
sip_url,transport,port, auth, source-IP allow-list). Secrets are always masked in responses. - Origin endpoint - the shared SBC ingress (
sip:<host>) the carrier sends inbound calls to, plus the accepted source IPs and mapped DIDs. - Bridge - the routing entity numbers attach onto. It is auto-resolved and hidden on the Connectivity surface - you never manage it directly here.
- Partial success - attach/detach operate on a list; each number reports
ok/errorindependently.
Get started in 5 minutes
Create a trunk, map a number, and confirm the lifecycle - step by step.