Connect
Configure HTTP endpoints and MQTT connectors for your workspace.
The Connect tab is where you manage every inbound data channel for your workspace.
HTTP endpoints
A workspace can have multiple HTTP endpoints. Each endpoint has its own URL and authentication settings, letting you segment devices by access policy or environment.
Creating an endpoint
- Click + New endpoint.
- Choose an authentication method (see below).
- Click Create. The endpoint URL is shown immediately.
Requires Editor or Admin role.
Authentication
| Method | Description |
|---|---|
| None | Public — any device with the URL can POST. |
| Username / password | HTTP Basic Auth. Credentials set per endpoint. |
| Client certificate | mTLS — device presents an X.509 cert signed by the endpoint's configured CA. |
| OAuth2 | Sender presents a Bearer token issued by an OAuth2 client registered in Access. |
Client certificate (mTLS)
Each endpoint has its own trusted CA configured. Devices are provisioned with a certificate signed by that CA. Authentication is verified at the TLS handshake — no application-level secret is needed, and the private key never leaves the device.
To configure: upload the CA certificate when creating or editing an endpoint. Revoke a device by revoking its certificate at the CA level.
OAuth2
Register an OAuth2 client in the Access tab, then select it when creating the endpoint. The sender must include a valid Bearer token on every POST: Authorization: Bearer <token>.
Two client types are supported:
- Client Credentials — for devices and M2M services. The device exchanges its
client_id+client_secretfor a short-lived access token, then uses it to POST data. - Authorization Code + PKCE — for user-facing applications. The authenticated user's token is forwarded with the request.
In both cases IoTMan identifies the sender from the token, enabling per-client or per-user data attribution.
Sending data
POST <endpoint-url>
Content-Type: application/json
{"sensor":"s1","value":22.4,"ts":1710000000}Any valid JSON payload is accepted. The response is {"ok":true} on success.
To send multiple datapoints in a single request, POST a JSON array. Each item is stored as a separate datapoint:
POST <endpoint-url>
Content-Type: application/json
[{"sensor":"s1","value":22.4},{"sensor":"s2","value":18.1}]Removing an endpoint
Click the delete icon on an endpoint row. The URL stops accepting requests immediately. Data already ingested is retained.
Requires Editor or Admin role.
MQTT connectors
IoTMan can subscribe to topics on your existing MQTT brokers and ingest messages automatically.
Adding a connector
- Click + Add connector.
- Fill in the broker host and port, topic filter, and optionally a username and password.
- Click Save. The connector starts immediately.
Requires Editor or Admin role.
Pausing and resuming
Toggle the switch on any connector row to pause or resume ingestion without deleting the configuration.
Deleting a connector
Click the delete icon. Data already ingested is retained.
Requires Editor or Admin role.