API
The Data API lets your own applications pull measured data straight from the platform, so Augos sits inside your stack rather than beside it.
1 · What it does
The API gives your systems programmatic access to measured data, on demand, without anyone exporting a file by hand. It returns the same readings you'd see in the platform, served straight to your code, for electricity, water, manufacturing and sensing devices, and it works on both actual and virtual measurement points.
2 · Getting access
Access is granted per measurement point. To register, email support@augos.io with the points you want enabled, and Augos issues you a unique authorisation token. Send that token as a Bearer token in the Authorization header of every request.
3 · Retrieve measurement data
Query parameters:
| Parameter | Required | Description |
|---|---|---|
pointID | Yes | The unique ID of the measurement point. Retrieve it from the points list (section 5). |
startDateUTC | Yes | UTC start of the period, format yyyy/mm/dd HH:mm. Inclusive. |
endDateUTC | Yes | UTC end of the period, format yyyy/mm/dd HH:mm. Inclusive. |
interval | Yes | hh for half-hourly data, or mi for one-minute data. |
summed | Yes | 0 returns all fields; 1 returns summarised data. |
productTypeID | When needed | The product type, where a point carries more than one. 2 = 3-phase electricity device, 7 = OEE device. |
A request for half-hourly data over one day looks like this:
4 · The response
Data comes back as JSON, one object per interval. The exact fields depend on the measurement point.
point is the full description of the measurement point. dateUTC is the UTC start of the interval: with interval=hh, a date of 2020/08/23 11:00 covers the period 11:00 to 11:29.
5 · Listing your measurement points
Every point has its own pointID. To retrieve the list of points and their IDs, call:
Send the same Authorization header. Optional parameters: skip (the row to start from), take (the number of rows to return), and all (set to 1 to return every record). Either take or all must be set for results to come back.
6 · Rate limits
Each measurement point allows up to 48 data requests a day, and up to 10 080 records per request. If you need more, an additional API subscription lifts the limit.
7 · Access and permissions
The API runs on the same roles and point-level permissions as the platform, so a token only ever returns the points it's cleared for, the same boundary a person would have. See Roles & access. For AI agents, Augos is building Model Context Protocol (MCP) support, so an agent can query the data structure directly rather than through a fixed export.