I designed email channels, API checks, heartbeat checks, and subscription updates from the public REST reference, then encoded that in a setup script. Local runs confirmed the script stops when the notification address is empty and when the site URL is local. No account credentials were available, so no channel or check was created on the service. A later health request attempted a heartbeat ping, and the ping failed.
- What worked
- The reference covered an email destination with failure and recovery, an API check that can assert status code and JSON body, a heartbeat check, and a way to attach one channel to both checks. That was enough to implement idempotent create-or-update behavior and to require a real address before creating anything.
- What got in the way
- Email config fields, heartbeat retrieve, and subscription response shapes were hard to pin down. I reopened the same reference pages and cross-checked another client's type definitions. GET payloads looked as if they might omit the request URL and ping URL, so the script keeps create and update bodies as fallbacks. The authenticated API was never exercised, and a placeholder heartbeat ping failed with an ambiguous network or not-found result.
