telvox
API keys

TelVox Connect · Live

Voice calls,one POST away.

Voice calls, one POST away.

The voice engine that runs regulated call floors, opened up for your code. Send one request and a phone rings. Your server decides what the call does next.

Get API keysRead the docs
GET /v1/calls/call_9f2b81live
{
"id": "call_9f2b81",
"direction": "outbound",
"to": "+14155550199",
"status": "queued",
"duration": null
}

Webhooks, POSTed to your server

  • call.queued10:42:01200

Illustrative payload · v0.x

POST /v1/calls

The whole product, in five steps.

Your backend sends one request and a phone somewhere starts ringing. When it answers, your app replies with a small call-control document, and its verbs (play, gather, dial) drive the live call. That is Connect, end to end.

  1. 1Your code asks for a call
  2. 2TelVox dials the number
  3. 3The customer answers
  4. 4Your app replies with a document
  5. 5The document drives the call
your terminal
$

call.status: idle

playgreeting playsgathercaller pressed 1dialbridged to an agent

Code samples are illustrative while the API is v0.x; the exact contract may change before general availability.

What you can build

Real patterns, running today.

Every one of these maps to a capability the engine already runs in production. No invented AI agents, no SMS. Voice primitives, composed your way.

Phone menus and IVR

Build menus and self-service flows on the same 12-node IVR engine that runs live call floors. Play audio, gather digits, check business hours, dip into your data, queue and transfer, all driven from your answer URL.

Call tracking

Give every campaign or source its own number, point inbound calls at your handlers, and attribute every call through the lifecycle webhooks you already wire up.

Outbound notifications

Trigger a call from your backend, play a message or gather a confirmation, and follow it to completion over status callbacks.

Calling inside your app

Your server mints a short-lived access token, and a browser or mobile client places and takes calls in-app over WebRTC. The secret never reaches the client.

Recording for QA

Capture calls with AES-256-GCM encryption, pause and resume on policy, and pull recordings back through audited, signed-URL playback.

Something else?

The primitives compose. Start with the quickstart and see how far one answer URL takes you.

Open the quickstart

How it works

Three steps to a live call.

01

Get a number

Grab an API key and a number. The team provisions numbers with you today; self-serve number purchase is on the roadmap.

02

Point an answer URL at us

Tell Connect where your server lives. When a call starts, we POST to your answer URL and wait for instructions.

03

Your markup runs the call

Respond with a simple JSON document: play, gather, route, bridge, record. The engine executes it and streams every event back to your webhooks.

Switching or evaluating

Coming from Twilio, Telnyx, or Plivo?

Then most of Connect will already feel like muscle memory. Here is the honest picture.

What will feel familiar

  • A REST API and webhooks

    Place a call with one POST. Lifecycle events land on your endpoints as they happen.

  • Markup that scripts the call

    Your answer URL returns a call-control document that plays, gathers, routes and bridges. The same idea as the XML flows those platforms use.

  • Per-usage pricing

    You pay for what you use, on a ladder from pay-as-you-go to volume to committed.

  • SDKs for your language

    Helper libraries and a CLI for the usual languages, in preview while the v0.x surface firms up.

What is different

  • Voice only, by design

    No sprawling product catalog that also spans SMS, video and email. Connect does calls, and does them properly. Messaging is on the roadmap, framed as a preview.

  • Compliance is heritage, not an add-on

    The engine already runs regulated dialing floors in production. Encryption at rest, append-only audit trails and tenant isolation were built for those floors first; Connect inherits them.

  • Pricing scoped with a human

    No rate-card maze. We size pricing to your call volume and feature mix together, then you know exactly what you pay for.

  • You talk to the team that built it

    Your questions go to the engineers behind the engine, not a ticket queue.

Comparison reflects public positioning, not a feature-for-feature audit.

The platform

Every primitive, one engine.

Each capability has its own page. All of it runs on the same infrastructure that powers TelVox Dial.

Voice API

Place and receive calls from code. One request starts an outbound call; inbound calls hit your answer URL.

Call control & IVR

Play audio, gather digits, route, bridge, transfer, queue. Composable instructions mapped to the real 12-node engine.

Dynamic SIP trunking

Spin up SIP trunks self-serve, and 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.

Recording

Record under policy with AES-256-GCM at rest and short-lived signed URLs for audited retrieval.

Webhooks & events

Subscribe to 9 lifecycle events. 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.

Security controls

Org-scoped isolation, append-only audit trail, short-lived JWTs and signed webhook egress.

Built for HIPAA workloads with a BAA available. Engineered to SOC 2 Type II and ISO 27001 controls; certification is in progress, never claimed as done.

AES-256-GCM at restappend-only audit trailorg-scoped isolationsigned, SSRF-safe egress9 lifecycle events12 IVR node types

Pricing

Usage-based. Scoped to your volume.

You pay for what you use, across a ladder from pay-as-you-go to volume to committed. We size pricing to your call volume and feature mix instead of posting per-minute rates here. See the model, then talk to the team for real numbers.

View pricing

Build calling into your product.

Sign up for sandbox credentials and a test number, then make your first call from your own code.

Get API keysRead the docs

Questions

Straight answers, caveats included.

What Connect is, what is shipped, and what is honestly still on the roadmap.

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, so you can place and receive calls, control them in real time, record them and react to lifecycle events from your own product.