/IOTCONNECT™ Message Protocol 1.0 defines the data structures for device-to-cloud and cloud-to-device communication. Use this specification to build custom SDKs when the provided SDKs do not fit your hardware or memory constraints.
/IOTCONNECT™ platform provides Various SDKs for different languages and platforms. however, These SDKs may not be suitable for devices with strict memory, CPU, or hardware constraints.
/IOTCONNECT™ provides you the ability to build your own SDKs using the same protocol that /IOTCONNECT™ SDKs use internally. Below is the complete developer documentation to build an SDK in any language that supports your device.
To start the process, call the Discovery API by passing parameters to fetch the Identity Endpoint. You need: CPID, supported language, version, and environment.
The Discovery API returns the base URL for subsequent Identity calls specific to your account and region.
On successful Discovery call, you receive the URL of the Identity API. This API provides additional values required to establish the device connection, send telemetry data, and manage device lifecycle.
D2C message data structures for communication with /IOTCONNECT™:
View D2C Message Specifications →
Message types for communication with /IOTCONNECT™ using Device SDK or custom SDK:
Device Telemetry: Standard sensor data payload with attribute key-value pairs and timestamp.
OTA Acknowledgement: Device confirms firmware update receipt, download progress, or installation status.
Device Acknowledgement Command: Device confirms command execution with success / failure status.
Gateway Device Telemetry: Parent device sends telemetry on behalf of child devices with child device ID.
Edge Device Telemetry: Locally processed / aggregated data from edge computing pipeline.
Edge Device Rule Match: Telemetry that triggered a local edge rule evaluation.
Twin Update Property: Device reports updated property values to synchronize with cloud twin.
Offline Telemetry: Buffered data sent after connectivity is restored with original timestamps.
Watch the complete walkthrough video showing the end-to-end process of establishing Device-to-Cloud (D2C) communication, publishing telemetry data, and validating device data with the IoTConnect platform.
C2D message data structures received by the device:
View C2D Message Specifications →
Message data structures received from /IOTCONNECT™:
Device Command: Remote command execution with optional parameters and acknowledgment requirement.
OTA Command: Firmware update notification with download URL, version, and checksum.
Module Command: Command targeting a specific software module on the device.
Template Attributes Change: Notification that template attributes have been modified in the portal.
Template Settings Change: Notification that template settings/shadow properties have changed.
Rule Change Command: Notification that device rules have been updated.
Device Change Command: Notification that device configuration has been modified.
Password Change Command: Notification to rotate device authentication credentials.
Hard Stop Command: Immediate device disconnection instruction from the platform.
Device Twin Message: Desired property update from cloud to synchronize device state.
Device Attributes: Full attribute list refresh pushed when template changes.
Message Protocol 1.0 is the legacy format. For new device integrations, use Device Message 2.1 which provides enhanced features including device identity messages, child device management, and improved acknowledgment handling.
