Water ATM API
Build on top of your Water ATM network
Machine status, dispensing events, payments and water quality — available as structured data for the systems you already run: billing, CRM, BI or a custom operations tool.
Water ATM Network — Live
Illustrative
Machines Online
482 / 501
Litres Dispensed
1.84M
Revenue Today
$6,240
Avg. Water Quality
97.2%
Dispensing Volume — 7 days
Device Fleet
- ATM-0142New Delhi
- ATM-0143Konark
- PLANT-07Nashik
- ATM-0209Kasba, Kolkata
- SENSOR-14Khamar
- ATM-0301Ayodhya
The problem
Fleet data trapped in one dashboard doesn't scale
A dashboard is enough until you need Water ATM data inside another system — accounting, a partner portal, a public transparency map, or a custom analytics tool.
- Manually exporting reports instead of syncing data automatically
- No way to trigger external workflows (e.g. finance, alerts) from machine events
- Third-party systems can't verify machine status independent of the dashboard
- Every new integration becomes a one-off manual process
The Hydrotec approach
A documented API over the same data the dashboard uses
The Water ATM API exposes machines, sites, dispensing events, transactions and quality readings as REST resources, plus webhooks for real-time events — so your systems don't have to poll for changes.
Features
What's included
REST resources
Machines, sites, dispensing events, transactions and quality readings as clean JSON resources.
Webhooks
Subscribe to real-time events instead of polling — machine offline, low tank, quality alert.
Token-based auth
Scoped API keys per integration, so partners see only what they need.
Historical data access
Query historical dispensing and revenue data for reporting and reconciliation.
Live machine state
Poll or subscribe to current machine status for external status pages.
Integration-ready
Designed to plug into billing, CRM, BI and partner-facing tools.
Architecture
One API, the same data as the dashboard
The API sits on the same data model as the Water ATM Dashboard, so anything visible in the console is available programmatically.
Plants, networks, ATMs, tanks
Sensors, meters, controllers
Ingestion, storage, rules
REST & webhooks
Web operations console
Field & customer apps
Forecasts, anomalies
Use cases
Where this fits
Finance & reconciliation
Sync transaction data directly into accounting systems.
Partner transparency
Give funding partners or government stakeholders a live status feed.
Custom analytics
Feed dispensing and quality data into your own BI tooling.
Technical detail
Example request
Illustrative response shape for a machine status lookup. Confirm current schema in the developer documentation before integrating.
- Authentication via bearer token scoped to your organization
- Pagination on list endpoints for large fleets
- Webhook delivery with retry on failed deliveries
- Rate limits documented per API key tier
{
"machine_id": "arosia-500-0142",
"site": "kasba-bus-depot",
"status": "online",
"tank_level_pct": 62,
"last_dispense_at": "2026-08-14T07:12:03Z",
"quality": { "ph": 7.1, "tds_ppm": 214 }
}Why it matters
Benefits
No manual exports
Systems stay in sync automatically.
Real-time awareness
Webhooks mean your systems know as soon as Hydrotec does.
Scoped access
Partners and integrations see only what they're authorized to.
Build what you need
A dashboard doesn't have to be the only interface to your fleet.
FAQ
Common questions
Is the Water ATM API publicly documented?
API access is provisioned per customer and partner. See /documentation/ for the current developer overview, and contact our team for access and up-to-date schema details.
What authentication does the API use?
Token-based authentication with keys scoped to an organization and, where needed, a specific site or machine group.
Can I get real-time machine events instead of polling?
Yes, via webhooks for events like machine offline, low tank level and quality threshold breaches.
Are the code examples on this page from a live, public API?
They're illustrative examples of the data shape used across Hydrotec's platform, clearly labeled as examples. Confirm exact field names and availability with our team before building an integration.
Get started
Talk to us about API access
Tell us what you're building and we'll scope the integration together.