DELETE https://xquik.com/api/v1/monitors/keywords/{id}
Delete a keyword monitor only when its tweet query should stop permanently.
Pause it instead when future monitoring might resume.
Free. This endpoint does not consume credits.
verify_endpoint while it returns
200. Deletion finishes when it returns 404. Respect Retry-After between
requests.
Remove one term from a monitored query
A keyword monitor stores one query. The API has no route that deletes a single term. This route deletes the whole monitor. To drop a term, create a new monitor with the revised query. Export the old monitor’s stored events. Then pause or delete the old monitor.Path parameters
Headers
Response
202 Accepted
Location and Retry-After headers. Poll Location
after the stated interval.400 Invalid ID
{ "error": "invalid_id", "message": "Invalid ID format." }
The provided monitor ID is not a valid format.401 Unauthenticated
{ "error": "unauthenticated", "message": "Missing or invalid API key" }
Missing or invalid API key.404 Not found
{ "error": "not_found", "message": "Monitor not found" }
No keyword monitor exists with this ID, or it belongs to a different account.429 Rate limited
Too many requests. Wait for theRetry-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. That keeps the monitor
available.Permanent remove
Delete stops the monitor immediately. Poll
statusUrl until it returns
404. You cannot update or resume the deleted ID.Stored history
Xquik removes stored events and webhook delivery records for this monitor
in batches. Export required records before deletion.
Pause instead
Use
PATCH /monitors/keywords/{id} with isActive: false to stop future
polling, alerts, and hourly billing. The monitor record stays.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 (Twitter) 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.Xquik deletes the keyword monitor and its stored events. Pause with
isActive: false if you want to stop new checks without deleting the monitor.Related.
- List Keyword Monitors to verify removal.
- Create Keyword Monitor to track a new query.
Response examples
- 400
{ "error": "invalid_input", "message": "Invalid input. Check the request body." } - 401
{ "error": "unauthenticated", "message": "Authentication required. Provide a valid API key or bearer token." } - 403
{ "error": "api_key_paused", "message": "This API key is paused. Resume it at dashboard.xquik.com/api-keys to use it again." } - 404
{ "error": "not_found", "message": "Resource not found." } - 429
{ "error": "rate_limit_exceeded", "message": "Too many requests. Try again later.", "retryAfter": 60 }