Webhooks

If the optional notification_config parameter is provided, the API will make an HTTP POST request to the URL specified in that parameter with details in the request body when the job either completes successfully or fails.

To use a webhook URL with restricted access, authorization headers can also be provided in the notification_config parameter.

Details on using the notification_config parameter can be found on the submission details page.

Here is an example of the POST request body sent after a successful transcription job:

Copy
Copied
{
  "job": {
    "id": "Umx5c6F7pH7r",
    "status": "transcribed",
    "created_on": "2018-05-05T23:23:22.29Z",
    "duration_seconds": 356.24,
  }
}

Here is an example of the POST request body sent after a failed transcription job:

Copy
Copied
{
  "job": {
    "id": "Umx5c6F7pH7r",
    "status": "failed",
    "created_on": "2018-05-05T23:23:22.29Z",
    "failure": "download_failure",
    "failure_detail": "Failed to download media file. Please check your url and file type"
  }
}
attention
  • The API will make a POST request, not a GET request, to the notification_config.url parameter. The request body will contain the job details.
  • You can unsubscribe from a webhook by responding to the webhook request with a 200 response code.
  • If a webhook invocation does not receive a 200 response, Rev AI will retry the callback URL every 30 minutes until either 24 hours have passed or a 200 response code is received.

Good third-party tools for webhook testing are Webhook.site and RequestBin.

Learn the basics of webhooks and then see an example of sending email notifications on job completion with webhooks.