Networks
Networks represent device connectivity domains. Use them when your product needs to separate devices, gateways, or deployments by a shared network identity and key.
If your deployment model does not separate devices by network, keep your network convention simple and document how your backend chooses the network used during provisioning.
Networks In The Console
Open Infuse IoT > Networks to view networks for the linked Infuse IoT organisation.
The network list shows:
- network name,
- description,
- numeric network ID,
- update time.
Create A Network
From Infuse IoT > Networks, select Add network and provide:
| Field | Use |
|---|---|
| Name | Human-readable network name. |
| Description | Operational context for the network. |
| Network ID | Numeric network identifier. |
| Key | Base64-encoded 32-byte network key. |
Treat network keys as sensitive operational material. Do not place them in public examples, repositories, browser code, or customer-visible logs.
API Workflows
Use the API when networks are created by deployment automation or need to be reconciled between environments.
| Task | Endpoint |
|---|---|
| List networks | GET /network |
| Create a network | POST /network |
For request schemas and response shapes, see the Infuse-IoT Cloud API reference.