Generate an API key in the UptimeRobot dashboard under My Settings; UptimeRobot v3 API uses API key authentication via the api_key parameter in POST bodies (application/x-www-form-urlencoded or JSON)
Create an alert contact: POST https://api.uptimerobot.com/v3/newAlertContact with type=2 for email and the recipient address; note that email contacts require the recipient to confirm before they become active (status transitions from 0 to 2)
Create a monitor: POST https://api.uptimerobot.com/v3/newMonitor with type=1 (HTTP/S), url, friendly_name, interval (seconds), and alert_contacts array including the confirmed contact ID and threshold
Retrieve monitor status: POST https://api.uptimerobot.com/v3/getMonitors with monitor IDs or retrieve all monitors; response includes status (0=paused, 1=not checked yet, 2=up, 8=down, 9=seems down)
Pause or resume a monitor: POST https://api.uptimerobot.com/v3/editMonitor with status=0 to pause or status=1 to resume for maintenance windows
Delete a monitor: POST https://api.uptimerobot.com/v3/deleteMonitor with id; deletion is permanent — retrieve and archive config before deleting
Known gotchas
UptimeRobot released v3 API; v2 is still accessible but will no longer receive new features — new integrations should target v3, which uses a structured array for alert contacts instead of v2's encoded string format
Webhook alert contacts (type=5) activate immediately without confirmation, but email contacts do not fire until confirmed by the recipient — automate a check for contact status before trusting new alert pipelines
Free-tier monitors have a minimum check interval of 5 minutes; paid plans support 1-minute intervals — validate the tier before setting interval values in automated provisioning scripts
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp