Getting started

The Partner API gives another system read-only access to one organisation's fleet: vehicles, live positions, trips, daily activity, alerts, driver scores and geofences. Every response is JSON over HTTPS.

Base address

https://api.routetracks.com/api/v1/partner/v1

All paths in these docs are relative to this address. For example, the vehicle list is:

GET https://api.routetracks.com/api/v1/partner/v1/fleet/vehicles

What you need

An administrator of the organisation creates an API client under Settings → Partner API and shares two values with you:

Value	Looks like	Notes
Client ID	fn_live_id_…	Not secret. Identifies your integration.
Client secret	fn_live_sk_…	Shown once at creation. Store it like a password.

A client can be limited to a list of IP addresses. If the administrator sets one, /authorize from any other address is refused. The check uses the address of the TCP connection in front of the API, after the load balancer. It does not use a forwarding header you set yourself. The token you receive is not tied to that address.

A client is also created with one or both scopes:

Scope	Calls it allows
Live snapshot (fleet.snapshot.read)	GET /vehicles. This is the credential for a live fleet poll.
Fleet data (fleet.data.read)	Every GET /fleet/* endpoint, including vehicle records, history and driver details.

GET /ping works with either scope.

Your first call in three steps

1. Get a token

curl -X POST https://api.routetracks.com/api/v1/partner/v1/authorize \
  -H "Content-Type: application/json" \
  -d '{"clientId":"fn_live_id_XXXX","clientSecret":"fn_live_sk_XXXX"}'

{
  "token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9…",
  "tokenType": "Bearer",
  "expiresIn": 3600,
  "expiresAt": "2026-10-23T13:00:00.000Z"
}

2. Check it works

curl https://api.routetracks.com/api/v1/partner/v1/ping \
  -H "Authorization: Bearer $TOKEN"

{
  "ok": true,
  "tenantId": "org_2abc…",
  "clientId": "fn_live_id_XXXX",
  "scope": ["fleet.snapshot.read", "fleet.data.read"],
  "serverTime": "2026-10-23T12:00:01.204Z"
}

3. Fetch data

curl "https://api.routetracks.com/api/v1/partner/v1/fleet/positions" \
  -H "Authorization: Bearer $TOKEN"

Next, read Authentication for how to refresh tokens, then the API reference.