Skip to main content

Telematics Data Ingestion

Beta

Telematics data ingestion is in beta and is enabled for a limited number of partners and customers, so its behaviour may still change.

If you are interested in sending telematics data to Cartrack, reach out to your Cartrack contact person to discuss access.

This page describes how customers or third-party data providers can deliver telematics events into Cartrack.

Who this is for​

  • Partners sending vehicle location and telemetry from their own devices/platforms
  • Customers consolidating data from multiple hardware vendors
  • Integrators evaluating payload and delivery requirements ahead of onboarding

What you send​

  • JSON events conforming to the telemetry schema in the Event specification
  • Payloads must be in UTC and ISO-8601 timestamps
  • Each event must be unique; include a stable provider-level identifier to avoid duplicates
  • The sending side can be the device itself (formatted per Cartrack requirements) or a provider’s intermediary server that forwards events on behalf of devices

Delivery expectations​

  1. Send events over HTTPS to the ingestion endpoint for your region:
    • Africa: https://af-webhooks-prod.cartrack.com/api/data/ingest/telematics
    • Asia: https://as-webhooks-prod.cartrack.com/api/data/ingest/telematics
  2. Authenticate using the X-API-KEY header that Cartrack provides for your tenant.
  3. Post one JSON event per request.
  4. Expect HTTP status codes to reflect acceptance; validation errors will be returned with detail.

Authentication​

  • Include X-API-KEY: <your-key> on every request. Keys are provisioned by Cartrack.
  • Treat the key as a secret

Data quality guardrails​

  • chassis_number (VIN) is the primary key used to match vehicles across systems. Create the vehicle in Cartrack before sending events for it: an event carrying a VIN that Cartrack does not track is accepted at the endpoint but is not processed, so nothing appears in Fleetweb for that vehicle. Automatic enrollment of unknown VINs is enabled per provider account rather than being available by default, so do not rely on it unless Cartrack has confirmed it for your account.
  • Enforce uniqueness using provider_event_id or a composite you control
  • Ensure event_ts is not in the future.
  • Use kilometers for odometer values; speed should be in km/h

Flowchart​

Next steps​

Review the detailed Event specification for field-by-field requirements and an example payload.

The interactive OpenAPI reference for the ingestion endpoint is hosted per region. Both regions serve the same contract, so use the one for the host you send to: