Monitors
Delete Twitter Keyword Monitor & Stop Webhooks
Delete a keyword monitor, stop polling its X search query, and prevent new matching tweet events and webhook deliveries. Includes signature and retry examples.
- 200
- 400
- 401
- 404
- 429
DELETE
Delete Twitter Keyword Monitor & Stop Webhooks
Delete a keyword monitor only when its tweet query should stop permanently.
Pause it instead when future monitoring might resume.
The Node.js, Python, and Go examples convert the delete response into one receipt row.
Store
The provided monitor ID is not a valid format.
Missing or invalid API key.
No keyword monitor exists with this ID, or it belongs to a different account.
Too many requests. Wait for the
Free - does not consume credits
keyword_monitor_id, success, verify_endpoint, and list_endpoint, then verify
that the deleted ID no longer appears in the list and that the verify endpoint
returns 404.
Remove one keyword without deleting the monitor
Use this route when the monitor should continue with fewer search terms. Confirm both the monitor ID and keyword ID before deletion. Save the keyword text in your approval record. The response identifies the removed keyword. Other keywords and monitor delivery settings remain a separate concern. Use a full monitor deletion only when the entire monitor should stop. Do not delete the monitor to remove one unwanted keyword.Path parameters
string
required
The unique keyword monitor ID.
Headers
string
required
Your API key. Session cookie authentication is also supported. Generate a key from the dashboard.
Response
200 OK
boolean
Always
true on successful deletion.400 Invalid ID
401 Unauthenticated
404 Not Found
429 Rate Limited
Retry-After header before retrying.
Deletion handoff
Use this endpoint when a keyword query should stop permanently. Use Update Keyword Monitor withisActive: false when you only need to pause alerts and keep the monitor
available.
Permanent Remove
Delete removes the keyword monitor. Store returned
success before treating
the deleted ID as permanently removed. The deleted ID cannot be fetched,
updated, resumed, or billed again.Stored History
Stored events and webhook delivery records tied to this keyword monitor are
removed with it. Export or reconcile records before deletion.
Pause Instead
Use
PATCH /monitors/keywords/{id} with isActive: false to stop future
polling, alerts, and hourly billing while preserving the monitor record.Verify Removal
Call List Keyword Monitors after
deletion. Get Keyword Monitor should
return
404 for the deleted ID.Track New Query
Create a new keyword monitor when the X search query changes. Store the new
id, query, eventTypes, isActive, and nextBillingAt.Webhook Reuse
Existing webhook endpoints remain configured. Keep their
eventTypes
aligned, then run Test Webhook before
relying on new keyword monitor alerts.The keyword monitor is deleted and its stored events are removed with it. Pause with
isActive: false if you want to stop new checks without deleting the monitor.Related: List Keyword Monitors to verify removal, or Create Keyword Monitor to track a new query.
- 200
- 400
- 401
- 404
- 429
Delete Twitter Keyword Monitor & Stop Webhooks