TelVox · Connect
Programmable voice, in a few lines of code.
Connect is the developer API behind the TelVox platform. Place and receive calls, control them in real time, record and react to lifecycle events — from your own code, on the same compliance-engineered infrastructure that powers Dial. Developer preview.
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"Make your first call
One request places a call.
Send a from, a to and an answer URL. TelVox dials out, and when the callee answers it fetches your answer URL for a call-control document that tells the call what to do next. Status callbacks follow the call through its lifecycle.
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" \
-d 'status_callback=https://your.app/voice/status'// POST https://your.app/voice/answer → 200
{
"instructions": [
{ "play": "https://your.app/audio/welcome.mp3" },
{
"gather": {
"num_digits": 1,
"action_url": "https://your.app/voice/menu"
}
}
]
}Our voice engine, your code
The voice stack that runs Dial — now an API.
Everything Connect exposes is already carrying real call traffic inside TelVox Dial: the dialer, the IVR and ACD engine, the recording pipeline, the SIP and WebRTC paths, the webhook fabric. Connect hands you those primitives directly, so you can build calling into your own product instead of adopting a whole contact center. The REST surface, SDKs and CLI are in developer preview — the engine underneath is not.
The voice primitives
Everything you need to put a call in your app.
The building blocks of the platform, exposed as an API and grouped by what they do. Compose them however your product needs — no contact center required.
Connectivity
Get calls and numbers into — and out of — your application.
Voice API
Place and receive calls from code. One request starts an outbound call; inbound calls hit your answer URL.
SIP & WebRTC
Bring calls in over SIP trunks or connect browser and mobile clients over WebRTC from one API.
Numbersself-serve buy: roadmap
Assign DIDs to your application and rotate caller ID for local presence.
Programmability
Drive calls in real time and react to what happens on them.
Call control & IVR
Play audio, gather digits, route, bridge, transfer, queue — composable instructions, mapped to the real 12-node engine.
Webhooks & events
Subscribe to the call lifecycle; TelVox calls your endpoints as state changes, over signed, SSRF-safe egress.
Messagingpreview
WhatsApp (templated) and email send, grounded in real Dial capabilities. No SMS, MMS, video or fax.
Trust
The compliance engineering that ships with every call.
Recording
Record under policy with AES-256-GCM at rest and short-lived signed URLs for audited retrieval.
Security controls
Org-scoped isolation, append-only audit trail, short-lived JWTs and signed webhook egress — see the controls.
Built on Dial
The same voice engine that runs TelVox Dial, exposed as an API — no new stack to trust.
What people build
Patterns that ship on day one.
Every one of these maps to a capability TelVox already runs in production — no invented AI agents, no SMS, just real voice primitives composed your way.
Interactive voice response
Build menus and self-service flows on the real 12-node IVR engine — play, gather, business-hours, data-dip, queue, transfer — driven entirely from your answer URL.
Call tracking
Assign DIDs per campaign or source, point inbound traffic at your handlers, and attribute every call through the lifecycle webhooks you already wire up.
Programmatic outbound notifications
Trigger an outbound call from your backend, play a message or gather a confirmation, and follow the call to completion over status callbacks.
Embedded WebRTC calling
Mint a short-lived access token server-side and let a browser or mobile client place and take calls in-app — the secret never reaches the client.
Recording for QA
Capture calls with AES-256-GCM envelope encryption, pause and resume on policy, and pull them back through audited, signed-URL playback.
Same infrastructure as Dial
The compliance engineering carries over.
Connect runs on the platform that runs Dial. Built for HIPAA workloads with a BAA available, and engineered to SOC 2 Type II and ISO 27001 controls — certification in progress, never claimed as done.
AES-256-GCM at rest
Envelope encryption for recordings and secrets.
Append-only audit trail
Every access and change is recorded, not editable.
Org-scoped isolation
Tenants are partitioned end to end.
Signed, SSRF-safe egress
Per-org allow-listed webhook delivery.
Grounded in real capabilities
- 9 lifecycle events
- 12 IVR node types
- AES-256-GCM
- SIP + WebRTC
- answer-URL call control
Pricing
Usage-based. Scoped to your volume.
You pay for what you use, across a Pay-as-you-go → Volume → Committed ladder. We size pricing to your call volume and feature mix rather than posting per-minute or per-number rates here — see the model and dimensions, then talk to sales for real numbers.
Questions
Connect FAQ
Connect is the programmable-voice (CPaaS) API in the TelVox platform — the developer-facing sibling of Dial. Where Dial is a ready-to-run contact center, Connect exposes the underlying voice primitives — place and receive, call control, recording, webhooks — so you can build calling directly into your own product.
The capabilities are real and shipped in Dial, but Connect's public REST API is in developer preview, so every code sample here is illustrative — it shows the shape of a request, not a finalized contract. Exact endpoints, fields, enums and SDK names may change before general availability, and helper-library names shown are planned rather than published.
They run on the same compliance-engineered infrastructure: AES-256-GCM encryption at rest, an append-only audit trail, org-scoped tenant isolation, short-lived JWTs and signed, SSRF-safe webhook egress. Connect gives you the API surface; Dial is the full application built on top of the same voice engine.
Connect works over SIP trunks and WebRTC, and assigns DIDs from a number pool to your application with caller-ID rotation for local presence. Today the team provisions numbers and trunk config with you; self-serve number search and purchase, and self-serve BYOC trunk config, are honestly on the roadmap rather than shipped.
You call the REST API with an API key over the Authorization: Bearer header — conceptually a key SID plus a secret. For browser and mobile WebRTC clients, your server mints a short-lived JWT access token with a voice grant and the client consumes it, so the secret never reaches the client. The full model is documented on the authentication concept page.
Pricing is usage-based, and we scope it to your call volume and feature mix rather than publishing per-minute or per-number rates here. See the pricing page for the model and dimensions, then talk to sales to put real numbers against your use case.
Also from TelVox
Run the whole floor on Dial.
Dial is our predictive dialer and cloud contact center for your floor. Browser-first agents, pacing that holds to the 3% abandon ceiling, IVR and queues for inbound, and a command center that shows the numbers live.
- Abandon
- ≤ 3%
- Agents live
- browser-first
Build calling into your product.
Join the developer preview for sandbox credentials and a test number — then make your first call from your own code.