Delete a monitor

⚠️ Alpha — the versioned response is under active development and
may change without notice. The default response is stable.

Deletes a monitor, stops its evaluation, and deletes the inline actions
that belong to it. Shared actions it notified through are kept.

The Observe-Api-Version header picks one of two behaviors.

Default (no header). The long-standing delete, which does not
change.

Versioned. Observe-Api-Version: 2026-10-06 or later answers as
documented here, refusing before anything is removed:

StatusWhen
204Deleted.
400A composite monitor; see below.
403You can view the monitor but not edit it, or an app manages it.
404The monitor does not exist, or you cannot view it.
409A composite monitor is built on it. The message names the composites to remove it from.

It is rolling out account by account; until it reaches yours, the
header returns 403. An earlier
or unparseable date takes the default behavior.

Composite monitors are deleted with DELETE /v1/composite-monitors/{id}.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required

Unique identifier of the monitor. A string, as every response body renders it.

Headers
string
^\d{4}-\d{2}-\d{2}$

Picks the behavior by release date (YYYY-MM-DD). 2026-10-06 or later answers as documented here, if enabled for your account (otherwise 403). No header, or an earlier or unparseable date, takes the default behavior described above.

Responses

Language
Credentials
Bearer
Authorization: Bearer <customerid> <apitoken>
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
*/*
application/json