Transcripts from live events in real-time
The live transcript dataset access allows you to access live text transcripts from events. The dataset is updated in real-time as new transcripts become available.
Our API provides support for live transcript streaming using JSON Lines (jsonl) format. When making a live transcript request, the API returns a URL that streams live transcript data in jsonl format. An example snippet of the data is shown above. There are a couple of different record types in the stream:
start: This should be the first record in any file. All other keys are meta data for the stream and could be empty.
entry: This is the default and most common record type and comes after the start. If no type is specified, it should be assumed that it is of this type. It contains the following
keep-alive: This can be sent at any point to indicate that the stream is still going, but nothing is necessarily being said. Clients should ignore these unless they have some logic for stand-off or similar. In practice this will rarely if ever be sent, but rather a file will be regarded active as long as it has not been closed.
end: Indicates an end. Nothing can be added to a file after this. If this exists or appears in the file during the stream, clients should stop polling. It can, but does not have to contain meta data. If it does not contain meta data, like below, then a successful exit should be assumed.
interruption: Something went wrong with the live transcription, the restart will be attempted 3 times.
true
indicating a restart, false
indicating the live transcription can’t be recovered.section: A section delimiter, displays the start or end of some section.
predicted-qna
and predicted-speech
.The API allows you to query the live transcript dataset using a variety of parameters, such as ticker, ISIN, and date and more. You can also use the API to retrieve a list of all live transcripts available in the dataset. For more information on how to use the API, see the API reference.
If you have a subscription to both the audio and transcript live datasets, you can retrieve both the Live Audio and transcript data simultaneously using the Live endpoints.
The data is served through a global CDN, ensuring low latency and high availability. The URL is unique to each live transcript stream and customer. It should not be shared with others or altered in any way as it may result in a loss of access.
Explore the Live Transcripts API endpoints.
Below is an example of how to consume a live transcript. The same example is also available at CodePen. Just make sure to replace the transcriptUrl
with your own.
Transcripts from live events in real-time
The live transcript dataset access allows you to access live text transcripts from events. The dataset is updated in real-time as new transcripts become available.
Our API provides support for live transcript streaming using JSON Lines (jsonl) format. When making a live transcript request, the API returns a URL that streams live transcript data in jsonl format. An example snippet of the data is shown above. There are a couple of different record types in the stream:
start: This should be the first record in any file. All other keys are meta data for the stream and could be empty.
entry: This is the default and most common record type and comes after the start. If no type is specified, it should be assumed that it is of this type. It contains the following
keep-alive: This can be sent at any point to indicate that the stream is still going, but nothing is necessarily being said. Clients should ignore these unless they have some logic for stand-off or similar. In practice this will rarely if ever be sent, but rather a file will be regarded active as long as it has not been closed.
end: Indicates an end. Nothing can be added to a file after this. If this exists or appears in the file during the stream, clients should stop polling. It can, but does not have to contain meta data. If it does not contain meta data, like below, then a successful exit should be assumed.
interruption: Something went wrong with the live transcription, the restart will be attempted 3 times.
true
indicating a restart, false
indicating the live transcription can’t be recovered.section: A section delimiter, displays the start or end of some section.
predicted-qna
and predicted-speech
.The API allows you to query the live transcript dataset using a variety of parameters, such as ticker, ISIN, and date and more. You can also use the API to retrieve a list of all live transcripts available in the dataset. For more information on how to use the API, see the API reference.
If you have a subscription to both the audio and transcript live datasets, you can retrieve both the Live Audio and transcript data simultaneously using the Live endpoints.
The data is served through a global CDN, ensuring low latency and high availability. The URL is unique to each live transcript stream and customer. It should not be shared with others or altered in any way as it may result in a loss of access.
Explore the Live Transcripts API endpoints.
Below is an example of how to consume a live transcript. The same example is also available at CodePen. Just make sure to replace the transcriptUrl
with your own.