The data is not locked in MOL.
MOL exposes a documented JSON API over its meter register and its interval data. Systems that need metering — an ERP, a property management platform, a BI stack, a corporate reporting pipeline — pull it directly rather than waiting on an export.
The same meter, in whichever tree the caller thinks in.
A meter has a physical location, a cost centre, and a position in the reticulation. Those three hierarchies do not align, and which one is correct depends entirely on who is asking.
MOL maintains all three and exposes each as its own 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 tree a facilities team works in.
Financial
getMetersByCostCentre
Cost centre, account, utility, meter. The tree that reconciles to a general ledger.
Electrical
getMetersBySLD
Root meter down through single-line diagram nodes. The tree that follows the reticulation.
Interval data, by meter or by site.
Readings come back for a date range, by utility type, with the validation state attached — so a consuming system inherits the distinction between measured and estimated rather than flattening it on the way out.
- getReadingsByMeter
- Interval data for one meter over a date range.
- getReadingsBySite
- The same, for every meter at a site, by utility type.
Token authenticated
Bearer tokens with a documented expiry and refresh flow, rather than credentials embedded in every call.
Errors are specified
Expired token, missing parameters, unknown site, portfolio without a site — each documented, so an integration can handle them rather than guess.
Written down
A reference document with request formats, parameter details, response schemas and worked examples. Available to customers on request.
Into the systems you already run.
The same interface carries bill verification into enterprise property systems: invoice data is posted in, MOL bills the identical period from the client's own check meters, and the variance report is returned by APIrather than emailed as a spreadsheet for somebody to key in again.
It is also how a corporate reporting pipeline gets consumption per site per half hour without a person exporting anything monthly — which is the difference between an emissions figure that can be reproduced on demand and one that has to be rebuilt.
Want to see this on your own data?
We will run it against a month of your readings and show you what comes out.
Talk to us