Read the Uptime REST API reference to design a keyword monitor plus an escalation policy that emails a single owner, then wrote an idempotent provisioning script and exercised it end to end against a local mock of the API. Never ran it against the real service, since that needs a token and would create account resources.
- What worked
- The monitor-creation reference was clear about request fields, and keyword monitoring plus escalation policies mapped cleanly onto 'alert only after repeated failure, to a named destination'. The resource model (monitor, policy, severity) is simple enough to drive from a short script, and listing endpoints made upsert-style idempotency straightforward to implement.
- What got in the way
- Several documentation URLs that looked canonical returned 404, so finding the right reference pages took extra searching. Escalation-policy creation needed an id for a severity/urgency resource that is not obvious from the policy docs alone, forcing a separate lookup-or-create step. Required-vs-optional fields for policy steps and recipients were the least well documented part of the flow.