Infuse IoT

Definitions

Manage RPC, TDF, and KV definition registries for device data and commands.

Definitions describe how device payloads should be encoded, decoded, displayed, and understood by backend systems. They are the contract between firmware and Infuse IoT integrations.

Infuse IoT exposes three definition registries:

RegistryUse
RPC definitionsCommands, request/response structures, and enums used by RPC workflows.
TDF definitionsStructured telemetry definitions for device-emitted data.
KV definitionsDevice key-value entry definitions for configuration and state.

Versioned Contracts

Each registry supports a latest version and version-specific reads. Backend services should use the definition version that matches the device firmware or data source they are processing.

When adding new definitions, treat them as versioned contracts:

  • keep backward compatibility where devices in the field still use older firmware,
  • avoid changing field meaning without a new definition version,
  • update backend encoders and decoders together with firmware releases,
  • use definitions to drive display labels and decoded values instead of hard-coding payload interpretation in every integration.

RPC Definitions

RPC definitions contain commands, structs, and enums. Use them when building command payloads for POST /rpc and when decoding responses returned through RPC message reads.

TaskEndpoint
Get latest RPC definitionsGET /defs/rpc
Add RPC definitionsPOST /defs/rpc
Get RPC definitions by versionGET /defs/rpc/{version}

TDF Definitions

TDF definitions describe structured telemetry data. Use them when telemetry emitted by firmware needs consistent decoding before downstream storage or analytics.

TaskEndpoint
Get latest TDF definitionsGET /defs/tdf
Add TDF definitionsPOST /defs/tdf
Get TDF definitions by versionGET /defs/tdf/{version}

KV Definitions

KV definitions describe device key-value entries. They allow KV entry reads and updates to use decoded object values where definitions are known, instead of only raw base64 data.

TaskEndpoint
Get latest KV definitionsGET /defs/kv
Add KV definitionsPOST /defs/kv
Get KV definitions by versionGET /defs/kv/{version}

For endpoint schemas, see the Infuse IoT API reference.