# Recording Transcription

{% hint style="info" %}
Recording Transcription is a supplementary feature of our paid Whereby Embedded plans. You can review the pricing and options [on our site](https://whereby.com/information/embedded/pricing/).
{% endhint %}

## Summary

Recording Transcription is available by default for all session recordings stored in Whereby-provided storage, and there is no need to enable or configure this feature. Recording transcripts are derived from recordings and saved as text files accessible through the Dashboard or via the API. They can be used as a standalone resource (eg. for compliance purposes) or sent to an external service for post processing (eg. to derive key topics or create a session summary).

## Setup

To produce a transcript from a recording of a Whereby session, you need to follow these steps:

1. Create a Whereby room with cloud recording enabled and configured to use Whereby-provided storage.
2. Record the session.
3. Trigger the transcription for the recording.

## How does it work?

You can use Recording Transcription manually through the Dashboard, or programmatically with the combination of API requests and webhook events.

### Manual Transcriptions

In order to use Recording Transcription, you need to first configure meeting recordings to use cloud recording with Whereby-provided storage. Go to the “**Configure**” → “**Recording**” section of your Dashboard and choose the "Whereby-hosted cloud recording" option with the trigger and recording format of your choice. [Learn more about recording options](https://docs.whereby.com/whereby-product-features/recording-with-embedded/cloud-recording).

{% hint style="info" %}
When configuring cloud recording options via the Dashboard, they will be applied as default settings for all rooms and meetings. However, you can override the defaults by specifying different preferences in the POST requests used to create meetings.
{% endhint %}

<figure><img src="https://888889433-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLH2UIJDLc2EElQvYUxWX%2Fuploads%2FYLGXLfIHlR2sckjWvjzT%2Fimage.png?alt=media&#x26;token=49ee3b13-0a61-4618-953d-aca6fdae4627" alt=""><figcaption></figcaption></figure>

When the sessions get recorded, you can access all recordings saved in the Whereby-provided storage from the “**Recordings**” page of your Dashboard. Find the session that you want to transcribe and choose the "**Start transcription**" option from the Actions column.

<figure><img src="https://content.gitbook.com/content/LH2UIJDLc2EElQvYUxWX/blobs/batSjYPcdtLhPEbbVTuM/Screenshot%202023-09-28%20at%2014.00.31.png" alt=""><figcaption><p>Start the transcription for selected recording of a Whereby session</p></figcaption></figure>

The transcription process may take some time, especially for recordings longer than 30 minutes. Once the transcript is ready, you can download it. The transcript is downloaded as an .md file.

<figure><img src="https://content.gitbook.com/content/LH2UIJDLc2EElQvYUxWX/blobs/xLSfSk4UpHPqf0MzPJpp/Screenshot%202023-09-28%20at%2014.06.48.png" alt=""><figcaption><p>Download the transcript from the session recording</p></figcaption></figure>

You can also download or delete transcriptions that have been already created from the “**Recordings**” page of your Dashboard.

### Programmatic Recording Transcriptions

If you want to automate the process of transcribing recorded Whereby sessions, you can do so with a combination of API requests and webhook events.&#x20;

#### Configure session recording

First, make sure that meetings are configured to use cloud recording with Whereby-provided storage:&#x20;

* If you want to use cloud recording with Whereby-provided storage **globally for all rooms**, go to the “**Configure**” → “**Recording**” section of your Dashboard and choose the "Whereby-hosted cloud recording" option with the trigger and recording format of your choice.
* If you prefer to set the **recording type for each room or meeting individually**, create the meeting with a [POST /meetings](https://docs.whereby.com/reference/whereby-rest-api-reference/meetings#post-meetings) request using the following parameters for recording (with the `"startTrigger"` and `"fileFormat"` of your choice):&#x20;

```json
"recording": {
    "type": "cloud",
    "destination": {
      "provider": "whereby",
      "fileFormat": "mp4"
    },
    "startTrigger": "none"
   },       
```

#### Record and transcribe the session

Depending on the type of recording trigger specified for the meeting, it will be recorded automatically, or the host will need to start the recording manually.&#x20;

When the recording is completed, Whereby sends a `recording.finished` [webhook](https://docs.whereby.com/whereby-product-features/insights-suite-and-api/webhooks) event. Hook onto that event to fetch the `recordingId` of the session that you want to transcribe.&#x20;

Then, send a [POST /transcriptions](https://docs.whereby.com/reference/whereby-rest-api-reference/transcriptions#post-transcriptions-bulk-delete) request with the  `recordingId` to start the transcription job.&#x20;

The transcription process may take some time, especially for recordings longer than 30 minutes. Once the transcript is ready, Whereby sends a `transcription.finished` [webhook](https://docs.whereby.com/whereby-product-features/insights-suite-and-api/webhooks) event. Hook onto that event to fetch the `transcriptionId` of the session that you want to transcribe.&#x20;

Send a [GET /transcriptions/{transcriptionId}/access-link](https://docs.whereby.com/reference/whereby-rest-api-reference/transcriptions#get-transcriptions-transcriptionid-access-link) request to get the download link of the transcription file. Transcripts are downloaded as .md files.&#x20;

#### Delete the recording and transcription files

Both the recording and the transcript of the session will be stored in the Whereby-provided storage until you delete them. If you want to optimize the cost or minimize the time when your sessions' content is stored in the Whereby-provided storage, you can delete the assets with 2 API requests:

* [DELETE /recordings/{recordingId}](https://docs.whereby.com/reference/whereby-rest-api-reference/recordings#delete-recordings-recordingid)
* [DELETE /transcriptions/{transcriptionId}](https://docs.whereby.com/reference/whereby-rest-api-reference/transcriptions#delete-transcriptions-transcriptionid)    &#x20;

## Supported Languages

Recording Transcriptions feature automatically identifies the dominant language spoken in the session and creates a transcript in this language. The following languages are supported: Chinese, Dutch, English, French, German, Hindi, Indonesian, Italian, Japanese, Korean, Portuguese, Russian, Spanish, Swedish, Turkish, Ukrainian.

## Known limitations

1. Recording Transcriptions are only available for session recordings stored in Whereby-provided storage. If you store session recordings in your own Amazon S3 bucket, it will be not possible to trigger transcriptions for these recordings.
2. Since recording transcripts are derived from recordings saved in Whereby-provided storage, this feature is not considered to be HIPAA compliant. Avoid using recording transcription in order to maintain HIPAA compliance of your Whereby sessions. [Learn more about Whereby HIPAA compliant setup](https://docs.whereby.com/telehealth-industry-solutions/hipaa-compliant-setup).
3. Recording Transcriptions sometimes fail for recordings of sessions longer than 45 minutes, so it is recommended to use this feature for shorter sessions. We will not charge you for failed transcriptions.&#x20;


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.whereby.com/whereby-product-features/transcribing/recording-transcriptions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.