
Open routes
HTTP push and Energis.Cloud
HTTP push is for a system that already holds your readings: a building management system, an IoT platform, a data logger or your own software. It posts them to Energis.Cloud in the Energis.Cloud HTTP message format, and a message in that format is read right away, with nothing to develop.
HTTP push on Energis.Cloud on , across all customers.
What Energis.Cloud reads from HTTP push
- Electricity consumption
- Water consumption
- Heat consumption
- Cooling consumption
Readings are mostly stored as 5-minute values.
What the HTTP push connection gives you
A documented format
One JSON request carries a batch of readings for one device: several metrics, several timestamps. A message you can retry and log on your side.
An authorised route
Each request presents an API key. A request without it is refused.
Connected for you
Naming an asset code in the message lets Energis.Cloud connect the incoming data points to that asset, rather than leaving them to connect by hand.
Resend to correct
A reading with a timestamp already stored is replaced, so resending a corrected batch fixes the period. A modest backfill works the same way.
How the connection is switched on
Open the route
Energis.Cloud support gives you the address to post to, the API key your request presents and the code that identifies your environment.
Check your assets
The assets you intend to feed should already carry the metrics you send: a reading connects only to a metric the asset has.
Send a first message
One device, a couple of timestamps, one metric. The first message creates a data source with one data point per column you declared.
Connected to your assets
Each data point is connected to its asset once, unless the message named the asset code. From then on the readings feed the asset's metrics.
See your HTTP push data on Energis.Cloud



