Connectivity
Infuse-IoT Cloud connectivity workflows include MQTT access tokens and CoAP-hosted file metadata. Use the console for development and operational token generation. Use the API when a backend service needs to issue tokens or inspect file availability automatically.
MQTT Tokens
MQTT tokens are short-lived tokens scoped to an Infuse IoT organisation. They are useful for trusted clients, gateways, and development workflows that need MQTT access without exposing long-lived admin credentials.
Open Infuse IoT > API Access and select Fetch Token to generate a token for the linked Infuse IoT organisation. The console displays the token, issue time, expiry time, and a copy action.
Use POST /mqtt/token when a backend needs to generate tokens automatically. 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 for production flows. 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.
Application release detail pages in the console also show release file metadata such as CoAP path, file length, CRC, and diff length. Use that view when operators need to inspect release metadata without calling the API.
| 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 Cloud admin workflows. This is part of the current legacy Infuse-IoT Cloud access model.
For broader access guidance and the current Infuse-IoT Cloud token limitation, see API Tokens.