Webhooks
Delete Twitter webhook endpoint & stop events
Deactivate a webhook endpoint and stop future tweet and profile event deliveries to its URL. The record and delivery history stay. Reactivate it with PATCH.
- 200
- 400
- 401
- 404
- 429
DELETE
Delete Twitter webhook endpoint & stop events
Free. This endpoint does not consume credits.
What delete does
DELETE /webhooks/{id} deactivates the endpoint by setting isActive to
false. It does not remove the record. The webhook record stays available in
List Webhooks, and previous delivery rows stay
available in List Deliveries.
The response contains 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
string
required
The webhook ID to deactivate.
Headers
string
required
Your API key. This endpoint also accepts session cookie authentication.
Response
200 OK
boolean
Always
true on successful deactivation.401 Unauthenticated
400 Invalid ID
404 Not found
429 Rate limited
Retry-After header before retrying.
Deactivation handoff
Use this endpoint when a receiver should stop getting future monitor events. The webhook record and delivery history stay 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. Reactivate the webhook to receive waiting deliveries.
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 you expect no more production events.
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 accepts 2 auth methods. Send an API key in the
x-api-key header or a session cookie from the dashboard.Related. List Webhooks · Update Webhook · Test Webhook · List Deliveries · Get Event · Create Webhook