Build on ChargeControl
Connect your systems to the charging and energy chain.
Use REST, GraphQL, webhooks, and OCPP-based charge point connectivity to bring ChargeControl data into the tools your team already runs.
What you can build on ChargeControl
ChargeControl exposes charging, energy, and settlement data through typed APIs, events, and open charge point protocols.
REST and GraphQL APIs
Query and update charging, session, cost, and account data through typed REST and GraphQL endpoints.
Event-driven webhooks
Subscribe to session, status, and settlement events instead of polling for changes.
OCPP-based charge point connectivity
Connect charge points and manage sessions using OCPP so hardware from different vendors speaks one protocol.
Scoped access and authentication
Issue credentials scoped to the data and actions a given integration actually needs.
One data model across domains
Charging, energy, and settlement data share consistent identifiers across home, public, workplace, and depot domains.
How teams integrate with ChargeControl
Integration work follows a consistent path from access to live data in production systems.
Authenticate and scope access
Set up credentials scoped to the systems and data your integration needs.
Model vehicles, chargers, and sessions
Map your fleet, sites, and hardware into the ChargeControl data model.
Subscribe to events
Use webhooks to react to session, status, and settlement changes as they happen.
Extend reporting and workflows
Pull charging, cost, and energy data into the CRM, ERP, or billing systems your team already runs.
Build on the same data your operations team sees
ChargeControl for developers means working with the same charging, energy, and settlement data that powers day-to-day operations, rather than a separate export. REST and GraphQL APIs cover queries and updates, while webhooks push session, status, and settlement events as they happen instead of requiring polling.
Charge point connectivity runs on OCPP, so vehicles, chargers, and site hardware from different vendors integrate against one consistent protocol. Access is scoped by credential, which keeps every integration limited to the data and actions it actually needs.
Because charging, energy, and settlement records share the same identifiers across home, public, workplace, and depot domains, an integration built for one domain extends naturally as more sites and systems come online.