Last updated
Was this helpful?
Last updated
Was this helpful?
To know more about how to use signingKeys, please refer to the section .
Let's establish some of our data that will be used in the following examples:
Workspace ID: a1405560-c8d3-4b1a-877d-3f449ad95352
Organization ID: 823fbfaf-f14e-4693-b55a-8ec1c17d649e
AccessKey: abcd
Creating a subscription for events of a specific channel
Creating a webhook subscription and filtering events based on interaction type
Creating a webhook subscription without filtering
In this example, we're sending event notifications for each sent message by the specified channel. To know more about valid events for each platform (e.g. SMS, E-mail), please refer .
This will send notification events to the specified webhook URL when an e-mail sent by the specified channel is opened by end-customers. To know more about all supported interactions, refer to
This will send notification events to the specified webhook URL for all email interactions. To know more about all supported interactions, refer to
To start receiving notifications via webhooks, the first step is to create a subscription. A webhook subscription specifies the destination URL for events and defines how they should be filtered. During setup, you can select which events to send to the specified URL. You can create multiple webhook subscriptions to route different types of events to various URLs as needed. Event filters are applied using AND operators, meaning that all specified criteria must be met for an event to be sent. If you want to handle multiple interactionTypes, you’ll need to create separate webhook subscriptions for each.
The ID for the workspace.
b4e02c85-c6d2-4b15-8885-e09671799c61
The ID for the organization.
cb28a94e-8557-4394-80ea-5bbd2170d434