EV Connect

EV Connect Sessions API

Start, stop, and retrieve charging sessions and transaction records, including energy delivered and usage tracked in real time. Endpoints and base URL are not publicly documented; access is partner/sales-gated via the EV Connect API Gateway.

GitHub OpenAPI

Documentation

📖
Documentation
https://www.evconnect.com/platform/

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/ev-connect/refs/heads/main/openapi/ev-connect-openapi.yml

Other Resources

🔗
PostmanCollection
https://raw.githubusercontent.com/api-evangelist/ev-connect/refs/heads/main/collections/ev-connect.postman_collection.json
🔗
OpenCollection
https://raw.githubusercontent.com/api-evangelist/ev-connect/refs/heads/main/collections/ev-connect.opencollection.json

OpenAPI Specification

ev-connect-openapi.yml Raw ↑ 
openapi: 3.0.1
info:
  title: EV Connect API Platform
  description: >-
    EV Connect (part of Schneider Electric) operates a charge point management
    platform (CPMS) whose open, standards-based APIs are exposed through an EV
    Connect API Gateway with documentation and service plans. The platform
    covers stations / charge points, charging sessions, connectors, drivers,
    pricing / plans, and event-driven integrations, alongside OCPP station
    certification and OCPI roaming.

    EV Connect does not publish a public API reference: base URL, endpoint
    paths, request/response schemas, and authentication details are gated
    behind a partner/sales relationship and the API Gateway developer portal.
    Because no public, machine-readable contract is available, this document
    intentionally declares no servers and an empty `paths` object rather than
    fabricating endpoints. It should be reconciled once partner documentation
    is obtained.
  termsOfService: https://www.evconnect.com/legal/
  contact:
    name: EV Connect Development
    email: development@evconnect.com
    url: https://www.evconnect.com/platform/
  version: '0.0'
# No public base URL is documented. Access is via the EV Connect API Gateway
# under a partner/sales agreement; the server URL is not published.
servers: []
# No public endpoints are documented. Paths are intentionally left empty to
# avoid fabrication; populate on reconciliation with partner documentation.
paths: {}