Integrations: LF Cloud API, webhooks, Modbus and BMS/SCADA
Data leaves LF Cloud three ways: your system pulls it with the REST API (Retriever for sensor readings, Consumption for metered utility data), LF Cloud pushes each new reading to your server through the Active Forwarding webhook, or reports export as PDF or Excel on a schedule. Data comes in from the loggers themselves and, for Modbus RTU and M-Bus equipment, through MODGATE and the LF M-Bus Cloud Bridge. A BMS, SCADA or ERP connects through the API or the webhook; credentials and endpoint specifications are issued per account once the integration is scoped.
Last updated:
What you can pull, push and connect
| Interface | Direction | What it does | Format and limits |
|---|---|---|---|
| Retriever API | Pull (REST) | The latest reading, the first record, any reading by timestamp, or every record across a time range you choose. | JSON with temperature, humidity, voltage, signal strength and more. EDGE and BLOCK devices. 1 call per serial per minute. |
| Consumption API | Pull (REST) | Aggregated consumption for water, natural gas, electricity, heating or cooling, for all meters in the account or one serial number, over a time range down to the hour. | m³ for water and gas, kWh for electricity, with a reliability confidence score per reading. Built for billing and energy audits. |
| Active Forwarding API | Push (webhook) | LF Cloud posts each new reading to your server as it syncs, and forwards in batches when stored history uploads from device memory. No polling. | Standard HTTP webhook; JSON with serial number, device ID and all sensor values. You set the endpoint URL and the security token in the cloud dashboard. |
| Provisioning | Push into LF Cloud (REST) | Register devices and push their configuration programmatically, so onboarding scales with the deployment. | Per-account credentials, issued once the integration is scoped. |
| Reports | Export | Any date range as PDF or Excel, or scheduled for automatic email delivery, so a file reaches an inbox without anyone signing in. | Includes the Mean Kinetic Temperature and min/max/average reports. |
| MODGATE | Modbus RTU into LF Cloud | Reads the registers of an RS485 Modbus RTU device and sends decoded values to LF Cloud over WiFi or cellular, with the same alarms as any LoggerFlex sensor. | Configurable registers. Typical uses: generator run-hours and fuel levels, solar inverter output. |
| LF M-Bus Cloud Bridge | M-Bus into LF Cloud | Reads wired M-Bus utility meters, as an M-Bus and Modbus master, and brings the readings into LF Cloud over LAN or WiFi. | For utility sub-metering and for industrial and HVAC metering. |
Authentication and limits
- API credentials and endpoint specifications are provisioned per account once an integration is scoped. No secrets, keys or endpoint URLs are published on this site.
- Webhooks use secure token-based authentication with a secret you define.
- Premium Access includes 2,000 API calls a year, and every device includes its first year of Premium. The Retriever API allows 1 call per serial number per minute.
- Data from every device goes directly to LoggerFlex servers in Canada (Montreal), over TLS 1.3 with role-based access.
BMS, SCADA and ERP
The loggers do not have to sit on your building or plant network: they reach LF Cloud on their own over WiFi or LTE, with no gateway. Your BMS, SCADA, ERP or custom dashboard then takes the data from LF Cloud, pushed by the webhook as readings arrive or pulled on its own schedule through the Retriever or Consumption API.
In the other direction, MODGATE and the LF M-Bus Cloud Bridge bring field equipment that speaks Modbus RTU or M-Bus into LF Cloud, where it is charted, reported and alarmed alongside the LoggerFlex sensors.
How to start an integration
- Tell an engineer which system receives the data, which devices or meters feed it, and whether it should pull or be pushed to.
- We scope the integration and provision your credentials and the API documentation for your account.
- For forwarding, enter your endpoint URL and security token in the cloud dashboard; readings start arriving with the next sync.
Frequently asked questions
Does LF Cloud have an API?
Yes. LF Cloud exposes a documented REST API: the Retriever API pulls historical or latest sensor readings as JSON, the Consumption API pulls metered utility data, and provisioning calls register and configure devices. Credentials and endpoint specifications are issued per account once an integration is scoped; no keys or URLs are published on the website.
Can LF Cloud push readings to our own server?
Yes, through the Active Forwarding API. LF Cloud posts each new reading to an HTTP endpoint you control as soon as it syncs, and forwards stored history in batches when a device uploads from memory. The JSON payload carries the serial number, device ID and all sensor values, and you define the security token.
How many API calls are included?
Premium Access includes 2,000 API calls a year, and every device includes its first year of Premium. The Retriever API is rate-limited to 1 call per serial number per minute. Webhook forwarding needs no polling at all.
Can LoggerFlex bring our Modbus or M-Bus equipment into LF Cloud?
Yes. MODGATE reads RS485 Modbus RTU registers and sends them to LF Cloud over WiFi or cellular, and the LF M-Bus Cloud Bridge reads wired M-Bus utility meters over LAN or WiFi. Their readings are charted, reported and alarmed like any LoggerFlex sensor, and your BMS or SCADA takes them back out through the API or the webhook.