The Autonautics Lite API

Read your fleet's vehicles, positions, trips and alerts from your own systems. The API only reads: it can never change anything.

Your own key

An Admin makes one in the app, under Account → API keys. It reads your own fleet, and makes 60 calls a minute.

Try it first, on our demo

Ask for a demo: with your demo login comes a demo key, by email. It reads the demo's made-up vehicles, makes 10 calls a minute, and stops when the demo ends.

Book a demo

Calls · What you can read · Times, periods and pages · Errors

Reading your data with an API key

Your own systems, such as an ERP, a dispatch tool or a spreadsheet, can read your fleet’s data. Make a key under Account → API keys, and send it with every call. A key only reads: it can never change anything.

Every call is a GET to https://fleet.example.com/api/public/v1, with the key in the Authorization header. The answer is JSON. For example, your vehicles:

KEY=lk_EXAMPLEyourkey
curl -H "Authorization: Bearer $KEY" "https://fleet.example.com/api/public/v1/vehicles"

and the trips of one day:

curl -H "Authorization: Bearer $KEY" \
  "https://fleet.example.com/api/public/v1/trips?from=2026-10-01T00:00:00Z&to=2026-10-02T00:00:00Z"

Keep the key on your server, like a password. Don’t put it in a web page: browsers can’t call the API, and anyone who sees the page would see the key. If a key may have leaked, revoke it and make a new one.

What you can read

`GET /vehicles`

Your vehicles, by registration. Takes: page.

id: The vehicle’s id, for the other calls.
registration: Such as KA01AB1234.
group: Its depot or branch, or null.
makeModel, driverName: Only when switched on under Vehicles → Settings; null when not filled in.

`GET /positions/latest`

Each vehicle’s latest position, by registration. All but the vehicle are null for one that has never reported. Takes: vehicleId (optional), page.

vehicleId, registration: The vehicle.
time: When the tracker took the position, in UTC.
latitude, longitude: Where it was, in degrees.
speedKmh, course: Its speed in km/h, and its heading in degrees from north.

`GET /trips`

Trips under way in the period, as on the Trips report: by registration, then oldest first. Takes: from, to, vehicleId (optional), page.

vehicleId, registration, group: The vehicle.
startTime, endTime: When the trip started and ended, in UTC.
start, end: Where, as latitude and longitude.
distanceKm, maxSpeedKmh: How far it went, and its top speed.

`GET /alerts`

Alerts raised in the period, oldest first. Takes: from, to, page.

id, time: The alert, and when it happened, in UTC.
type: geofence, speeding or offline.
vehicleId, registration: The vehicle.
what, where: As the Alerts screen says it, such as “Left Okhla depot”.
acknowledgedAt: When someone acknowledged it, or null.

Times, periods and pages

Times are in UTC, written like 2026-10-01T08:05:00Z. Give from and to the same way.
A period is at most 31 days, and goes back only as far as your history is kept. The answer’s historyFrom says where that starts.
Lists come in pages of up to 500 in data. When nextPage isn’t null, ask again with page= that number.
Each key can make 60 calls a minute.

Errors

An error answers with its status and a title saying what was wrong.

400: Something asked is wrong, such as a missing period or one longer than 31 days. The answer says what.
401: No key, a wrong key, a revoked key, or your account is suspended. The answer is the same for each.
403: API access, or the screen the data comes from, isn’t part of your plan. Ask us to switch it on.
404: That vehicle isn’t one of yours.
429: More than 60 calls in a minute with one key, or many wrong keys from one address. Wait for the seconds in the Retry-After header.