Mobile API · v1

Build against the same fleet your portal runs on.

A JSON API over the core fleet operations, scoped to one company by the credential you authenticate with. Read and write the same records the portal does — nothing is a separate copy.

Vehicles, drivers and depots
Work orders and maintenance schedules
Fuel logs and charging sessions
Breakdown logs and engine diagnostics
Driver schedules and reassignments
A read-only dashboard summary

Machine authentication — exchange a client credential for a token

curl -X POST /api/auth/token \
  -H 'Content-Type: application/json' \
  -d '{"clientId":"...","clientSecret":"..."}'

# then, on every request
Authorization: Bearer <token>

Tokens are short-lived and scoped to the company the credential was issued for. Issue and regenerate them on the portal's Mobile App Access screen.

FleetManagement System

Sign in with your portal account to read the documentation and try real requests. This is a human login, separate from the mobile app's own API-client credential — it is only here so the docs page knows who is asking.

Need credentials for an automated integration instead? That is a separate, company-issued client id and secret — see the portal's Mobile App Access screen. This sign-in is only for a person exploring the docs.