ELD INTEGRATION CONTRACT

List engine events

Read source-qualified engine observations relevant to electronic logging.

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

GET/v1/engine-events

REQUIRED SCOPEeld:events:read

Behavior & boundaries

This is an ELD observation feed, not a diagnostic scanner, location feed, or maintenance API.

Null values remain unavailable. Do not substitute phone GPS for missing ECM measurements.

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

Request parameters

fromdate-time · required

Inclusive UTC start. Required; range cannot exceed 31 days.

todate-time · required

Exclusive UTC end. Must follow from.

vehicle_idstring · optional

Optional equipment reference; only resources authorized to this integration.

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 / type	Description
`event_id`string	Opaque observation reference.
`vehicle_id`string	Equipment reference.
`recorded_at`date-time	UTC capture time.
`source`string	Origin of the measurement. `ecm`
`quality`string	Quality of the observation. `validstaleunavailable`
`engine_power`string	Observed engine-power state. `onoffunknown`
`vehicle_motion`boolean \| null	Whether motion was observed; null if unavailable.
`distance_meters`number \| null	Accumulated ECM distance in meters; null if missing.
`engine_seconds`integer \| null	Accumulated ECM engine operating time in seconds.

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 →

curl --request GET \ --url "${API_BASE_URL}/v1/engine-events?limit=25&from=2026-10-15T00%3A00%3A00Z&to=2026-10-16T00%3A00%3A00Z" \ --header "Authorization: Bearer $ACCESS_TOKEN" \ --header "Accept: application/json"

using var client = new HttpClient { BaseAddress = new Uri(Environment.GetEnvironmentVariable("API_BASE_URL")!) }; client.DefaultRequestHeaders.Authorization = new System.Net.Http.Headers.AuthenticationHeaderValue( "Bearer", Environment.GetEnvironmentVariable("ACCESS_TOKEN")); using var response = await client.GetAsync("/v1/engine-events?limit=25&from=2026-10-15T00%3A00%3A00Z&to=2026-10-16T00%3A00%3A00Z"); response.EnsureSuccessStatusCode(); var json = await response.Content.ReadAsStringAsync();

{ "data": [ { "event_id": "evt_example_engine_1", "vehicle_id": "veh_example_014", "recorded_at": "2026-10-15T16:00:00Z", "source": "ecm", "quality": "valid", "engine_power": "on", "vehicle_motion": false, "distance_meters": 482160000, "engine_seconds": 24012000 } ], "next_cursor": null }