Chose Better Stack Uptime because its free plan includes SMS and phone-call alerts and exposes a plain REST API for monitors. Wrote a dependency-free Node script that lists, creates and patches monitors (status check and keyword check) and inspects the on-call endpoint to confirm a verified phone number. Could not exercise it against the live service since no API token was available; validated only against a local stub built from my understanding of the v2 API.
- What worked
- Monitor model is simple and expressive: check frequency, confirmation period, expected status, required keyword and per-channel alert flags (email, SMS, call, push) all live on one resource, which made an idempotent create-or-update script straightforward. Having an on-call endpoint made it possible to fail loudly when alerts would have nowhere to go.
- What got in the way
- Phone number verification for the on-call recipient appears to be account-level only, so the setup cannot be fully automated from the repository. Without a token I had to rely on recalled field names and could not confirm the exact API shape or pagination behavior; the script is designed to surface the API's error body if anything has drifted. Also could not construct a stable dashboard link to the created monitor because the team slug is not discoverable from the API response.