Create Web Call v2 is deprecated
Deprecation date: 09/30/2026POST /v2/create-web-call will be deprecated on September 30, 2026 in favor of
POST /v3/create-web-call. Existing
integrations continue working during migration. Upgrade your browser JavaScript SDK and update
how your integration creates calls.
Upgrade the browser SDK
Upgrade to the latest browser SDK:/v2/create-web-call. The SDK’s RetellWebClient compatibility class continues
to accept v2 tokens in 3.x.
Replace call creation and connection
Replace the request to your server andRetellWebClient.startCall() with
RetellClient.createWebCall(). The SDK sends the v3 request and connects audio
automatically.
Create a public key and allow your website’s domain
(localhost for local testing). Keep API keys on your server. If reCAPTCHA is
enabled for the public key, pass a fresh token as recaptchaToken with each call.
Add call controls to your page:
app.js
localhost, click Start call, and allow
microphone access. Talk to the agent, then click End call. The session ends
and fires onEnd. See the web call guide for audio controls
and live transcripts.
Migrate server-created calls
If you retain an existing server-created call flow, upgrade both your server SDK and browser SDK. The server SDK’s web-call creation method now uses v3 and returns connection details instead of the full call object. If you make HTTP requests directly, switch toPOST /v3/create-web-call with the same JSON body.
Upgrade the browser SDK before switching the server to v3. For an existing
RetellWebClient integration on SDK 3.x, forward these fields to startCall():
Use get call if your application needs call fields
such as
call_status, agent_id, or metadata after creation.
Update event handlers
Calls created through v3 do not deliver every event from the previous connection type. Audit handlers as well as call creation:
See the web call guide for supported hooks,
transcript authentication, and
audio options.

