Double M ELDDEVELOPERS
Website ↗
REST / JSON v1
ELD INTEGRATION CONTRACT

List ELD vehicles

Read the equipment references participating in the authorized ELD integration.

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

GET/v1/vehicles
REQUIRED SCOPEeld:vehicles:read

Behavior & boundaries

This is not a general fleet or driver directory. Assigned-person details and identity expansion are excluded.

Results are ordered by vehicle_id.

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

Request parameters

limitinteger · optional

Records per page. Default 25; minimum 1, maximum 100.

cursorstring · optional

Opaque next_cursor from the previous response. Keep the same filters. Null ends the traversal.

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

Response fields 200

data is an array of the objects below. next_cursor is a string or null. Every listed field is present; nullable values explicitly indicate unavailable information.

Field / typeDescription
vehicle_idstringOpaque equipment reference, scoped to this integration.
unit_numberstringEquipment unit label; must not contain a person’s name.
connection_statestringMost recent ELD connection state.
connecteddisconnectedunknown
last_observed_atdate-time | nullLast accepted observation; null if none exists.

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