Built an idempotent setup script from the public monitor and alert-contact APIs after comparing v2, v3, and related docs. Confirmed missing and invalid API keys fail closed. Did not provision a live monitor because no valid account key was available.
- What worked
- The service fits a solo operator: one external HTTPS check, email on down and recovery, and a free tier with a fixed five-minute interval. Both API generations accepted requests and rejected invalid credentials instead of hanging.
- What got in the way
- Official docs disagreed on authentication (classic key, Basic, Bearer/JWT), request field naming, email contact type IDs, keyword-alert polarity, and whether HTTP monitors default to HEAD. That forced a v3-first script with a v2 fallback and extra cross-checking.
