Skip to main content
GET/rest/vehicles/status
{ }

Sample data for Johannesburg. Change the country at the top of the page.

Every vehicle in your fleet, one API call away

Positions, trips, events, drivers and video from Cartrack telematics. Read them over REST, unlock vehicles from a phone, or send in data from your own devices.

Make your first callBrowse the API reference

Pick your integration

Fleet REST API

Read vehicle status, trips and events, manage drivers and geofences, send commands, and get webhooks when something happens.

Read the guideAPI reference

Mikey mobile SDK

Let drivers lock and unlock a vehicle over Bluetooth from your Android or iOS app, and read its lock status and fuel level.

Read the guideRequest SDK access

Telematics APIBeta

Send location and telemetry from your own devices or platform, so those vehicles show up next to the rest of your fleet.

Read the guideEvent reference

Your first call in three steps

  1. Get your API credentials

    Your Fleetweb administrator issues API credentials for each integration. How authentication works

  2. Choose the country your account is in

    Each country has its own base URL.

  3. List your vehicles

    Run the request and you get back every vehicle on the account. Full quick start

Terminal
$ curl 'https://fleetapi-za.cartrack.com/rest/vehicles' \
  --header 'Accept: application/json' \
  --user 'username:password'

Recent Fleet API releases

All release notes
  1. Version 1.26.0930.1

    [Vehicle Commands]: PUT /vehicles/{registration}/immobilise and GET /vehicles/immobilise/status are no longer listed in the API reference. Both keep serving their existing callers; new integrations should use the start-inhibit endpoints above.

    2 new features, 8 improvements, 7 fixes
  2. Version 1.26.0924.1

    [General]: Repeated failed authentication attempts are now throttled. Once an account has failed authentication too many times from the same address, further requests from that address for that account receive HTTP 429 Too Many Requests until the block expires, including requests that carry valid credentials. The response includes the X-RateLimit-Retry-At and X-RateLimit-Retry-After-Seconds headers, and error.message starts with Too many failed authentication attempts. Integrations must stop retrying on HTTP 401 Unauthorized and correct the credentials instead: retrying a rejected password in a loop is what triggers the block. See the Rate Limiting guide for details.

    3 improvements, 1 fix
  3. Version 1.26.0923.1

    [Drivers]: Deprecated the legacy positional custom_fields (custom_1..custom_8) on the driver endpoints. It is now translated from custom_field_values, and values sent in a request are still accepted for backward compatibility but no longer written. Use custom_field_values instead.

    2 new features, 6 improvements, 3 fixes

What teams build with it

Available in 27 countries across Africa, Asia-Pacific, the Middle East and Europe. See every base URL