Skip to main content
DELETE
/
monitors
/
keywords
/
{id}
Delete keyword monitor
curl --request DELETE \
  --url https://xquik.com/api/v1/monitors/keywords/{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/monitors/keywords/21 \
  -H "x-api-key: xq_YOUR_KEY_HERE" | jq
The Node.js, Python, and Go examples convert the delete response into one receipt row. Store 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.

​
Path parameters

​
id
string
required
The unique keyword monitor ID.

​
Headers

​
x-api-key
string
required
Your API key. Session cookie authentication is also supported. Generate a key from the dashboard.

​
Response

​
success
boolean
Always true on successful deletion.
{ "success": true }

​
Deletion handoff

Use this endpoint when a keyword query should stop permanently. Use Update Keyword Monitor with isActive: 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.
Last modified on May 18, 2026