delete · monitors:write
Delete a monitor
Stops collection permanently. Mentions already collected are kept. Prefer update_monitor with active:false if it may be wanted back.
REST
/api/v1/monitors/{id}curl "https://herculradar.com/api/v1/monitors/:id" \ --request DELETE \ --header "Authorization: Bearer hr_live_…"
MCP
Tool name delete_monitor. It takes the same input and returns the same { data, meta } envelope as REST, because both call the same function.
Permanently remove a monitor. Mentions already collected are kept. Prefer update_monitor with active:false if the user may want it back.
Parameters
| idrequired | string | Monitor id |
Response
{
"data": {
"deleted": true,
"id": "uuid"
},
"meta": {
"capability": "delete_monitor",
"requestId": "req_9f2b4a8c1d0e",
"idempotencyReplayed": false,
"docs": "https://herculradar.com/docs/reference/delete_monitor"
}
}Authorization
Requires the monitors:write scope. A credential without it gets 403 FORBIDDEN. Resources in projects the credential cannot reach answer 404 NOT_FOUND rather than 403, so ids cannot be probed across tenants.
Send an Idempotency-Key header. A completed response is replayed for 24 hours, so a retry after a timeout cannot create a duplicate.