Skip to main content
webhooks:write The webhooks:write scope allows you to manage webhook subscriptions — create new subscriptions, update existing ones, delete them, and send test pings. Webhooks deliver real-time event notifications to your server via HTTPS POST requests with HMAC-SHA256 signatures.

Endpoints


Create webhook subscription

Creates a new webhook subscription. The response includes a secret used for HMAC-SHA256 signature verification. Store this secret securely — it is only returned once at creation time.

Request body

See Webhook Events for all available event types.

Available event types

Example

Response — 201 Created

The secret is only returned when the webhook is created. Store it securely. You will need it to verify webhook signatures. See Webhook Verification for details.

Status codes


Update webhook subscription

Updates an existing webhook subscription. You can change the URL, event list, or active/inactive status. Only include the fields you want to change.

Path parameters

Request body

Example — Update URL and events

Response — 200 OK

Example — Disable a webhook

Response — 200 OK

Status codes


Delete webhook subscription

Permanently deletes a webhook subscription. This action cannot be undone.

Path parameters

Example

Response — 204 No Content

No response body.

Status codes


Send test ping

Sends a test test.ping event to the webhook URL. The test delivery is performed synchronously and the response includes the HTTP status and body from your endpoint.

Path parameters

Request body

No request body is required.

Example

Response — 200 OK (delivery successful)

Response — 200 OK (delivery failed)

The webhook must be active and subscribed to the test.ping event for the test to succeed. If the webhook is inactive, a 400 Bad Request error is returned.

Status codes


Error response — Missing scope

If your API key does not include webhooks:write, any request to these endpoints returns:
Last modified on June 30, 2026