MOL · capability 08 of 08
MOL data is available to other systems through a documented API.
MOL provides a documented JSON API to its meter register and its interval data. Systems that need metering data, such as an ERP (enterprise resource planning) system, a property management platform, a business intelligence tool or a corporate reporting pipeline, retrieve it directly instead of waiting for an export.
The same meter in three hierarchies: physical, financial and electrical.
A meter has a physical location, a cost centre and a position in the reticulation. These three hierarchies do not align, and which one applies depends on who is asking.
MOL maintains all three and exposes each as a separate call, so a finance integration does not have to reconstruct a cost-centre rollup from a building tree.
Physical
getMetersByBuilding
Site, building, meter point, meter. The hierarchy a facilities team works in.
Financial
getMetersByCostCentre
Cost centre, account, utility, meter. The hierarchy that reconciles to a general ledger.
Electrical
getMetersBySLD
From the root meter down through the single-line diagram nodes. The hierarchy that follows the reticulation.
Interval data by meter or by site.
Readings are returned for a date range, by utility type, with the validation state attached. A consuming system therefore keeps the distinction between measured and estimated values.
- getReadingsByMeter
- Interval data for one meter over a date range.
- getReadingsBySite
- Interval data for every meter at a site, by utility type.
Token authentication
Bearer tokens with a documented expiry and refresh process, instead of credentials sent with every call.
Documented error responses
Expired token, missing parameters, unknown site and portfolio without a site are each documented, so an integration can handle them correctly.
Reference documentation
A reference document covers request formats, parameter details, response schemas and worked examples. It is available to customers on request.
Integration with existing systems.
A separate integration, outside the standard API, carries bill verification into an enterprise property system. Invoice data is posted in, MOL bills the same period from the client's own check meters, and the variance report is returned automatically, instead of being emailed as a spreadsheet for someone to capture again.
Through the API, a corporate reporting pipeline obtains consumption per site per half hour without anyone exporting data each month. An emissions figure calculated this way can be reproduced on demand rather than rebuilt.
See this applied to your own data.
PMT will run it against a month of your readings and show you the results.