HOS Logs API — TT ELD External Integration

Returns all Hours of Service log entries for a driver on a single calendar date. Each entry represents one ELD event with location, odometer, and engine-hours data.

Authentication

Header	Required	Purpose
`x-api-key`	Yes	API key
`provider-token`	Yes	Provider authentication token

Endpoint

GET/api/externalservice/hos-logs/:usdot/:driverId/?date={date}

Parameters

Parameter	In	Required	Description
`usdot`	Path	Yes	Company USDOT number
`driverId`	Path	Yes	Driver identifier (UUID)
`date`	Query	Yes	Log date in `YYYY-MM-DD` format

Example Request

bash

Response 200 OK

json

{
  "driverId": "d1e2f3a4-0000-0000-0000-000000000000",
  "date": "2026-06-25",
  "logs": [
    {
      "start_date": "2026-06-25T00:00:00.000Z",
      "event_code": 1,
      "event_type": 1,
      "address": "123 Main St, Dallas, TX",
      "coordinates": { "lat": 32.7767, "lng": -96.7970 },
      "odometer": 120450,
      "engine_hours": 3210.5,
      "note": ""
    },
    {
      "start_date": "2026-06-25T08:00:00.000Z",
      "event_code": 3,
      "event_type": 1,
      "address": "I-20 W, Fort Worth, TX",
      "coordinates": { "lat": 32.7550, "lng": -97.3308 },
      "odometer": 120650,
      "engine_hours": 3215.5,
      "note": ""
    }
  ]
}

Log Entry Fields

Field	Type	Description
`start_date`	string (ISO 8601)	Start timestamp of the duty-status segment
`event_code`	integer	ELD event code identifying the specific event within its type
`event_type`	integer	ELD event type category
`address`	string	Human-readable address at segment start
`coordinates`	object	GPS position — `lat` and `lng` as floats
`odometer`	number	Odometer reading at segment start
`engine_hours`	number	Engine hours at segment start
`note`	string	Optional driver annotation for the segment

Error Responses

Status	Meaning
400	Missing or invalid `date` parameter
401	Missing or invalid authentication headers
404	Driver not found for the given USDOT

Contact the support team for access credentials or integration assistance.