Integrations
Connect ChargeControl to the systems you already run.
REST, GraphQL, APIs, and webhooks bring charging, energy, and settlement data into CRM, ERP, billing, and other operational systems.
What integrations provide
A consistent way to read and react to charging, cost, and account data from outside systems.
REST and GraphQL access
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 updates.
Scoped credentials
Issue access limited to the data and actions a given integration actually needs.
Consistent identifiers
Shared identifiers across domains keep integrated systems working from the same records.
How integrations connect
Most integrations follow the same path from scoped access to live, event-driven data.
Define integration scope
Identify which data and actions the target system needs before issuing access.
Connect REST or GraphQL endpoints
Bring charging, cost, and account data into the target system through typed endpoints.
Subscribe to relevant events
React to session, status, and settlement changes as they occur instead of polling.
Monitor and adjust
Track integration activity and refine scope as operational needs change.
Systems and protocols ChargeControl connects to
Integrations reach both business systems and the charging network itself.
CRM, ERP, and billing
Connect charging and cost data to the business systems finance and operations already rely on.
Charge point protocols
OCPP-based connectivity keeps the charge point layer consistent underneath integrated systems.
Roaming networks
OCPI supports connections with public charging networks and roaming partners.
Bring ChargeControl data into the systems you already run
Integrations connect the charging, energy, and settlement data inside ChargeControl to the business systems teams already depend on. REST and GraphQL endpoints handle queries and updates, while webhooks push session, status, and settlement events as they happen so integrated systems do not have to poll for changes.
Most integrations follow the same path: define the scope of data and actions needed, connect the relevant endpoints, subscribe to the events that matter, and then monitor and adjust access as operational needs change. Scoped credentials and consistent identifiers keep that process predictable as more systems connect.
On the network side, OCPP-based connectivity keeps the charge point layer consistent, and OCPI extends that reach to public charging networks and roaming partners, so integrated systems work from the same charging reality operations teams see.