📘
Permission Issue?
Please see our section on webhook permissions, to see if its a token issue. Please feel free to reach out to us at our support page for additional help.

Event Order

It is possible for webhooks to come out of order, so ensure you are putting some basic protections in place in your consumption logic. For example, if you see that a records is in a 'final' state, then you will want to reject additional updates from events that are from an earlier state.

Data Context

To know what data to send to you, your token must have enough information to describe 'who' you are. Please review the webhook permissions section if your request is not working or you are getting to much or too little information.

Scopes

To ensure that webhooks are not used to circumvent read permissions, you must have not only the subscriptions:read scope when creating a subscription, but you must have the read permissions on the target resource being subscribed to. For example, when trying to create a subscription to conversations, you would need to have a scope statement of conversations:read subscriptions:read.