Data Context

The token being used to make the request, will determine the granularity of the data that will be broadcast on the subscription. A parter for example will be able to see data across many merchants, where as a merchant will only be able to view their own record, and sub customer/conversation records.

As a result, to be able to subscribe to a webhook, the token being used must have read access to that data. So, you could not for example, create a customer subscription with a token that does not have customer:read on it.

Scopes

To ensure that a requestor cannot use webhooks to view data they do not have access to, when making a request to create a webhook you must have the appropriate :read access on the token at the same time. For example, when creating a subscription to conversations you must have both subscriptions:create and conversations:read on the token.