Skip to main content

​
Mutations

​
deleteWebhookSubscription

Removes an existing WebhookSubscription by its identifier. After deletion, the system no longer sends event to the associated endpoint for that subscription.
  • The API user context must have AUTHENTICATED scope to access webhook subscriptions. Anonymous users cannot retrieve this data.
  • The API user context must have permission to delete webhook subscriptions.
  • The API user context must be present and valid - otherwise, access is denied.
The following arguments can be used in the mutation:
ArgumentTypeDescription
idID!The ID of the webhook subscription to delete.
mutation deleteWebhookSubscription {
  deleteWebhookSubscription(id: 98) {
    response
    errors
  }
}
The deleteWebhookSubscription mutation supports the same advanced features as other mutations:

Authentication

Understand the authentication requirements and how to properly authenticate your requests.
Common error scenarios and solutions:
  • 401 Unauthorized: Ensure you’re using a valid authentication token with AUTHENTICATED scope
  • 403 Forbidden: Verify your user account has the necessary permissions to access webhook subscription data