The link to the redacted audio file.
The status of your transcription. queued, processing, completed, or error
or
The status of the redacted audio file. redacted_audio_ready
The unique identifier of your transcription.
Generated using TypeDoc
Instead of polling for the result of your transcription, you can receive a webhook once your transcript is complete, or if there was an error transcribing your audio file.
Specify Your Webhook URL
When submitting an audio file for transcription, you can include the additional parameter
webhook_urlin your POST request. This must be a URL that can be reached by our backend.Receiving the Webhook
You'll receive a webhook when your transcription goes to status
"completed", or when your transcription goes to status"error". In either case, aPOSTrequest will be made to the webhook URL you supplied. The headers and body will look like this:Once you receive the webhook, you can make a
GETrequest to/v2/transcriptto fetch the final result of your transcription.Including Custom Parameters in Your Webhook Request
Often times, you'll want to associate certain meta data with your transcription request, such as a customer ID, and have that passed back to your webhook. The easiest way to do this is to include these parameters in your webhook URL as query parameters, for example:
Then, when you receive the webhook, you can parse these parameters out of the webhook URL.
Failed webhooks and retries
If we get a non
2xxresponse when wePOSTto your webhook URL, we'll retry the request 10 times, with a 10 second interval between each retry. After all 10 retries fail, we'll consider the webhook to be permanently failed.If we are unable to reach your webhook URL (usually caused by a timeout, or your server being offline), no retries will be attempted.
Audio Redaction
If a
webhook_urlwas provided in yourPOSTrequest when submitting your audio file for transcription, we will send aPOSTto yourwebhook_urlwhen the redacted audio is ready. ThePOSTrequest headers and JSON body will look like this: