Data boundaries
Privacy boundaries keep driver identity outside the integration contract.
Contract referenceData endpoints are not available on this website. Examples are illustrative. No live requests are sent from this portal.
No driver information retrieval
The API contract does not expose a driver directory, profile endpoint, lookup, search, or person identifier. This boundary applies to related objects as well as top-level responses.
- No first or last names, usernames, email addresses, or cell and telephone numbers.
- No employee numbers, driver or co-driver identifiers, license numbers, or identity documents.
- No signatures, signature images, or document download URLs.
- No comments, annotations, notes, shipping references, or other unstructured text that could contain personal information.
- No GPS coordinates, address fields, trip origins, destinations, or location history.
The narrow data that remains
Equipment references, record references, duty states, timestamps, durations, engine observations, and structured health states are included only for authorized ELD workflows. Record identifiers are opaque and scoped to a carrier and integration; they do not provide a reverse lookup to a person.
The same record may be recognizable from other information held by a recipient. Restrict access, define a purpose and retention policy, and do not use operational patterns to build a driver identity directory.
An explicit field allowlist
The downloadable schemas list the permitted fields and disallow additional properties. Future server implementations must project from domain records into these allowlisted response models, including errors. They must not serialize driver entities and then try to hide selected properties.
- Reject unsupported fields, include, expand, and driver-related selectors.
- Test nested responses and error bodies for identity leakage.
- Use fixed error messages without echoing request values.
- Apply the same restrictions to exports and any later event delivery mechanism.
Separate integrations from regulated records
These reduced responses are not a complete regulated record of duty status, roadside inspection output, or FMCSA transfer file. Required identity-bearing records belong in a separately authorized inspection workflow, outside this integration contract.
No camera, video, audio, coaching, dispatch, payroll, fuel, maintenance, or general fleet-management resources are included.