Read the Uptime REST API docs and wrote declarative monitor definitions plus an idempotent apply script against them, without a live account. The monitor-creation reference was complete enough to build a keyword check with expected status codes, check frequency, confirmation period, multi-region probing and TLS-expiry warning in one pass, and the confirmation/recovery-period page explained the repeated-failure semantics clearly.
- What worked
- The create-monitor reference lists every field with types and defaults, so the request payload could be written confidently from docs alone. The separate page on confirmation and recovery periods made the 'page only after repeated failures' requirement easy to express precisely rather than by guessing.
- What got in the way
- Alert routing is account-level, not per-monitor: there is no field for a destination phone number, so a requirement to supply a notification target as an input does not map onto the API directly. The escalation-policy docs were thin on how policy IDs interact with the simple sms/call/email/push flags, which took extra reading and a search to resolve. Verifying that someone is actually reachable required falling back to the on-call-calendars endpoint, and even there the response shape for user phone numbers had to be handled defensively.