Skip to main content
DELETE
/
monitors
/
{id}
Delete monitor
curl --request DELETE \
  --url https://xquik.com/api/v1/monitors/{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/7 \
  -H "x-api-key: xq_YOUR_KEY_HERE" |
  jq -c '{
    monitor_id: "7",
    success: .success == true,
    verify_endpoint: "/api/v1/monitors/7",
    list_endpoint: "/api/v1/monitors",
    events_endpoint: "/api/v1/events?monitorId=7",
    event_detail_endpoint_pattern: "/api/v1/events/{event_id}",
    webhooks_endpoint: "/api/v1/webhooks",
    deliveries_endpoint_pattern: "/api/v1/webhooks/{webhook_id}/deliveries"
  }'
The cURL, Node.js, Python, and Go examples convert the delete response into one receipt row. Store monitor_id, success, verify_endpoint, list_endpoint, events_endpoint, event_detail_endpoint_pattern, webhooks_endpoint, and deliveries_endpoint_pattern, 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 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 tracked account should stop permanently. Use Update Monitor with isActive: false when you only need to pause alerts and keep the monitor available.

Permanent Remove

Delete removes the account 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 account monitor are removed with it. Export or reconcile records before deletion when support or audit workflows need history.

Event Audit

Use List Events before deletion to capture monitor events. Use Get Event when you need one event’s full payload before removing the monitor.

Delivery Audit

Use List Deliveries before deletion when webhook delivery evidence must be retained. Join delivery streamEventId to event IDs. Do not use x_event_id as the delivery join key.

Pause Instead

Use PATCH /monitors/{id} with isActive: false to stop future checks, alerts, and hourly billing while preserving the monitor record.

Verify Removal

Call List Monitors after deletion. Get Monitor should return 404 for the deleted ID.

Track New Account

Create a new account monitor when the tracked account changes. Store the new id, username, xUserId, eventTypes, isActive, and nextBillingAt.

Webhook Reuse

Existing webhook endpoints remain configured. Check List Webhooks, keep their eventTypes aligned, then run Test Webhook before relying on new account monitor alerts.
The 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 Monitors to verify the monitor was removed, Get Monitor to confirm 404, List Events and Get Event to preserve event evidence, List Webhooks and List Deliveries to retain delivery evidence, or Create Monitor to set up a new one.
Last modified on May 21, 2026