Integrate

Every device sends its own readings with its own token. HTTP and MQTT both carry them, and both accept the same JSON body: HTTP for one request per reading, MQTT for hardware and gateways that hold one connection open.

A PLC or a Modbus device reaches Logable through a gateway that reads the equipment and publishes over MQTT. Logable never speaks Modbus itself.

Pages in this section#

• Send your first reading. From a device token to a value on a dashboard in five minutes, with HTTP or MQTT.
• Send readings over HTTP. POST a device reading to the ingest service with a device token. Payload, validation rules, error codes and rate limits.
• Publish readings over MQTT. Connect to the Logable broker over TLS with a device token and publish readings on the device's own topic.
• Send stream events. Post events to a stream when the data is not a device. Same body shape, its own token, no status field.
• Send a field the device type does not define. Add your own keys to a reading. They are stored and shown, but they never drive an alert or a forecast.
• Device tokens. How a device token works, how to rotate one without a gap, and what a revoked token sees.
• Connect a PLC or a Modbus device via a gateway. Logable ingests HTTP and MQTT. A gateway reads your PLC or Modbus registers and publishes each reading on the device's topic.
• Receive alerts as an HTTP call. Register a webhook endpoint, verify the signature, and handle retries and replays.
• Rate limits and payload limits. Which limit applies to a device, a gateway, a stream and a signed-in user, and what to do when you hit one.

Where to go next#

Device types lists the field names each type accepts, with an example payload and code samples for every language.