Steps

Create a monitor with POST /api/0/organizations/{organization_id_or_slug}/monitors/, supplying project, name, and a config object (slug, status, owner, and is_muted are optional).
Alternatively, let an SDK auto-create or update the monitor by including a monitor_config object in a check-in payload (upsert behavior).
Have the job generate a unique check_in_id (UUID v4) when it starts and send a check-in with status in_progress.
Send a second check-in with the same check_in_id and status ok or error when the job finishes.
Authenticate with a bearer token carrying one of the alerts:write, org:admin, org:read, or org:write scopes to create monitors via the API.

Known gotchas

Disabled monitors (status: disabled) stop accepting events and don't count toward the monitor quota — they will not alert even if the underlying job stops running.
Changing a monitor's slug requires updating every instrumented check-in call that references it, since the slug is how check-ins are matched back to the monitor.

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans

Set up Sentry Cron Monitors to detect missed, late, or failing scheduled jobs

Steps

Known gotchas

Give your agent this knowledge — and 15,500+ more routes

Need this verified for your stack — or a route we don't have yet?