DEVELOPERS

TELVEX API

A REST interface over the same platform the carrier portal uses — numbers, routing, trunks and call detail records, authenticated with scoped bearer keys.

01ENDPOINTS

telvex@api ~ v1

List DID numbers assigned to your account.

REQUEST

curl https://api.telvex.cc/v1/numbers \
  -H "Authorization: Bearer $TELVEX_API_KEY" \
  -G -d country=GB -d type=geographic -d limit=2

RESPONSE

200 OK

{
  "object": "list",
  "data": [
    {
      "id": "num_8f21c0",
      "e164": "+442038xxxxxx",
      "country": "GB",
      "type": "geographic",
      "status": "active",
      "trunk": "trk_edge_lon_01"
    },
    {
      "id": "num_a71d55",
      "e164": "+442079xxxxxx",
      "country": "GB",
      "type": "geographic",
      "status": "active",
      "trunk": "trk_edge_lon_01"
    }
  ],
  "has_more": false
}

$ ▊

API DOCUMENTATION

REST over HTTPS, JSON payloads, cursor pagination and idempotent order calls.

AUTHENTICATION

Bearer API keys scoped per environment, rotatable from the carrier portal.

WEBHOOKS

Signed events for call completion, number provisioning and trunk state changes.

RATE LIMITS

Per-key limits with burst allowance; headers expose remaining quota.

02WEBHOOK EVENTS

call.completedEmitted when a call clears, including duration and disposition.

number.provisionedEmitted when an ordered number becomes routable.

trunk.state_changedEmitted on registration or IP endpoint state transitions.

balance.thresholdEmitted when a prepaid balance crosses a configured level.

03RATE LIMITS

READ

600 req / min

WRITE

120 req / min

BURST

2× for 10 s

Indicative limits · confirmed per account at provisioning

Connect your
traffic.