Subscribing to Events

By default, a webhook callback is triggered on any event happening within the realm of the organization for which the webhook was created (or any of its sub-organizations). By specifying the params.events property when configuring the webhook, it can subscribe to specific events.

Still, we would like to encourage you to have a single webhook URL subscribe to the events you need, and do further event filtering from there.

Wildcard Subscriptions

When configuring a webhook, you can use wildcards (an * asterisk) to denote a set of events. Examples:

Subscription	Description
message.create.contact.*	A message was created in a contact conversation
message.create.*.results	A results message was created in a conversation
message.*	A message in a conversation was created, updated or deleted.
organization.*	A conversation was created, updated or deleted
*.update	A resource was updated

A wildcards can only be used to replace an entire word in an event subscription.