> ## 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. # Real-time telemetry upload > Periodic upload of real-time electrical telemetry (typically every 5 seconds during charging or discharging). Supports single-phase and three-phase via the optional `phase_details` block. **Related:** proposed component-level fields (contactor cycles, fan RPM, isolation tests, V2G inverter health) are described in [Proposed Extensions](https://developers.telluspowergroup.com/diagnostics/proposed-extensions). ## OpenAPI ````yaml /api-reference/openapi.json post /device/telemetry openapi: 3.1.0 info: title: Tellus Open Platform API version: 1.3.0 summary: Charger-platform integration API for CPMS, EMS, aggregators, and chargers. description: > The Tellus Open Platform API enables Charging Point Management Systems (CPMS), Energy Management Systems (EMS), aggregators and chargers themselves to integrate with the Tellus charging-platform infrastructure. The API is divided into three logical surfaces: - **Operator-side API** (`/v1/operator/...`) — used by CPMS, EMS, and aggregators to query the fleet, retrieve charging records, control chargers, schedule charging, issue load-flexibility commands, and subscribe to a real-time telemetry WebSocket. - **Charger-side API** (`/v1/device/...`) — used by chargers themselves for registration, heartbeat, telemetry, event reporting, charging-record upload, command fetching (long-polling), command-status reporting, and firmware-upgrade status. - **Operator-to-operator interop (legacy)** — an older roaming-style interface (PascalCase, PUT-based) used for data exchange between operator platforms, modelled after China's national charging-interop standard. Most modern partners should integrate via the Operator-side API instead. All requests use HTTPS (TLS 1.2 or higher). Plain HTTP is not supported. All bodies are `application/json`. Timestamps are ISO 8601 UTC. Energy is in kWh, power in kW, current in A, voltage in V, temperature in °C, and SOC is an integer percentage 0–100. Optional request signing using HMAC-SHA256 is supported for high-security operations (see §2.2.4 of the v1.3 specification). contact: name: Tellus Power — Platform Team url: https://www.telluspowergroup.com license: name: Proprietary — Tellus Power Group servers: - url: https://api.telluspower.example.com/v1 description: > Production (HOSTNAME PENDING). The v1.3 specification uses `api.chargingplatform.com` as a placeholder; the real production hostname has not yet been confirmed by the developer team. - url: https://api-test.telluspower.example.com/v1 description: | Test / Sandbox (HOSTNAME PENDING). To be confirmed by the developer team. security: [] tags: - name: Operator — Authentication description: OAuth2 client-credentials grant for CPMS / EMS / Aggregator integrations. - name: Operator — Sites & Devices description: >- Read-only resource queries — sites accessible to the authenticated client, and per-device detail with connector states. - name: Operator — Remote Control description: >- Initiate charging, stop charging, V2G discharge, and set charging schedules remotely. - name: Operator — Charging Records description: Historical session data (CDR — Charging Detail Records). - name: Operator — Energy & Flexibility description: >- Aggregated energy time-series and load-flexibility / demand-response control. - name: Operator — Commands description: Track execution of issued commands. - name: Operator — Telemetry Stream (WebSocket) description: >- Real-time telemetry subscription via WebSocket. Documented here for reference; the connection is established outside the OpenAPI request/response model. - name: Charger — Provisioning description: First-time device registration and access-token issuance. - name: Charger — Reporting description: Heartbeat, real-time telemetry, event reporting, charging-record upload. - name: Charger — Commands description: Long-polling for pending commands and reporting their execution status. - name: Charger — Firmware description: Firmware upgrade status reporting. - name: Operator-to-operator (legacy interop) description: | Older roaming-style interface (PascalCase fields, PUT methods) used for data exchange between operator platforms. Modern partners should normally integrate via the Operator-side API instead. externalDocs: description: >- Tellus Power developer documentation — guides, diagnostics, runbooks, and proposed API extensions url: https://developers.telluspowergroup.com paths: /device/telemetry: post: tags: - Charger — Reporting summary: Real-time telemetry upload description: > Periodic upload of real-time electrical telemetry (typically every 5 seconds during charging or discharging). Supports single-phase and three-phase via the optional `phase_details` block. **Related:** proposed component-level fields (contactor cycles, fan RPM, isolation tests, V2G inverter health) are described in [Proposed Extensions](https://developers.telluspowergroup.com/diagnostics/proposed-extensions). requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/TelemetryUpload' example: timestamp: '2025-03-15T10:30:05Z' connector_id: 1 state: charging voltage: 220.5 current: 32 power: 7.04 energy_delivered: 12.3 soc: 55 temperature: 35.2 responses: '200': description: Telemetry accepted. security: - deviceBearer: [] externalDocs: description: >- Proposed component-level telemetry fields (contactor cycles, fan RPM, isolation tests, V2G inverter health) url: >- https://developers.telluspowergroup.com/diagnostics/proposed-extensions components: schemas: TelemetryUpload: type: object required: - timestamp - connector_id - state - voltage - current - power - energy_delivered properties: timestamp: type: string format: date-time connector_id: type: integer minimum: 1 state: type: string enum: - idle - charging - discharging - fault voltage: type: number current: type: number power: type: number energy_delivered: type: number soc: type: integer minimum: 0 maximum: 100 temperature: type: number phase_details: $ref: '#/components/schemas/PhaseDetails' PhaseDetails: type: object properties: phase_a: $ref: '#/components/schemas/PhaseDetail' phase_b: $ref: '#/components/schemas/PhaseDetail' phase_c: $ref: '#/components/schemas/PhaseDetail' PhaseDetail: type: object required: - voltage - current properties: voltage: type: number current: type: number securitySchemes: deviceBearer: type: http scheme: bearer bearerFormat: JWT description: | Charger-side bearer token. Obtained by exchanging `device_id` and `device_secret` (issued at registration) at `/v1/device/token`. Valid for 24 hours. ````