Skip to main content
A contract-first API for fleet partners building an operations dashboard, a driver app, or a backend-for-frontend integration with FLO.

Integration model

The API is fleet scoped. The API key identifies exactly one fleet, so callers never send an internal fleet ID. Persist the stable opaque public IDs the API returns rather than database IDs, phone numbers, or registration numbers.

Authentication

The x-api-key header and what it scopes.

Identifiers

Prefixed opaque IDs and why to store them verbatim.

Idempotency

Idempotency-Key on mutating requests.

Pagination

limit, offset, and the metadata envelope.

Modules

Money

All monetary values are integer paise, in fields suffixed accordingly — balance_paise, energy_price_paise_per_kwh, final_cost_paise. There are no floating-point amounts. Do not divide for display until the last possible moment.

Sessions are asynchronous

A 202 Accepted on a session request means the command was accepted for processing — not that the charge point has acted on it. Poll the session to observe the outcome.

Errors

Errors share one envelope across every endpoint:
Branch on error.code. The message is written for human readers and may change.

Enforcement caveats

Restrictions are evaluated only when FLO can identify the session as belonging to the configured driver_id or vehicle_id. Where identity, SOC telemetry, or remote-stop support is unavailable, FLO enforces only the supported parts of a restriction:
  • SOC-based stop enforcement depends on the CPO or charger sending usable SOC updates for the active session.
  • Time-window and SOC stop enforcement depend on the CPO or charger supporting remote stop for the active session path.
  • Vehicle restrictions are stored even when FLO cannot yet identify the vehicle during charging; enforcement begins when vehicle identification becomes available.
Treat a stored restriction as intent, not as a guarantee. Surface the caveats above to fleet operators rather than implying enforcement is unconditional.