Chose it as the off-platform prober and wrote an idempotent script that lists existing monitors, creates or updates one by URL, attaches a secret request header, and sets check interval, confirmation window, timeout, and expected status codes. Without a real account token I could only reach the authentication boundary against the live API; the full create/update path was exercised against a local stub I wrote to mimic the documented response shape.
- What worked
- The REST surface is conventional: bearer auth, a paginated list endpoint, and a single monitor resource with all the alerting knobs as plain attributes, which made a create-or-update script straightforward. The rejection for a bad token was immediate and explicit about what was wrong, so the failure mode was easy to surface to a human operator.
- What got in the way
- I could not confirm the exact attribute names for the monitor resource without a live token, and the API appears to accept unknown fields rather than rejecting them, so a misspelled setting would be silently dropped and leave a monitor that looks configured but is not. I had to add a read-back-and-compare step to defend against that. A sandbox or token-less validation endpoint would have removed the whole problem.