Driver login · OAuth 2.0 + PKCE

Sign drivers in without a backend.

Your app opens a ChargeIT-hosted login in your branding and gets back a short-lived token for that one driver. No API key in the app, and no second user system to build.

Your appOpens the hosted login
Hosted loginIn your branding
Driver tokenShort-lived, one driver
ChargeIT APICalled straight from the app

How it works

Four steps, no backend.

  1. Register your app

    In the developers panel: bundle IDs, redirect URIs and your client ID.

  2. The driver signs in

    On the hosted login, in your branding. PKCE ties the sign-in to your app, so an intercepted code is useless.

  3. Your app gets a token

    Short-lived and limited to that driver: their sessions, their tags, their payments.

  4. Call the driver API

    Straight from the app, with the driver’s token.

The driver API

Everything a driver app needs.

Built on the same driver accounts the ChargeIT app uses.

Find chargers

Map search, live availability and prices.

Charge

Start and stop by QR code or connector, with live kWh, power and cost.

Account

Profile, RFID tags, payment methods, history and receipts.

Events

Session updates by webhook, or push notifications sent for you.

Keys and tokens

Why apps get tokens, not keys.

An API key never goes inside a mobile app, where anyone could extract it. Your backend uses keys; each driver in your app gets a token of their own.

  • One driver per tokenA token reaches only that driver’s own data.
  • Data stays on ChargeIT’s sideDrivers’ personal and payment data stay with ChargeIT, under GDPR controls.
  • No second user systemDrivers sign in with the same accounts the ChargeIT app uses.

API keys

For servers. Scopes and a rate tier per key.

Driver tokens

For apps. One driver, short-lived.

Questions

Driver login, answered.

Do I need my own backend to sign drivers in?

No. The hosted login and the driver token are all your app needs.

Can the login page carry my brand?

Yes. The hosted login is shown in your branding.

How do I get access?

The developers panel is switched on per organisation. Request API access and we’ll set up your organisation and scopes.

Build your own driver app.

Tell us about your app and we’ll enable driver login for your organisation.

Request API access