List SIP trunks
Authorization
bearerAuth API key authentication: send your Zernio API key in the Authorization header, prefixed with Bearer.
In: header
Response Body
application/json
application/json
{ "trunks": [ { "id": "string", "label": "string", "sipHost": "string", "sipPort": 0, "transport": "tls", "termination": { "uri": "string", "username": "string" }, "numbersAttached": 0, "createdAt": "2019-08-24T14:15:22Z" } ], "enabled": true}Detach a number from its SIP trunk
Returns the number's calls to Zernio routing. Idempotent when the number is not attached to any trunk.
Create a SIP trunk
Creates a SIP trunk an external voice platform (Retell, ElevenLabs, Vapi, or any SIP endpoint) can import your Zernio numbers into. The trunk carries both directions: inbound calls on attached numbers are delivered to `sipHost`, and the platform originates outbound calls through `termination.uri` with the digest credentials. The `digestPassword` is returned only by this call (and by rotate-credentials); store it immediately. Attach any number of numbers to a trunk. Several trunks may point at the same host. Each carries its own credentials and spend cap, so separate destinations (e.g. an agency's clients) stay isolated.