Your water data belongs in your systems, too.
HydroOS runs a documented REST API. Read your sites, fields, readings, trials and alerts straight into the tools your operation already runs on, push readings in from your own sensors, and get a signed webhook the moment something changes — no exports, no re-keying, no waiting on us.
Five resources, one key, your own stack.
Each resource is a versioned, paginated REST endpoint scoped to your organization. Pull them on a schedule into a warehouse, a dashboard, or whatever your team already uses to run the season.
Your ranches, water systems, blocks and reservoirs, with their structure intact.
The individual fields and blocks inside each site.
Water-chemistry results over time — the record your decisions are built on.
Product trials and what they measured, so results can live in your own reporting.
Threshold and threat alerts, the moment the platform raises them.
It takes data in, not just out.
Most platforms will show you your data and stop there. HydroOS accepts it — so the sensors and lab feeds you already own can write straight into the same record your agronomy runs on.
Push readings in from your own sensors and lab feeds, one call per reading, safe to retry.
Send an idempotency key with a reading and a retried or replayed call resolves to the same row — a flaky connection at the pump house never doubles your record.
Find out when it happens, not when you next poll.
Subscribe an endpoint and HydroOS calls you as events occur. Every delivery is signed, so your systems can verify a payload genuinely came from us before acting on it.
reading.createdA reading was ingested from one of your devices.alert.createdThe platform raised new alerts for your organization.threat.createdNew water threats were detected.notification.createdNew notifications were produced for your team.
Built to survive your security review.
The questions an IT team asks before they will connect anything to a vendor — answered up front, because they are the same questions we had to answer to build it.
Per-organization keys
Every key belongs to exactly one organization. The organization is derived from the key itself, never from the request — a key cannot reach another customer's data.
Scoped permissions
A key carries only the scopes you grant it. Read access and ingest are separate permissions, so a sensor feed never gains the ability to read your trials.
Stable pagination
Keyset pagination, not offsets. Pages stay consistent as new records arrive mid-read, so a long sync can't silently skip or duplicate rows.
Versioned and documented
A versioned /api/v1 namespace with a machine-readable OpenAPI 3.1 document, kept in lockstep with the live API by an automated check.
curl -H "Authorization: Bearer $HOS_KEY" \
"https://hydroos.ag/api/v1/sites?limit=50"Full endpoint documentation and the OpenAPI document are available inside HydroOS to organizations on the Enterprise plan.
The API is part of the Enterprise plan.
API keys, ingest and webhooks are enabled per organization on Enterprise. If you are already a HydroOS customer, your team can find the full developer reference inside the platform once it is switched on. If you are evaluating, tell us what you need to connect and we will walk you through it.
Tell us what you need to connect
Sensors, a warehouse, an existing agronomy stack — tell us where the data has to go and we'll route you to a person, not a cart.