Galadri

Telematics

Connect vehicle telemetry providers and map Galadri vehicles to provider vehicle IDs.

DIMO is available self-serve in the Galadri Console. Enable it from the Credentials page, save your organization's DIMO client ID and encrypted DIMO API key, and store the DIMO token ID on each matching Galadri vehicle. For Geotab, Samsara, and other telematics providers, contact Galadri so we can scope the integration and credential flow with you.

Provider availability

DIMO is the self-serve provider today. Geotab, Samsara, and other fleet telematics providers are available through a contact-us setup path because each deployment usually needs customer-specific account access, data contracts, and rollout validation.

Matching rule

Galadri reads telemetry for a Galadri vehicle by looking up that vehicle's telemetry_system_id. For DIMO, store the DIMO vehicle token ID there as a string. This field is returned by the vehicle REST API, but it is intentionally hidden from the AI agent and from agent-managed writes.

Organization-owned auth

Each organization uses its own DIMO developer app. Galadri encrypts the DIMO API key and uses it server-side only to request DIMO developer and vehicle tokens. Vehicle reads fail closed when the DIMO vehicle is not shared with that organization's DIMO app.

Setup

  1. 1. Open the Credentials page and choose Telematics, then DIMO.
  2. 2. Enter your DIMO client ID and DIMO API key. Configure your DIMO app with this redirect domain if DIMO requires it: https://galadri.com.
  3. 3. Share the relevant vehicles with your organization's DIMO app. Galadri will use DIMO's token exchange to enforce those vehicle permissions at read time.
  4. 4. When you create or update a Galadri vehicle, set telemetry_system_id to the DIMO token ID that Galadri should query.

Vehicle Sync

Use Galadri's existing vehicle CRUD API to keep the Galadri-side records in sync with the vehicles you create or remove in DIMO. When your system adds a vehicle on the DIMO side, create or update the matching Galadri vehicle record, keep the VIN accurate, and set telemetry_system_id to the DIMO token ID. Galadri uses the stored token ID to exchange for a vehicle JWT and query DIMO telemetry. When a vehicle is removed, remove or archive it on the Galadri side as well.

Example

POST /v1/vehicles
{
  "user_id": "user_123",
  "year": 2024,
  "make": "Ford",
  "model": "Transit",
  "nickname": "Delivery van 12",
  "vin": "12345",
  "telemetry_system_id": "8"
}

The full vehicle API reference lives in the Data Model docs. Use those endpoints for create, update, and delete behavior. This guide exists to explain the DIMO-side sync contract and the developer-managed telemetry mapping field, not to replace the vehicle API reference.

Telemetry Results

Once DIMO is enabled, agents can answer questions from latest vehicle signals, recent trip segments, and compact telemetry analysis. Galadri keeps large provider payloads server-side and returns concise answers plus structured supporting data. Snapshot responses can include a parked or current-location map item when DIMO provides location data.

Snapshot reads also keep the Galadri vehicle record fresh when vehicle write access is enabled. When DIMO returns timestamped odometer, location, or DTC values and the VINs do not conflict, Galadri automatically updates odometer_km, last_odometer_update_utc, last_latitude, last_longitude, last_geo_update_utc, dtc_codes, and last_dtc_update_utc for that vehicle. Stale snapshot timestamps and VIN mismatches do not overwrite stored values.

For backend dashboards or scheduled refreshes, call POST /v1/vehicles/:id/refresh with explicit targets to refresh telemetry, DTC code, or valuation fields directly without starting a chat turn.

Trip lookups can return map-ready routes when the user asks to see trips on a map. Multiple returned routes render together on one labeled map instead of stacking separate maps for each trip.

Galadri filters out zero-movement trip segments and converts telemetry into the requested unit system or the end-user's saved unit preferences before it reaches the answer.

DIMO time windows are sent to the provider as UTC. Galadri keeps UTC fields in the result for traceability, and also adds local display fields from the request or end-user timezone so responses can use the user's timezone without manual timestamp conversion.

DIMO's documentation is available at dimo.org/docs.

CommunicationsNext