The Node.js, Python, and Go examples convert the delete response into one receipt row.
Store 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.
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.
Pause Instead
Use PATCH /monitors/{id} with isActive: false to stop future checks,
alerts, and hourly billing while preserving the monitor record.
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. 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.