Monitors
Update a monitor
Change a monitor with PATCH /v1/monitors/: send only what changes, or set status to paused or active to pause or resume it.
PATCH
Update a monitor
Change a monitor. Send only the fields that change:
search and webhook are merged into the stored ones, so {"search": {"max_results": 5}} keeps the query. To pause a monitor, send {"status": "paused"}. To resume it, or to turn a disabled monitor back on, send {"status": "active"}.
Common changes
schedule replaces the stored schedule instead of merging into it. A new once schedule makes a completed monitor active again. Resuming a monitor counts toward your organization’s active monitors. See Limits. Schedules lists the schedule rules and Webhook events lists the event names.
When the request adds a webhook to a monitor that had none, the response carries webhook.secret, once, as the create response does. Store it: before this change, such an update returned no secret, so the webhook couldn’t be verified. An update that only changes the url or events of an existing webhook, and every GET, never shows the secret.
SDK, CLI and MCP
The SDK methods need SDK 0.2.0 or later.
pause and resume send status for you. See SDKs → Monitors and CLI → Monitors.
Related operations
- Get a monitor shows the stored values before you change them.
- Bulk actions pauses or resumes many monitors in one request.
- Delete a monitor removes a monitor for good.
Authorizations
Body
application/json
Send only what changes.
Response
The updated monitor