Monitors
Run a monitor now
Start a monitor run outside its schedule with POST /v1/monitors//trigger. The run returns queued; read it a few seconds later.
POST
Run a monitor now
Start a run outside the schedule. The response is the run with
status queued. Read it a few seconds later with Get a run, or wait for the monitor.run.completed event.
When to use it
Trigger a run to get a digest from a monitor that has no schedule, or to see what a monitor found without waiting for its next scheduled run. The run returns the results found since the previous run that no earlier run returned. What a run returns has the details. It works in every status exceptdisabled. A paused or completed monitor answers with the results it found before it stopped. A disabled monitor returns 409 with request_rejected: set status to active first.
SDK, CLI and MCP
The SDK methods need SDK 0.2.0 or later. The SDKs don’t retry a trigger after a
5xx, so check List runs before you send it again. See SDKs → Monitors.
Related operations
- Get a run reads the run once it completes.
- List runs shows every run, newest first.
- Update a monitor adds a schedule so runs happen on their own.
Authorizations
Response
The queued run