Double M ELDDEVELOPERS
Website ↗
REST / JSON v1
Developer portal/Hours of service
ELD INTEGRATION CONTRACT

Get an HOS summary

Read the calculated clock snapshot associated with an authorized log.

Contract referenceData endpoints are not available on this website. Examples are illustrative. No live requests are sent from this portal.

GET/v1/daily-logs/{log_id}/hos
REQUIRED SCOPEeld:hos:read

Behavior & boundaries

Clocks are independent constraints, not permission to drive or a compliance determination. Rule selection and exceptions require validated calculation logic.

A null clock means the calculation is unavailable. The sample is a 16:00 UTC snapshot; it is separate from the final daily totals.

Returns only resources authorized to the credential's carrier and integration. Driver profiles, contact details, and identity expansion are excluded.

Request parameters

log_idpath · required

Opaque reference scoped to the authorized integration. A missing or inaccessible resource returns 404.

Unsupported parameters, including driver selectors and identity expansion, are outside this contract. Read the field policy →

Response fields 200

data contains one object with the fields below. Every listed field is present; nullable values explicitly indicate unavailable information.

Field / typeDescription
log_idstringDaily-record reference.
as_ofdate-timeUTC calculation snapshot time.
rule_setstringVersioned rule identifier, not evidence of certification.
calculation_statestringWhether required inputs were available.
availableincomplete
driving_remaining_secondsinteger | nullRemaining driving-clock seconds; null if unavailable.
shift_remaining_secondsinteger | nullRemaining shift-window seconds; null if unavailable.
cycle_remaining_secondsinteger | nullRemaining cycle-clock seconds; null if unavailable.

Error responses

400 invalid parameters · 401 invalid credential · 403 insufficient scope · 404 absent or inaccessible resource · 429 rate limit · 503 unavailable.

Error envelope and retry guidance →
KEEP BUILDING WITH CONTEXTReview the data boundaries →

Find your next step.

GUIDEBuild around the log.A focused integration reference for electronic logging, engine observations, and operational record review.GUIDEAuthentication & accessA server-to-server contract with narrow scopes and carrier isolation.GUIDEData boundariesPrivacy boundaries keep driver identity outside the integration contract.GUIDEPagination & timePredictable traversal, explicit time windows, and readable units.GUIDEErrors & rate limitsSafe failures and deliberate retries for integration clients.GUIDEContract changelogChanges to the documentation and integration contract.GET · VehiclesList ELD vehicles/v1/vehiclesGET · VehiclesGet an ELD vehicle/v1/vehicles/{vehicle_id}GET · ELD devicesList ELD devices/v1/eld-devicesGET · ELD devicesGet an ELD device/v1/eld-devices/{device_id}GET · ConnectionsList connection events/v1/vehicle-connectionsGET · Engine eventsList engine events/v1/engine-eventsGET · Daily logsList daily logs/v1/daily-logsGET · Daily logsGet a daily log/v1/daily-logs/{log_id}GET · Duty statusList duty-status events/v1/duty-status-eventsGET · Hours of serviceGet an HOS summary/v1/daily-logs/{log_id}/hosGET · DiagnosticsList ELD diagnostics/v1/eld-diagnosticsGET · Audit historyList record audit events/v1/audit-events