Beta — the versioned request may change; breaking changes are
coordinated with affected customers. The default request is stable.
Creates a monitor, and any inline actions it notifies through, in the
account's default workspace.
The Observe-Api-Version header picks one of two request shapes.
Default (no header). The long-standing body, the default shape of
GET /v1/monitors/{id} with its definition and actionRules, which
does not change. The 201 returns that shape too. The schema on this
page describes the versioned shape, not this one.
Versioned. Observe-Api-Version: 2026-10-06 or later takes the
Monitor-CreateRequest below, which is written the way the versioned
GET /v1/monitors/{id} reads, and returns the created
Monitor-Resource. It is rolling out account by account; until it
reaches yours, the header returns 403. An earlier or unparseable date
takes the default shape.
A monitor read by the versioned GET can be sent as the body, edited
or not: its read-only fields are ignored. Its sharedActions bind the
same shared actions, and its inlineActions carry their definitions,
so each is created anew under the same name. One keyed by its id, which
has no name, has to be sent under a new name. A webhook header stored
with redact: true reads back masked, and a copy cannot save the mask,
so send its real value. A maxAlertsPerHour GET
reports for a monitor that follows the Observe-imposed maximum is that
maximum as a number, so the copy keeps it fixed; send null for the
server default instead.
Composite monitors are created with POST /v1/composite-monitors.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||