Dolby.io Real-time Streaming uses Webhooks to notify your application when an event happens in your account. A webhook enables Dolby.io Real-time Streaming to push real-time notifications to your app.
To get started, log into your Dolby.io Real-time Streaming account and select Webhooks from the left menu. Here you can create and manage your Webhooks.
You can create a new Webhook by pressing the Add (+) button. This will open a popup window on your screen containing various options for your new Webhook.
In the Webhook url field you can specify the Webhook callback url. This url is where Dolby.io Real-time Streaming will notify your application about an event.
After writing your callback url, you can select which type of events you want to receive. There are 2 types Feed hooks and Recording hooks:
- Feed hooks notifies you about when a stream has been published or stopped publishing. You can learn more in Feeds hooks.
- Recording hooks will notify about the life cycle of a stream recording. You can learn more in Recording hooks.
Once created you can see your webhooks in a scrollable list.
From this screen you can either delete the webhook by pressing the Delete Button, or open the management screen by clicking the row or also the arrow on the right.
The management screen allows you to edit and view details attached to your Webhook including Webhook url, type of hook enabled, Webhook secret and delete.
You can edit the url of the webhook by pressing the pen icon at the end of the row:
After pressing the button you can modify the url and confirm your decision by pressing either the Cancel Button or Confirm Button:
The Webhook Secret is used to ensure your server is only receiving the expected Dolby.io Real-time Streaming requests for security reasons.
You can renew this secret by pressing the Renew button. You can use this if you think the original webhook secret was compromised.
This cannot be undone. Once you have renewed the Webhook secret, the old one is gone. Please be sure you want to renew the Webhook secret before proceeding.
More information of the API here.
Updated 5 months ago