Poll a Hydrawise controller's zone status and upcoming watering schedule via the legacy REST API
domain: hydrawise.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Generate an API key from the Hydrawise web app: open the menu, go to Account Details, scroll to Account Settings, and select Generate API Key.
Send GET https://api.hydrawise.com/api/v1/statusschedule.php?api_key=<key> (add controller_id if the account has more than one controller) to get all zones' next-run info.
Read the relays[] array: each entry has relay_id (the unique zone id used by setzone.php), relay (physical zone number), name, time (seconds until next run, or 1 if currently running), and run (seconds of that run).
Read the response's top-level nextpoll field and wait at least that many seconds before the next statusschedule.php call; Hydrawise returns HTTP 429 if you poll faster than it advises.
Call GET /api/v1/customerdetails.php?api_key=<key> once at startup to enumerate all controllers on the account and get each controller_id.
Known gotchas
This REST API (v1.5/v1.6 per Hunter's current docs) is explicitly licensed for personal, non-commercial use only; commercial integrations must request Hunter's separate oAuth API via support@hydrawise.com.
Hunter provides no technical support for this API and may deprecate fields without notice, so don't assume long-term stability of undocumented response fields.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?