Telematics Data Ingestion

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

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

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
- Europe: https://eu-webhooks-prod.cartrack.com/api/data/ingest/telematics
Authenticate using the X-API-KEY header that Cartrack provides for your tenant.
Post one JSON event per request.
Expect HTTP status codes to reflect acceptance; validation errors will be returned with detail.

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

chassis_number (VIN) is the primary key used to match vehicles across systems; create the vehicle in Cartrack first before sending events or they will be rejected.
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

Review the detailed Event specification for field-by-field requirements and an example payload. See the ingestion endpoint reference at https://docs-af-webhooks-prod.cartrack.com/api/telematics-ingest#tag/Data-Ingestion.