LotGrids Wallet API

Let your fleet's own driver app bill LotGrids charge sessions directly against each driver's sub-wallet — no payment modal, no redirect back into the LotGrids app.

What this API is for

Every LotGrids fleet partner gets a wallet. Fleet admins top it up (via the Partner Dashboard) and distribute funds into individual drivers' sub-wallets. This API is how your driver-facing app spends that money: it quotes a full charge for a driver at a given charger, and then debits the driver's sub-wallet to authorize the session — all in real time, from your own app.

Two integration paths

Path	Who calls it	Authenticates with
Server-to-server	Your fleet's backend	Your fleet's API key
Driver app	Your driver-facing mobile/web app	A short-lived driver token, minted by your backend

Your backend never hands your API key to a driver's device. It uses the key once, server-side, to mint a token scoped to that one driver — the driver app then uses only that token.

How a charge session gets billed, end to end

1Driver scans the QR code on a LotGrids charger — the code is just the charger's ID — and picks which connector their vehicle is plugged into.

2Your app asks your backend for a driver token (your backend already has one cached, or requests a fresh one with your API key via Mint Driver Token).

3Your app calls Quote Charge Session with the charger, the connector, and the driver's email, using that token. LotGrids reads the vehicle's model, battery capacity, and current charge level from the charger and returns the price of a full charge plus the driver's current sub-wallet balance.

4If the balance covers the full quote, the driver charges to full. If not, the driver can choose to charge only as much as their balance allows — your app decides the amount to send next.

5Your app calls Start Charge Session with that amount. The sub-wallet is debited atomically, LotGrids sends the prepaid amount to the charger, and dispensing starts.

6When the session ends, the charger reports what it actually dispensed. If that's less than what was prepaid — the session was interrupted, or stopped early — LotGrids automatically refunds the difference to the driver's sub-wallet. Nothing further to call.

Note: the LotGrids map app (map.lotgrids.com) bills fleet drivers the same way under the hood, using the driver's existing LotGrids sign-in instead of a minted token — that's an internal integration, not something your app needs to replicate.

Ready to try it? Head to the Quickstart.