Connectivity
Infuse IoT connectivity workflows are API-led. Backend services issue short-lived MQTT tokens for trusted clients and inspect CoAP file availability where file-based device workflows are used.
MQTT Tokens
Use POST /mqtt/token to generate an organisation-scoped MQTT token. The request includes:
| Field | Use |
|---|---|
organisationId | Organisation the token is scoped to. |
ttlSeconds | Token lifetime, from 60 seconds to 86400 seconds. |
The response includes the token, issuedAt, and expiresAt.
Issue MQTT tokens from a trusted backend. Do not place long-lived admin credentials in device apps, customer browsers, or public code to let clients mint their own tokens.
CoAP Files
The CoAP file endpoints expose file listing and file statistics for workflows that rely on files hosted through the CoAP server.
| Task | Endpoint |
|---|---|
| List files | GET /coap/files |
| Read file statistics | GET /coap/file/{filename}/stats |
Admin API Key
POST /admin/apiKey generates an API key for Infuse IoT admin workflows. This is part of the current legacy Infuse IoT access model.
For broader access guidance and the current Infuse IoT token limitation, see API Tokens.