Connector Ingest

Customer-owned connectors run outside Fleet Core. They map third-party fleet systems into Fleet Core ingest payloads.

Required HMAC Headers

Content-Type: application/json
X-Connector-Key: <connector-key>
X-Ingest-Timestamp: <utc-iso-timestamp>
X-Ingest-Nonce: <unique-nonce>
X-Ingest-Signature: v1=<hex-hmac-sha256>

Signature Base String

v1
<HTTP_METHOD>
<PATH>
<X-Ingest-Timestamp>
<X-Ingest-Nonce>
<sha256 hex of raw request body>

The path must be exact. For telemetry, use /ingest/http/raw.

Endpoints

Endpoint	Purpose
`POST /ingest/http/raw`	GPS, CAN, and telemetry payloads
`POST /ingest/http/provisioning/vehicles`	Stage vehicle candidates
`POST /ingest/http/provisioning/drivers`	Stage driver candidates
`POST /ingest/http/tachograph/download-result`	Push tachograph artifacts
`GET /ingest/http/logs?limit=20`	Connector-scoped debug receipts and provisioning status

Debug Logs

GET /ingest/http/logs is signed with the same HMAC headers. Use an empty raw body for the signature and sign the path /ingest/http/logs without the query string.

The response is scoped to the authenticated connector and includes recent raw ingest receipts, staged provisioning items, and hints such as missing platform vehicleId when telemetry was accepted but cannot be normalized yet.

Retry Rules

Retry 429 and 5xx with exponential backoff. Generate a new nonce and signature for each retry. Stop on 401 and 403 until credentials or connector status are fixed.

Idempotency

Telemetry deduplicates by connector, path, payload hash, identifiers, and event timestamp. Provisioning deduplicates by connector, customer, resource type, and externalId.