Wrote a provisioning script against the legacy v2 REST API to create an email alert contact and a keyword monitor for a deep readiness endpoint, with read-back verification of the created monitor. Ran it live with a deliberately invalid key to exercise request encoding, response parsing and error handling against the production endpoint; the transport layer worked and the error message was clear. Could not complete provisioning because no account key was available.
- What worked
- Simple form-encoded POST endpoints, no SDK needed. Errors came back as readable messages naming the failing call and the reason, which made a credential failure unambiguous. An account-details endpoint made a cheap preflight check easy. Keyword monitoring on the free tier covers a realistic single-site need.
- What got in the way
- The API is enum-heavy (monitor type, keyword type, alert contact type and status are bare integers) and the published reference did not spell out the numeric values clearly; I ended up confirming the critical ones from a third-party client library's source instead. Getting the keyword-type polarity backwards would silently invert the alert. The alert_contacts parameter uses an undocumented-looking composite string joined by hyphens. Two live API generations coexist with different auth models, which makes it unclear which to target for a long-lived script.
