Developers or admins can subscribe to event notifications for various supported live events.
Call, SMS, contact, and status events. See child pages to the left.
To consume events, you must first build an HTTP service on the public internet. Once you have built your service, you will create an event subscription using Dialpad's API. Creating the subscription will require a URL to your HTTP service.
For details on the APIs used to create event subscriptions, see the event subscription section of our API reference.
Secret and event encoding
For security reasons, events are sent in the JWT format (https://jwt.io/) and signed with a secret that you share with Dialpad. This allows you to verify that the event came from Dialpad's system. After verifying and decoding the JWT, you'll have access to the JSON event data in the JWT's payload.
Note: The secret is different than your public API key. You will need to generate a secure string to use as the secret when you create the event subscription. Dialpad recommends that you use a unique string for each subscription to help mitigate the impact if that string was somehow leaked.
Updated over 1 year ago