Subscribe to real-time station status and alarm notifications from the ChargePoint Web Services (partner) API
domain: chargepoint.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm the partner API plan includes notification access, since notification subscription methods are gated by API plan and access rights separately from basic station-query methods.
Register a notification subscription for the station or organization scope covering the event types needed — e.g. station_usage_status_change, station_alarm, station_reservation_enabled — per ChargePoint's Web Services Programmer's Guide.
Authenticate outbound webhook deliveries and inbound calls consistently with the SOAP WS-Security scheme (license key and account credential in the SOAP header) ChargePoint uses for its Web Services API.
Process incoming status-change notifications idempotently, since network retries or duplicate delivery can resend the same event; key on the station/port ID plus event timestamp to dedupe.
Fall back to periodic getStationStatus polling for the same stations as a reconciliation safety net, since webhook delivery gaps during ChargePoint-side incidents won't self-heal without an independent poll.
Known gotchas
Notification methods are not universally available — some ChargePoint partner tiers only expose polling methods like getStationStatus, and teams discover the gap only after building against notification-based assumptions.
The API is SOAP-based with WS-Security, not a modern REST/JSON webhook payload — teams expecting typical REST webhook tooling need a SOAP client/parser in the receiving pipeline.
Event types and payload fields differ across API Programmer's Guide versions (e.g. 4.1 vs 5.0) — confirm which version the account is provisioned against before building parsing logic around a specific guide's field names.
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?