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.

Pick your integration

Fleet REST API

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

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.

Telematics APIBeta

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

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.1007.2

    [General]: Repeated requests for a resource that was not found are now throttled. Once the same resource path has answered HTTP 404 Not Found too many times, further GET requests for it receive HTTP 429 Too Many Requests until the block expires. The response includes the X-RateLimit-Retry-At and X-RateLimit-Retry-After-Seconds headers, and error.message starts with Too many requests for a resource that was not found. Other paths are not affected. Integrations must stop requesting a resource that answers 404 instead of retrying it. See the Rate Limiting guide for details.

    7 improvements, 4 fixes
  2. Version 1.26.1007.1

    [Carpool]: GET /carpool/bookings and GET /carpool/bookings/{booking_id} now return pickup_site_location_id, return_site_location_id and booking_purpose_id.

    5 new features, 7 improvements, 6 fixes
  3. 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