Problem description

In the subscriptions API, the error 403 SUBSCRIPTION_MISMATCH of the Create operation is returned when the access token has been granted with a scope that allows to create a subscription for an event but, in the request body, the client requests a subscription for a different one.
This is fine in APIs where there is more that one event to subscribe to but here, since we only have one, if the token lacks the scope, the error returned would be 403 PERMISSION_DENIED instead.

Expected behavior

Remove error 403 SUIBSCRIPTION_MISMATCH

Alternative solution

Open to suggestions