Getting Started

Prerequisites

• Complete the Onboarding process — your AWS account ID must be registered before requests will be authorized
• Your provider name issued during onboarding, sent as the X-Provider-Key header (aggregators only — see POST /v2/telemetry)
• AWS credentials configured locally (~/.aws/credentials or environment variables)

Endpoints

Data transmission requirements

• Submit updates via POST /v2/telemetry for each position or signal change
• Updates must be chronologically ordered by timestamp per asset — payloads with a signalTimestamp older than the last accepted timestamp for that asset will be accepted but not processed

Send your first payload

All requests must be signed with SigV4a. Once signed, POST to /v2/telemetry:

{
  "payloadId": "550e8400-e29b-41d4-a716-446655440000",
  "carrier": "AZNG",
  "signalTimestamp": 1751989541000,
  "assetIdentifier": { "id": "OT18049", "type": "HOSTLER", "operator": "AZNG" },
  "gps": { "latitude": 47.6062, "longitude": -122.3321, "inMotion": true }
}

A 202 Accepted response confirms the payload was received. The body contains a requestId for support tracing.

Error handling