Decide whether you are changing phase for individual tagged plants or for a whole plant batch, since these use different endpoints and payloads.
Retrieve the valid growth phase names for your state via the growth phases reference endpoint.
For individual plants, submit plant label, new phase, tag, location, and phase-change date to the plant growth-phase endpoint.
For batches, submit batch name, count of plants to move, new phase, and destination location to the batch growth-phase endpoint.
Keep each request to 10 or fewer objects.
Verify the change by querying the vegetative, flowering, or active plant/batch listing endpoints.
Known gotchas
The plant-level and batch-level endpoint names differ only slightly, which is an easy source of path errors.
The HTTP method used for the plant-level growth-phase change differs between API v1 and v2.
Some states require assigning a new individual plant tag when moving plants to a flowering phase; confirm your state's specific rule before automating this step.
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?