Access ChargePoint's Web Services API for charging station status and management, understanding it is a partner-gated SOAP interface rather than an open self-serve REST API
domain: developer.chargepoint.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm you have an existing ChargePoint account with a Network Manager role, since API access is tied to an existing account and service plan rather than open signup
Contact ChargePoint developer support to request API access and a license key if you do not already have one
Build your integration against the SOAP-based Web Services API, authenticating requests using the WS-Security header pattern with your issued license key and password
Use station status calls to retrieve real-time port availability and use management calls to retrieve the list of stations tied to your organization
Confirm current auth and endpoint details directly with ChargePoint before building, since this is a partner-gated program subject to change outside public documentation
Known gotchas
This is a SOAP and XML based API, not a modern REST or OAuth API, which affects tooling choices and client library availability
Access is gated behind an existing ChargePoint account and a support-mediated request for a license key, so budget lead time for account provisioning before development can start
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?