Skip to main content
DELETE
/
webhooks
/
{id}
Delete webhook
curl --request DELETE \
  --url https://xquik.com/api/v1/webhooks/{id} \
  --header 'x-api-key: <api-key>'

Documentation Index

Fetch the complete documentation index at: https://docs.xquik.com/llms.txt

Use this file to discover all available pages before exploring further.

Free - does not consume credits
curl -X DELETE https://xquik.com/api/v1/webhooks/15 \
  -H "x-api-key: xq_YOUR_KEY_HERE" \
  | jq --arg webhook_id "15" '{
    webhook_id: $webhook_id,
    success,
    inventory_endpoint: "/api/v1/webhooks",
    deliveries_endpoint: ("/api/v1/webhooks/" + $webhook_id + "/deliveries")
  }'
These snippets shape a deactivation receipt. Store the webhook ID with its inventory and delivery-log endpoints instead of printing the raw delete response.

​
What delete does

DELETE /webhooks/{id} soft-deactivates the endpoint by setting isActive to false. The webhook record stays available in List Webhooks, and previous delivery rows stay available in List Deliveries. The response is only { "success": true }; it does not return the URL, event types, or signing secret. To receive events again, call Update Webhook with isActive: true, then run Test Webhook before routing production monitor events to the receiver.

​
Path parameters

​
id
string
required
The webhook ID to deactivate.

​
Headers

​
x-api-key
string
required
Your API key. This endpoint also accepts session cookie authentication.

​
Response

​
success
boolean
Always true on successful deactivation.
{ "success": true }
The webhook is deactivated immediately. Pending deliveries that are already in-flight may still be attempted, but no new deliveries will be queued.

​
Deactivation handoff

Use this endpoint when a receiver should stop getting future monitor events but you still need the webhook record and delivery history for audit or rollback.

Soft Deactivate

The endpoint sets isActive to false and returns { "success": true }. It does not return the webhook configuration.

Future Deliveries

Inactive webhooks do not receive new monitor deliveries or scheduled retries. In-flight delivery attempts may still finish.

Audit Trail

Use List Webhooks to confirm webhooks[].isActive: false, then use List Deliveries for prior delivery status, attempts, errors, and timestamps.

Delivery Audit

Delivery rows for inactive endpoints can show pending, failed, or exhausted attempts. Store streamEventId, status, attempts, lastStatusCode, lastError, createdAt, and deliveredAt.

Event Join

Use delivery streamEventId as the {id} for Get Event. Store monitorId, monitorType, type, occurredAt, and data with the deactivation record.

Receiver Cleanup

Remove queue, CRM, alerting, or warehouse routing only after the endpoint is inactive and no more production events are expected.

Reactivate

To reuse the same webhook, call Update Webhook with isActive: true, then run Test Webhook.

Signing Secret

Delete returns no secret. Keep the original Create Webhook secret for audit records or future reactivation.
This endpoint supports dual authentication: API key (x-api-key header) or session cookie from the dashboard.Related: List Webhooks · Update Webhook · Test Webhook · List Deliveries · Get Event · Create Webhook
Last modified on May 23, 2026