Comment on page
Transcribing sessions
Transcribing allows you to get a verbatim transcript of what was said in the Whereby meeting.
Transcriptions are derived from session recordings stored in Whereby-provided storage and saved as text files accessible through the customer portal 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).
In order to produce a transcript from 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
You can use Whereby transcriptions manually through the customer portal, or programatically with the combination of API requests and webhook events.
In order to use Whereby transcriptions you need to first configure meeting recordings to use cloud recording with Whereby-provided storage. Go to “Configure” → “Recording” section of your customer portal and choose "Whereby-hosted cloud recording" option with the trigger and recording format of your choice. Learn more about recording options.
When configuring cloud recording options via the customer portal, 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.
Set "Whereby-hosted cloud recording" as Recording option
When the sessions get recorded, you can access all recordings saved in the Whereby-provided storage from the “Recordings” page of your customer portal. Find the session that you want to transcribe and choose the "Start transcription" option from the Actions column.
Start the transcription for selected recording of a Whereby session
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.
Download the transcript from the session recording
You can also download or delete transcriptions that have been already created from the “Recordings” page of your customer portal.
If you want to automate the process of transcribing Whereby meetings, you can do so with a combination of API queries and webhook events.
First make sure that meetings which should be transcribed are configured to use cloud recording with Whereby-provided storage:
- If you want to use cloud recording with Whereby-provided storage globally for all rooms, go to “Configure” → “Recording” section of your customer portal and choose "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 POST /meetings request using the following parameters for recording (with the
"startTrigger"and"fileFormat"of your choice):
"recording": {
"type": "cloud",
"destination": {
"provider": "whereby",
"fileFormat": "mp4"
},
"startTrigger": "none"
},
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.
When the recording is completed, Whereby sends a
recording.finished webhook event. Hook onto that event to fetch the recordingId of the session that you want to transcribe. 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 event. Hook onto that event to fetch the transcriptionId of the session that you want to transcribe. Send a GET /transcriptions/{transcriptionId}/access-link request to get the download link of the transcription file. Transcripts are downloaded as .md 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 optimise the cost or minimise the time when your sessions' content is stored in the Whereby-provided storage you can delete the assets with 2 API requests:
Last modified 1mo ago