Service Cloud Voice Implementation Guide
Summer '26 (API version 67.0)
Spring '26 (API version 66.0)
Winter '26 (API version 65.0)
Summer '25 (API version 64.0)
Spring '25 (API version 63.0)
Winter '25 (API version 62.0)
Summer '24 (API version 61.0)
Spring '24 (API version 60.0)
Winter '24 (API version 59.0)
Summer '23 (API version 58.0)
Spring '23 (API version 57.0)
Winter '23 (API version 56.0)
Summer '22 (API version 55.0)
Spring '22 (API version 54.0)
Winter '22 (API version 53.0)
Summer '21 (API version 52.0)
Spring '21 (API version 51.0)
Winter '21 (API version 50.0)
Summer '20 (API version 49.0)
Newer Version Available
Using the Telephony Integration REST API
The Telephony Integration REST API allows you to programmatically manage a voice call.
The provided Amazon Connect Lambda functions automatically use these endpoints to perform
telephony functions, but you can also use these APIs separate from the provided Lambda
functions.
-
Create VoiceCall
Creates a VoiceCall record containing the participants (that is, the caller and recipient) for the VoiceCall. When you create a VoiceCall record, it creates a conversation in Salesforce. Only use this API in a real-time context, which means that you should invoke this API only when a call is initiated. -
Post-Call Update
Updates the VoiceCall after the call has ended. Use this API to update call-related parameters that are unavailable during the VoiceCall creation stage. -
Create Transcript
Creates a transcript during a call. Transcripts can be saved to a conversation. You can create transcripts using this API only for an ongoing call. If the call has ended, you can no longer create transcripts. -
Execute OmniFlow (Beta)
Executes the Omni-Channel flow to route calls. It passes the call ID (Salesforce VoiceCallId or telephony vendor ContactId) as parameters to the flow and returns the agent or queue routing instructions to the contact flow. By default, Service Cloud Voice uses the Omni-Channel flow (or fallback queue) specified for the phone channel that matches the dialed number. If the dialed number doesn’t match an existing phone channel, you can optionally set a new dialed number, Omni-Channel flow, and fallback queue as input parameters to this API call. -
Telephony Integration REST API Sample Code
The following JavaScript code sample performs the authorization process and then invokes the Voice API. -
Telephony Integration REST API Authorization
The Telephony Integration REST API requires JWT authorization. Usually, the provisioning process already sets up this authorization for you. This content simply provides instructions in case you must manually set up this authorization.