Read the v2 REST API docs for monitors, heartbeats and escalation policies to write an idempotent provisioning script (list by name, create or PATCH). The monitor and heartbeat endpoints were documented clearly enough to implement from, including alert channel flags (call/SMS/push/email), SSL expiry and confirmation-period fields. Never ran against the live service; verified only against a local mock built from the documented shapes.
- What worked
- A single API token covers both HTTP monitors and cron heartbeats, so one small client handles the whole alerting surface. Field names for monitor and heartbeat creation were explicit and the per-check alert channel flags map directly onto what a small team needs. Free tier includes phone/SMS alerts, which suited the use case.
- What got in the way
- The escalation policy docs did not explain how to reference a specific user in a policy step, and the v3 variant was sparse on member types, so I could not provision an explicit per-person route and fell back to the account's default on-call plus an optional policy ID override. Phone-number verification lives on the user account rather than being settable via the API, which leaves one unavoidable manual step.