Integrate the ChargePoint API to retrieve station availability and initiate charging sessions for fleet management
domain: chargepoint.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Apply for ChargePoint API access through the ChargePoint developer program and obtain OAuth 2.0 client credentials for the sandbox environment.
Authenticate via the OAuth 2.0 client credentials or authorization code flow to obtain an access token; include it as a Bearer token in all API requests.
Query the station search endpoint with geographic coordinates or organization ID to retrieve stations and their EVSE availability status.
For fleet use cases, retrieve the list of stations assigned to your organization's fleet account and check port-level status (AVAILABLE, IN_USE, FAULTED).
Initiate a remote charging session by calling the start session endpoint with the station ID, port number, and driver credential token; poll session status or subscribe to webhooks.
Retrieve session history and energy data from the session summary endpoint for fleet energy reporting and cost allocation.
Known gotchas
ChargePoint uses a device RFID credential model alongside app credentials; fleet integrations often require pre-registering driver cards or app credentials before remote start is permitted.
Session data latency: energy (kWh) delivered values in real-time session responses may be updated at intervals (not continuous streaming) — do not treat them as instantaneous meter readings.
ChargePoint's API has separate endpoints and auth scopes for depot (fleet) vs. public network management; request only the scopes relevant to your use case to avoid access errors.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?