Start a single Rachio zone for a specific duration via the public API
domain: rachio.readme.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Obtain the target zone's unique id from a prior GET /public/device/{id} or /public/person/{id} call.
Send PUT https://api.rach.io/1/public/zone/start with JSON body {"id": "<zoneId>", "duration": <seconds>} and an Authorization: Bearer header.
duration must be between 0 and 10800 seconds (3 hours); Rachio rejects larger values.
Poll GET /public/device/{id}/current_schedule to confirm the zone is running and see remaining time.
To run several zones back to back in one call instead, use PUT /public/zone/start_multiple with an ordered list of zone ids and durations.
Known gotchas
There is no single-zone stop endpoint that mirrors zone/start; stopping requires device/stop_water (whole device) or pause_zone_run (temporary hold), covered separately.
A 4XX response body carries the real rejection reason (e.g. zone disabled, duration out of range) — don't rely on the HTTP status code alone.
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?