TelVox · Connect
What's changing in the preview.
A running log of the Connect developer-preview API — versioned v0.x. The capabilities underneath are real and shipped in Dial; what changes here is the public API surface we're exposing them through.
Connect is in developer preview, so the API is versioned in the v0.x range and breaking changes are possible before general availability. Entries are tagged by version, not by calendar date. Every API artifact referenced below is illustrative — see the API reference for current shapes.
Release history
Preview releases.
Newest first. Each version notes what was added, changed or deprecated as the preview API took shape.
- v0.7
Access tokens for WebRTC clients
- AddedPOST /v1/access-tokens mints a short-lived JWT with a voice grant so a browser or mobile client can place and receive calls — the API secret never reaches the device.
- AddedDocumented the server-mints / client-consumes model, grounded in the real single-use token rotation and JsSIP WebRTC softphone already shipped in Dial.
- v0.6
Conferences & queues reference
- AddedConference resource with a participants subresource — add, remove, hold and mute — over the real ARI snoop/bridge engine.
- AddedACD queue resource with a members subresource, surfacing the shipped Redis-backed FIFO / longest-idle queue, MOH, maxWait/maxSize and overflow.
- ChangedConference docs no longer imply a participant ceiling — the platform does not cap participants, so none is advertised.
- v0.5
Webhooks & events subscription API
- AddedSubscription endpoints over the 9 real lifecycle events (web-form, call-start, hangup, no-agent, disposition, callback, queued, abandoned, voicemail-left), with custom headers, JSON payload templates, retries and encrypted secrets.
- AddedDocumented per-org host allow-listing (the SSRF guard) and signed delivery for every webhook.
- Changedstatus_callback event names aligned to initiated / ringing / answered / completed across the calls and recordings docs.
- v0.4
Recording resource & signed-URL retrieval
- AddedRecording resource with fetch/list/delete and a RecordingStatusCallback (in-progress / completed / absent / failed), grounded in the real AES-256-GCM pipeline.
- AddedDocumented recording modes (always / on_demand / never) with pause/resume, S3 / local / SFTP backends, wav→mp3 and audited signed-URL playback.
- v0.3
Numbers & SIP/WebRTC docs
- AddedPhoneNumbers (IncomingPhoneNumber) reference for listing assigned numbers and setting an answer URL and caller-ID rotation strategy.
- AddedSIP trunking and WebRTC capability pages, with live MOS / codec / transport metrics surfaced from the real softphone.
- DeprecatedMarked self-serve number search and purchase, and self-serve BYOC trunk config, as roadmap — numbers and trunks are provisioned with the team during the preview, not bought via API.
- v0.2
Call control via the answer URL
- AddedDefined the primary call-control model: your answer_url returns a JSON call-control document with play / gather / dial / record / hangup instructions.
- AddedMapped the instruction set to the real 12-node IVR engine, including the api_call data-dip node for branching on an external API mid-call.
- DeprecatedScoped the XML call-control markup dialect to roadmap only — the JSON answer-URL model is the supported path for the preview.
- v0.1
Developer preview — first cut
- AddedBase URL https://api.telvox.dev with flat resource paths (/v1/calls, /v1/recordings, …) and API-key bearer auth.
- AddedCalls resource — create an outbound call (from / to / answer_url / status_callback), fetch, list and modify in-progress — over TelVox's real place/receive engine with AMD, alternate-number failover and caller-ID/DID rotation.
- ChangedAdopted the developer-preview honesty convention: every endpoint, field, enum and JSON sample is stamped illustrative — shape may differ at GA.
Track the preview.
Join the developer preview and we'll flag breaking changes before they land. A machine-readable index lives at /connect-llms.txt.
Build on the preview, shape the GA.
Join the developer preview, make your first call, and tell us where the API should go before it's locked in.