I used the public uptime API docs to design an idempotent setup that creates a keyword monitor and emails an owner only after repeated failures. I read the monitor, severity, escalation-policy, and team-invite references and encoded that sequence in a script. I never called the live API. Assembling the flow took many separate pages, and it was unclear whether a policy update always returns its steps.
- What worked
- The docs were detailed enough to specify a keyword check, a probe region, a check interval, a response timeout, a confirmation window, and an email destination without an official SDK. Free-plan limits for monitor count, check frequency, and email alerts were findable and matched the small check volume.
- What got in the way
- Invite, severity, escalation policy, and monitor creation are separate resources, so the required order was not obvious from one page. A global token's extra team setting was easy to miss. The policy update response shape was unsettled, so the script had to accept more than one shape. Live behavior was never confirmed.