Integrate the Transcription Viewer App

To follow along with this guide, you should have the following elements set up and ready to use:

• Twilio account credentials, specifically your Account SID and your Auth Token, which you can get from the Console .
• A configured Voice Intelligence Service.
• The SID of your Service.
• Access to transcripts that you would like to view.

Each time you wish to initialize and present the Transcription Viewer, you need to:

1. Fetch the SID of the transcript you would like to present.
2. Use your Account SID, Auth Token, and some metadata from the transcript to acquire a one-time token.
3. Pass the one-time token as a URL query parameter to initialize the Transcription Viewer.

Let's run through each of these steps now.

There are a number of ways that you can acquire the SID of the transcript you'd like to view, so choose the one that best fits your application.

If your application already has a call SID, you can look up the transcript SID by passing the call SID as a URL query parameter, callSid. This will narrow the search down to the transcript generated by that call.

Look under EXAMPLE JSON RESPONSE in the code column to the right. The returned data contains the key transcripts whose value is an array containing, in this case, one JSON object. The value of the object's sid key is the transcript SID you need. It starts with GT.

If you don't have a call SID, you can make the same request described above, but without the callSid query parameter. This will return all your transcriptions, so you need to be able to identify the one you want so you can extract its SID.

Again, under EXAMPLE JSON RESPONSE for the code sample, the returned data contains a transcripts key whose value is an array containing, in this case, a single JSON object (for a single transcription). The value of the object's sid key is the transcript SID you need, starting with GT.

To use this option, you'll need the URL of your web service that listens for GET or POST requests. When you make the following API call, it causes a request to be made to your URL — the one set as the value of the WebhookUrl parameter — whenever a transcription task completes. You'll find the transcript SID in the JSON data sent to your URL.

Each Transcription Viewer session requires a new one-time token. This is a short-lived, single-use key that is used to authorize Transcription Viewer to access the transcript.

You request the one-time token by making a call to the endpoint:

You use your Twilio Account SID and Auth Token to authorize the request, which is submitted as JSON. The JSON includes a grants array containing an object. This object must include your service SID and the transcript SID as key-value pairs. Check out the examples below to see how the request body JSON is formatted.

In addition to service and transcript SIDs, you can include a user ID in the one-time token request's metadata section. This is optional. The user SID should be used to identify the user who will be opening the Transcription Viewer. This usage is shown in the examples below.

You can also choose to have Transcription Viewer display a button which, when clicked, allows the Agent to download the audio from which the transcript was made. To add this button, include an isDownloadButtonVisible key in the one-time token request's metadata section and set its value to true. Again, this is shown in the examples below.

You may also specify a custom token expiry period, called a TTL (Time To Live). The default value is one minute, and that's what's applied to the first of the following examples. The second example sets a TTL of 10 minutes (600 seconds) by adding an ott_ttl field to the request body.

With this data, you can acquire a one-time token. The basic structure of the request is shown below. The request JSON also includes a mandatory product field — this indicates the app you're requesting the token for. Please use annotator as its value.

Once you've acquired a one-time token, pass it as a URL query parameter with your request for Transcription Viewer. The latest build of Transcription Viewer is available here:

To request Transcription Viewer with the one-time token, just add a token parameter to the URL as follows:

This assumes your token is stored in an environment variable called $TOKEN. You can now use this URL directly, or via an iframe in your web page HTML, as the following examples show.

If your app will present Transcription Viewer in its own window, your application should open a new window and load its contents with the latest Transcription Viewer build, as shown above. Make sure you include the one-time token as a URL query parameter.

You might, for instance, choose to have your service redirect to this URL right after acquiring the token.

The entire flow might then be:

1. An Agent views a UI with a list of transcripts to view.
2. The Agent selects a transcript. This triggers a request to a backend service propagating the transcript SID and the service SID.
3. The backend service reads these SIDs from the request and uses locally-stored Twilio account credentials to generate a one-time token.
4. The backend service redirects the browser to the latest Transcription Viewer build with the token appended to the app's URL.

The Transcription Viewer can be embedded in an HTML iframe. To do so, add the URL and appended token to the iframe markup like this:

To achieve this, your server will likely need to retrieve and then dynamically embed the token into the HTML.

The entire flow might then be:

1. An Agent views a UI with the list of transcripts to view.
2. The Agent selects a transcript. This triggers a request to a backend service propagating the transcript SID and the service SID.
3. The backend service reads these SIDs from the request and uses locally stored Twilio account credentials to generate a one-time token.
4. The backend service renders an HTML page that contains the iframe snippet above.

What is a one-time token?

The one-time token (OTT) is used internally by the Transcripiton Viewer app to acquire a fully privileged access token for use during the lifetime of a search operation. It is short lived — approximately one minute — and can be used once only. It's purpose is to avoid embedding a fully privileged access token in client-side code.

How is token refresh handled?

Token refresh is not supported during preview. The one-time token is exchanged for a token with a time to live of one hour.