WebSocket endpoint. Connect to wss://<base>/v1/operator/stream?devices=<comma-separated device_ids>
with the access token in the Authorization header during the WebSocket
handshake (or as a ?token=... query parameter).
The server pushes JSON telemetry frames (see TelemetryFrame schema)
for the subscribed device IDs at the platform’s configured cadence.
This endpoint cannot be tested via the standard “Try it” console — use a WebSocket client. The schema below describes one frame the server emits.
curl --request GET \
--url https://api.telluspower.example.com/v1/operator/stream{
"device_id": "dvc_a1b2c3d4e5f6",
"timestamp": "2025-03-15T11:05:00Z",
"connectors": [
{
"connector_id": 1,
"state": "charging",
"power": 6.9,
"energy_delivered": 13.1,
"soc": 58
}
]
}Documentation Index
Fetch the complete documentation index at: https://developers.telluspowergroup.com/llms.txt
Use this file to discover all available pages before exploring further.
Comma-separated list of device IDs to subscribe to.
WebSocket handshake successful. Subsequent traffic is JSON-encoded
TelemetryFrame messages, one per device per cadence interval.
A single telemetry frame pushed by the operator-side WebSocket telemetry stream (§13.2.7). The server emits one frame per device on a regular cadence (typically every few seconds) for the device IDs the client subscribed to when establishing the WebSocket connection.
curl --request GET \
--url https://api.telluspower.example.com/v1/operator/stream{
"device_id": "dvc_a1b2c3d4e5f6",
"timestamp": "2025-03-15T11:05:00Z",
"connectors": [
{
"connector_id": 1,
"state": "charging",
"power": 6.9,
"energy_delivered": 13.1,
"soc": 58
}
]
}