Skip to content

TelVox · Connect · Docs

Developer docs

TelVox Connect is the programmable-voice API behind the TelVox platform — the developer-facing sibling of Dial. Place and receive calls, drive them in real time, record under policy, and react to lifecycle events from your own code, on the same compliance-engineered infrastructure that powers Dial. These docs cover the concepts, a make-your-first-call quickstart, task guides and the API reference.

Developer preview

Connect is in developer preview. The capabilities are real and shipped in Dial, but the public REST API, SDKs, CLI and self-serve console are preview surfaces — endpoints, fields and payloads may change before general availability. Every API artifact in these docs is stamped “illustrative.”

The auth model, in brief

Server-side requests authenticate with an API key — a SID plus a secret, conceptually a username and password — sent as a bearer token in the Authorization header. The base URL is https://api.telvox.dev. Browser and mobile WebRTC clients never see the secret: your server mints a short-lived JWT access token with a voice grant and the client consumes that. Key issuance is provisioned with our team during the preview. See Authentication & API keys for the full model.

POST/v1/calls
# illustrative — shape may differ at GA
curl https://api.telvox.dev/v1/calls \
  -H "Authorization: Bearer $TELVOX_API_KEY" \
  -d from="+14155550100" \
  -d to="+14155550199" \
  -d answer_url="https://your.app/voice/answer"
201 createdringing

Start here

New to Connect? These three get you from zero to a ringing phone.

Quickstart

Make your first call end to end — get preview keys, set an answer_url, POST a call, and handle the status callback.

Open
Authentication & API keys

How requests are authenticated: an API key SID + secret sent as a bearer token, plus short-lived JWTs for WebRTC clients.

Open
Make your first call

A single POST to /v1/calls places an outbound call; inbound calls hit your answer URL so your app decides what happens next.

Open

Concepts

The mental model behind the API — how auth, call control and webhooks fit together.

Authentication & API keys

API-key SID + secret, bearer auth, env-var conventions, and short-lived access tokens for browser and mobile clients.

Open
Call-control markup

The answer-URL request/response loop and the call-control document your app returns. A markup dialect is on the roadmap.

Open
Webhooks & callbacks

Status callbacks across the call lifecycle and the signed, SSRF-safe egress that delivers them to your endpoints.

Open

Guides, reference & SDKs

Go deeper: runnable task guides, the per-resource API reference, and the planned helper libraries and CLI.

Guides

Task-oriented how-tos: build an IVR, track calls, send outbound notifications, embed WebRTC calling, record for QA.

Open
API Reference

Base URL, auth, errors, pagination and the resource index — Calls, Recordings, Conferences, Queues, Numbers and more.

Open
SDKs & CLI

Planned server helper libraries, client WebRTC SDKs and a telvox CLI. Names and packages are preview, not yet published.

Open