Build around the log.

One contract. A clear boundary.

Connect systems around the records that matter: vehicle connections, engine observations, duty-status events, and hours-of-service summaries. This reference keeps the integration surface focused on electronic logging.

This portal publishes the integration contract. Data endpoints are not available on this website. Request and response examples use fabricated records; the portal never sends live API requests.

Read your first request

Start with the vehicle reference, then follow the related connection, device, and log references. Every example uses an API_BASE_URL environment variable. Supply a separately provisioned API origin before running a request; doublem.io is the documentation website.

• Review authentication and authorization scopes.
• Choose the smallest ELD resource needed for your workflow.
• Read the parameter rules and response field definitions.
• Import the downloadable OpenAPI contract or Postman collection into your local tooling.

export API_BASE_URL="https://api.example.invalid"
# Reserved example only. Replace with a provisioned API origin.
# Load ACCESS_TOKEN from your secret store, not source control.
curl "$API_BASE_URL/v1/vehicles?limit=25" \
  --header "Authorization: Bearer $ACCESS_TOKEN"

A deliberately focused surface

• ELD-connected vehicles and device metadata.
• Connection health and source-quality engine events.
• Daily log summaries, duty transitions, and HOS clocks.
• ELD diagnostics and structured audit events.

Operational data, without a people directory

There are no driver-profile or driver-lookup endpoints. Names, contact information, identity documents, signatures, and person identifiers are excluded. Resource references identify records and equipment within an authorized integration.

Operational records are still sensitive and can reveal patterns. Treat them as access-controlled data, not as anonymous public information. Read the data-boundaries guide before designing storage or exports.