TelVox · Connect · Docs

SDK status

There are no TelVox SDKs, helper libraries or CLI yet. The REST API is plain HTTPS and JSON, so any HTTP client works. Every sample in these docs uses cURL, Node fetch or Python requests.

Use any HTTP client

Send your API key as a Bearer token, send JSON, and send Accept: application/json so errors come back as JSON. Here is the same outbound call in three clients. See the Quickstart for the full walk-through and the API reference for every endpoint.

curl -X POST "$TELVOX_BASE_URL/calls" \
  -H "Authorization: Bearer $TELVOX_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json" \
  -d '{
    "from": "+918045670100",
    "to": "+919876500199",
    "url": "https://your.app/voice/answer",
    "statusCallback": "https://your.app/voice/status"
  }'

Environment variables

The samples read two variables. Keep the key on your server.

# server side only. Never ship the key to a browser.
TELVOX_API_KEY=sk_live_…   # created in the dashboard, shown once
TELVOX_BASE_URL=https://connect.telvox.dev/api

Twilio helper libraries do not work

The XML your webhook returns follows Twilio's markup, and status callbacks use Twilio's field names (CallSid, CallStatusand so on). So code that builds TwiML or reads Twilio callbacks will mostly carry over. The REST API is different: the paths, the request fields and the auth (one Bearer key, not an account SID and token) do not match Twilio's, so a Twilio REST client cannot talk to Connect.

Browser dialers

There is no TelVox browser SDK. To put an agent on calls in the browser, create a WebRTC agent seat and sign in with a standard SIP-over-WebSocket library such as JsSIP or SIP.js, using the seat's SIP credentials and TURN servers. Your server fetches those with your API key. See SIP trunks for the connection endpoint.

Building tooling or an agent against Connect? A plain-text index of these docs lives at /connect-llms.txt.