Skip to main content
The Delete Webhook endpoint allows you to permanently remove webhook endpoints from your application. Once deleted, the webhook will no longer receive events and cannot be recovered. This operation is irreversible, so use it carefully.

Endpoint Details

  • URL: /api/v0/webhooks/{webhook_id}
  • Method: DELETE
  • Authentication: Required (API Key Authentication with Scopes)
  • Content-Type: application/json
  • Required Scope: webhook:delete

Authentication

This endpoint requires API key authentication with specific scopes:

Required Headers

Required Scope

Your API key must have the webhook:delete scope to access this endpoint.

Path Parameters

Response

Success Response (204 No Content)

When a webhook is successfully deleted, the API returns a 204 No Content status with an empty response body. This indicates that the webhook has been permanently removed.

Confirmation Response (200 OK)

Some implementations may return a confirmation response:

Example Requests

Error Responses

Safety Considerations

Irreversible Action: Once a webhook is deleted, it cannot be recovered. All configuration and delivery history will be permanently lost.
Active Deliveries: Deleting a webhook may interrupt pending event deliveries. Consider disabling the webhook first and waiting for pending deliveries to complete.

Pre-Deletion Checklist

1

Verify Webhook ID

Double-check the webhook ID to ensure you’re deleting the correct webhook.
2

Check Dependencies

Verify that no critical processes depend on this webhook for functionality.
3

Review Recent Activity

Check recent delivery events to ensure no important events are in progress.
4

Backup Configuration

Note down webhook configuration (URL, settings) in case you need to recreate it.
5

Inform Team

Notify relevant team members about the webhook deletion, especially if it’s shared.

Alternative Actions

Before deleting a webhook, consider these alternatives:
Temporary Solution: Disable the webhook by setting isActive: false instead of deleting it.
Benefits:
  • Preserves configuration and history
  • Can be easily re-enabled later
  • Safer than permanent deletion
Redirect to New Endpoint: Update the webhook URL to point to a new endpoint.
Use Cases:
  • Moving to a new server
  • Changing webhook implementation
  • Temporary redirects
Export Settings: Save webhook configuration before deletion for future reference.

Batch Operations

Delete Multiple Webhooks

Cleanup Unused Webhooks

Best Practices

  • Always implement a confirmation step for deletion operations
  • Display webhook details before deletion to prevent mistakes
  • Consider requiring additional authentication for bulk deletions
  • Log all webhook deletions for audit purposes
  • Include user information, timestamp, and reason for deletion
  • Maintain deletion logs for compliance and troubleshooting
  • Check for pending deliveries before deletion
  • Consider disabling webhook first, then deleting after grace period
  • Implement proper error handling for deletion failures
  • Export webhook configurations before deletion
  • Store critical webhook settings in version control
  • Document webhook purposes and dependencies

Use Cases

Development Environment Cleanup

Migration Cleanup

  • POST /api/v0/webhooks - Create a new webhook
  • GET /api/v0/webhooks - List all webhooks
  • GET /api/v0/webhooks/{id} - Fetch specific webhook details
  • PATCH /api/v0/webhooks/{id} - Update webhook configuration