Chargekeeper
en
White label & API

Your charging service, under your brand.

Chargekeeper runs the operating layer. You keep the customer relationship: a driver app in your colours, published under your name, and a REST API to connect your tools.

Simulation

Your brand on the supervision platform and the app

Type your service name and pick your colour: the supervision platform and the driver app change together, before your eyes.

Primary colour
Logo (optional)

PNG, SVG, JPG or WebP, it stays in your browser.

The Chargekeeper supervision platform and driver app in your colours, down to the charts. Logo, icon, wording and publication on the App Store and Google Play are defined with you during the project.

What is yours

A shared platform, an experience in your name

Your brand experience

Driver app and documents in your identity: name, icon, colours and store publication, within the agreed scope.

REST API

Chargers, sessions, users and commands reachable from your information system, with your account permissions.

Organisations and roles

Customers, sites, users and permissions kept apart in a multi-organisation operation.

Controlled data

Exports and flows that feed your reporting, billing or support tools.

REST API

Connect your tools to the platform

The same data as the supervision interface, queried from your CRM, ERP or app. Access follows your account permissions, and the project documentation lists the available resources.

  • Charger list and live status
  • Ongoing and past sessions
  • Remote commands: start, stop, reset
A few calls
  • GET /v1/api/charging-stations
  • GET /v1/api/transactions/status/active
  • PUT /v1/api/charging-stations/{id}/remote/start
Response
{
  "count": 128,
  "result": [
    {
      "id": "LYS-06",
      "chargePointVendor": "Alfen",
      "chargePointModel": "Eve Double Pro",
      "inactive": false,
      "connectors": [
        {
          "connectorId": 1,
          "status": "Charging",
          "currentInstantWatts": 21980
        },
        { "connectorId": 2, "status": "Available" }
      ]
    }
  ]
}
Architecture

From the charger to your information system

Architecture starts from the systems actually in place. An integration is only committed once its API, data and responsibilities have been qualified.

  1. 01

    Chargers and energy

    OCPP equipment, sites, meters and energy systems.

  2. 02

    Chargekeeper

    Supervision, sessions, users, pricing, payment, roaming.

  3. 03

    Your interfaces

    Branded app, portal, REST API and exports.

  4. 04

    Your systems

    ERP, CRM, BI, finance or support, within the validated scope.

FAQ

White-label and API questions

Can the service carry only our brand?

The level of customisation depends on the offer and scope: mobile app, documents and journeys are qualified during discovery.

Does the API expose every feature?

Available resources depend on what the API exposes and on the account permissions. Requirements are checked against the documentation before any commitment.

Does Chargekeeper replace our ERP or CRM?

No. Chargekeeper runs EV charging operations and integrates with your tools once interfaces and responsibilities are defined.

Can a specific integration be connected?

Yes, after assessing the third-party API, data, security, maintenance and support model.

Let us design your charging platform

Journeys, brand, data and interfaces: we scope it before talking development.

Scope my project