> ## 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. # Query charge-point information (legacy) > Legacy interface (§3 of the v1.3 spec). Implemented by the charging operator and called by a peer "data-demander" platform. PascalCase request and response fields, PUT method. ## OpenAPI ````yaml /api-reference/openapi.json put /customer/query_station_info 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: /customer/query_station_info: put: tags: - Operator-to-operator (legacy interop) summary: Query charge-point information (legacy) description: | Legacy interface (§3 of the v1.3 spec). Implemented by the charging operator and called by a peer "data-demander" platform. PascalCase request and response fields, PUT method. requestBody: required: true content: application/json: schema: type: object properties: LastQueryTime: type: string description: >- Last query time, format `yyyy-MM-dd HH:mm:ss`. Empty queries all. PageNo: type: integer default: 1 PageSize: type: integer default: 10 example: LastQueryTime: '2024-01-08 15:30:00' PageNo: 3 PageSize: 20 responses: '200': description: Charge-point list returned. content: application/json: schema: type: object properties: PageNo: type: integer PageCount: type: integer ItemSize: type: integer ChargePoints: type: array items: $ref: '#/components/schemas/LegacyChargePoint' components: schemas: LegacyChargePoint: type: object description: Legacy roaming-style charge-point representation. required: - ChargeBoxId - CreateTime - Type - Power - Longitude - Latitude - Connectors properties: ChargeBoxId: type: string maxLength: 64 description: Unique device code. CreateTime: type: string description: ISO 8601 format. Type: type: string enum: - DC - AC Power: type: integer minimum: 1 description: Maximum power (kW). Longitude: type: number minimum: -180 maximum: 180 Latitude: type: number minimum: -90 maximum: 90 Connectors: type: array items: $ref: '#/components/schemas/LegacyConnector' minItems: 1 LegacyConnector: type: object description: Legacy roaming-style connector representation. required: - ConnectorId - Status properties: ConnectorId: type: integer minimum: 0 Status: type: string enum: - Available - Working - Fault ````