Water API
The platform's data, available to your systems
Sites, devices, water quality, transactions and alerts — as a documented REST API, so your own systems can build on Hydrotec's data instead of working around it.
The problem
A dashboard is one interface. You may need others.
Operations teams need dashboards. Finance systems, GIS platforms, partner portals and custom internal tools need structured data — and shouldn't require manual exports to get it.
- No programmatic access means every integration is a manual export
- External systems can't react to events in real time
- Custom reporting tools rebuild data pipelines that already exist
- Partner and funder transparency requires a public-facing feed
The Hydrotec approach
One documented API across the platform
The Water API exposes the same resources that power Hydrotec's dashboards and mobile apps — sites, devices, readings, transactions and alerts — with webhooks for real-time events.
Features
What's included
Sites & devices
Query registered sites and devices, their configuration and current status.
Water quality data
Access quality readings tied to specific devices and timestamps.
Transactions
Dispensing and payment transaction records for reconciliation and reporting.
Webhooks
Subscribe to real-time events instead of polling for changes.
Scoped authentication
Token-based access scoped per organization, site or use case.
Developer documentation
A getting-started guide and reference for integrators.
Architecture
The same data model, exposed as an API
Every dashboard metric, mobile app screen and report ultimately reads from the same underlying resources the Water API exposes — so what you see in the product, you can build with in code.
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
Custom internal tools
Build exactly the internal view your team needs, on top of Hydrotec's data.
Partner & funder transparency
Expose a live status feed to stakeholders without manual reporting.
System integration
Sync Hydrotec data into billing, GIS or BI systems automatically.
Technical detail
Example resource
Illustrative structure of a sites resource. Confirm current schema in the developer documentation.
- REST resources for sites, devices, readings, transactions and alerts
- Bearer token authentication scoped per organization
- Webhooks for real-time device and alert events
- Pagination and filtering on list endpoints
{
"site_id": "site-nairobi-14",
"name": "Nairobi Central",
"devices": 6,
"status": "operational",
"last_reading_at": "2026-08-14T09:32:00Z"
}Why it matters
Benefits
Build what you actually need
The dashboard doesn't have to be your only interface.
Real-time, not batch
Webhooks mean your systems react as events happen.
One integration, many use cases
The same API supports internal tools, partner feeds and BI exports.
Documented, not guessed
A reference and getting-started guide instead of reverse-engineering.
FAQ
Common questions
Who is the Water API for?
Developers and technical teams at operators, utilities and partners who need programmatic access to Hydrotec's platform data beyond the standard dashboard.
Is API access included by default?
API access is provisioned per customer and use case. Contact our team to discuss access, scope and current schema for your integration.
What's the difference between the Water API and the Water ATM API?
The Water ATM API is a focused subset for Water ATM-specific data — dispensing, payments and machine status. The Water API covers the broader platform, including monitoring, quality and utility use cases.
Are the code examples on this page confirmed live endpoints?
They're clearly labeled examples illustrating the data shape used across the platform. Confirm exact endpoints and fields with our team or in current developer documentation before integrating.
Get started
Talk to us about API access
Tell us what you're building and we'll help you scope the integration.