> ## 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. # Charging-record upload > After a charging session ends, the charger uploads the complete charging record (CDR). ## OpenAPI ````yaml /api-reference/openapi.json post /device/charging-records 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/charging-records: post: tags: - Charger — Reporting summary: Charging-record upload description: >- After a charging session ends, the charger uploads the complete charging record (CDR). requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/ChargingRecordUpload' example: record_id: rec_9x8y7z6w connector_id: 1 start_time: '2025-03-15T09:00:00Z' end_time: '2025-03-15T10:30:00Z' energy: 15.2 max_power: 7.2 avg_power: 6.8 cost: 12.16 meter_start: 12345.6 meter_end: 12360.8 vehicle_info: vin: LVXFA394XJ1234567 soc_start: 20 soc_end: 90 responses: '200': description: Record accepted. security: - deviceBearer: [] components: schemas: ChargingRecordUpload: type: object required: - record_id - connector_id - start_time - end_time - energy - max_power - avg_power - meter_start - meter_end properties: record_id: type: string connector_id: type: integer minimum: 1 start_time: type: string format: date-time end_time: type: string format: date-time energy: type: number max_power: type: number avg_power: type: number cost: type: number meter_start: type: number meter_end: type: number vehicle_info: $ref: '#/components/schemas/VehicleInfo' VehicleInfo: type: object properties: vin: type: string description: Vehicle Identification Number (17-char ISO 3779). soc_start: type: integer minimum: 0 maximum: 100 soc_end: type: integer minimum: 0 maximum: 100 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. ````