CarTrack

Website: https://www.cartrack.co.za/ 

 

⚠️ Work in Progress ⚠️

This integration requires assistance from our support team for setup and configuration. Please contact our support team at support@earthranger.com and we’ll guide you through the process to ensure everything is set up correctly.

We are actively working to make this integration self-service in the future. Stay tuned for updates!


Need this documentation before it's ready?
Let us know at support@earthranger.com. We're happy to help.


Prerequisites

Data Source

  1. CarTrack account username.

  2. CarTrack API Password.  You may obtain this value by logging in to your CarTrack account, select Settings, API Settings, and create an API Password under “Admin Credentials”.

  3. CarTrack API endpoint (e.g., https://fleetapi-zw.cartrack.com/rest/, or https://fleetapi-mz.cartrack.com/rest/, or https://fleetapi-za.cartrack.com/rest/ )

Data Delivery

  Credentials or an authentication token to access the delivery system.

Configuration

Notes for Support (click to expand)

Go to Gundi v1.

Go to the Inbound Integrations and select Add Integration.

Follow the steps below to configure the integration:

Name: Enter a suitable name (e.g., "Sitename - CarTrack")

Owner:  Select the integration's owner

Type: CarTrack

Provider Key:  Leave empty. It will automatically give it a name.

Default Device Group: Leave empty. Gundi will automatically create a default group.

Endpoint:  Endpoint provided by the user (e.g., https://fleetapi-zw.cartrack.com/rest, or https://fleetapi-mz.cartrack.com/rest, or https://fleetapi-za.cartrack.com/rest)

Token:  Leave empty

Login/Password:  CarTrack Username and "API Password" provided by the user

State:   

{}

Click Save

Configure the Default Device Group to select the destination site. 

 
 

Data Pull Frequency

Approximately every 10 minutes.

 

Characteristics

  • This integration retrieves data including latitude, longitude, timestamp, speed, odometer reading, ignition status, event location, and device ID.

 

Data Delivery

The time it takes for data to appear in your destination system depends on several factors, such as latency introduced by the source, network conditions, and intermediary systems. While these factors may vary, Gundi typically checks for available data at scheduled intervals (approximately every 10 minutes).

If data is not available in your system after this interval, please check the source of the data for its availability. If the issue persists, contact our Support team for assistance.

 

Tags: Data Provider,  Vehicle Tracking, Movement Data, Gundi v1, Pull Integration
Last Update: July 8, 2025