Reference / Providers
Provider coverage
One API. Different source capabilities. Compare what our adapters implement before choosing the data your app needs.
This compares this service's adapters, rather than every feature sold by a provider. Implementation does not imply activation or live acceptance for your connection. Device hardware, token permissions, account scope, current purpose and independent read grants still apply.
- Implemented
- The adapter implements this dataset; separate activation and permissions apply.
- Conditional
- The field is mapped, but may be unavailable for an account or asset.
- Not mapped
- This adapter does not map the field. The provider may offer it elsewhere.
Datasets
| Dataset | Samsara | Motive | Geotab | Access and coverage |
|---|---|---|---|---|
| Core asset roster | Implemented | Implemented | Implemented | The default list uses core source IDs. |
| Optional core vehicle metadata | Implemented | Implemented | Implemented | Separate opt-in; a core source-ID projection, distinct from normalized profiles. |
| Normalized vehicle profiles | Implemented | Implemented | Implemented | Separate profile purpose and read grant; optional fields differ below. |
| Completed historical trips | Implemented | Implemented | Implemented | Approved vehicles and trip-start window; distance/duration source bases differ. |
| Account group directory | Implemented | Implemented | Implemented | Separate directory purpose/read grant before credential-visible discovery; not proof of every account group. |
| Explicitly selected groups | Implemented | Implemented | Implemented | Approved source-group IDs and verified account scope; resolves approved parents only. |
| Vehicle group memberships | Implemented | Implemented | Implemented | Matching profile/membership authority; directory expansion needs its own grant. |
| Driver directory | Implemented | Implemented | Implemented | Separate driver/PII authority and read grant. Driver data is excluded from the current vehicle-only pilot. |
Use the same linked endpoints for every provider. Telemetry history reads observations collected by this service; complete upstream telemetry backfill is not implemented. Utilization and usage summaries depend on valid collected counters, source continuity and coverage, rather than a provider's native utilization report. Engine runtime includes idle/PTO and does not prove productive work.
Readings and diagnostics
Extended readings require explicit opt-in and source validation. Missing, stale, invalid and unsupported readings remain explicit; they never become invented zeros. See units and availability.
| Reading | Samsara | Motive | Geotab | Normalized unit |
|---|---|---|---|---|
| Location | Conditional | Conditional | Conditional | degrees |
| Odometer | Conditional | Conditional | Conditional | meters |
| Lifetime engine runtime | Conditional | Conditional | Conditional | seconds |
| Lifetime idle duration | Conditional | Not mapped | Not mapped | seconds |
| Speed | Conditional | Conditional | Conditional | meters per second |
| Heading | Conditional | Conditional | Not mapped | degrees |
| Fuel level | Conditional | Conditional | Not mapped | percent |
| Vehicle battery voltage | Conditional | Conditional | Not mapped | volts |
| Engine state | Conditional | Not mapped | Not mapped | enum |
| Fault codes and events | Conditional | Conditional | Conditional | diagnostic records |
Vehicle profile fields
These are provider-sourced profile fields. VIN decoding, images and specifications belong to separate enrichment, not an implied provider capability. Available values are returned; missing or invalid optional values are omitted.
| Field | Samsara | Motive | Geotab |
|---|---|---|---|
| Vehicle name | Conditional | Conditional | Conditional |
| VIN | Conditional | Conditional | Conditional |
| Make | Conditional | Conditional | Not mapped |
| Model | Conditional | Conditional | Not mapped |
| Model year | Conditional | Conditional | Not mapped |
| License plate | Conditional | Conditional | Conditional |
| License plate region | Not mapped | Conditional | Conditional |
| Device serial number | Conditional | Not mapped | Conditional |
| Normalized active/inactive status | Conditional | Conditional | Conditional |
| Source status | Not mapped | Conditional | Not mapped |
| Normalized fuel type | Not mapped | Conditional | Not mapped |
| Source fuel type | Not mapped | Conditional | Not mapped |
| Source creation time | Conditional | Conditional | Not mapped |
| Source update time | Conditional | Conditional | Not mapped |
| Active from | Not mapped | Not mapped | Conditional |
| Active until | Not mapped | Not mapped | Conditional |
Collection and connection setup
| Behavior | Samsara | Motive | Geotab |
|---|---|---|---|
| Core collection | Native feed | Polling | Native feed |
| Credential implementations | API token; OAuth | OAuth; Partner/master OAuth | Database API user |
| Fault evidence model | Complete active snapshot | Explicit source records | Explicit source records |
| Adapter version | 1.5.0 | 1.4.0 | 1.2.0 |
Credential implementations do not mean a complete self-service connection experience is available. Gated customer invitations support Samsara API tokens, Geotab service accounts and separately registered Samsara/Motive OAuth. They keep collection paused after enrollment and still need isolated deployment and live pilot acceptance. See the customer onboarding guide. Stored profiles, trips, directories and memberships use separately approved collection plans, not the core feed's cadence. Cadence is configurable and is not an exact freshness guarantee.
Shared service features
Public sync operations request separately authorized work across these adapters; an application sync token does not replace a dataset read credential. Fault webhooks deliver this service's normalized fault events, subject to each provider's evidence model above.
VIN enrichment supplies cached identity, images, specifications and build sections through Auto.dev independently of the telematics provider. It needs a valid VIN, separate enrichment activation and upstream product entitlement; it is not currently activated for the GCI testing fleet. Raw supplier payloads and deletion/tombstone access remain unsupported across the stored profile, trip and directory contracts.
Provider notes and live validation
Validation below is a dated testing observation, not an account-wide availability or production guarantee. All providers require their own fleet acceptance before activation.
Samsara
Testing status: Core, vehicle profiles and a bounded trip pilot have live testing evidence as of October 10, 2026. Other datasets still need their own activation and acceptance.
- The adapter targets the US API cloud. Vehicle/device and endpoint permissions determine what is returned.
- Odometer prefers engine readings, then calibrated GPS readings. Complete active-fault snapshots and explicit fault-record providers have different clearance evidence.
- Trips use GPS distance and elapsed motion interval duration. Optional trip coordinates are preserved only when valid.
- Profile status is based on gateway association, including the exact observed unpaired placeholder; it does not indicate engine activity or productive utilization.
Motive
Testing status: Implementation has synthetic validation. Live acceptance of an authorized fleet in this standalone service is still pending.
- Explicit company ownership is required. Partner/master access needs provider-approved provisioning; polling can miss changes between captures.
- Odometer source units are explicitly selected as miles or kilometers, then normalized to meters. Engine runtime arrives in hours and is normalized to seconds.
- Trip distance uses explicit kilometer counter differences; generic distance is not guessed from display settings. Duration is provider-reported driving duration, not elapsed time.
- Completed driving, personal-conveyance and yard-move periods need fleet acceptance against the intended trip definition. Fault absence never proves clearance.
Geotab
Testing status: Implementation has synthetic validation. Live acceptance of an authorized database/API-user account is still pending.
- Gated customer invitations accept a dedicated service account for an operator-prepared database/server and explicit approved device IDs, currently at most 100 per connection. Credentials are encrypted and collection remains paused; OAuth is not implemented for Geotab. Live onboarding acceptance remains pending.
- Odometer requires the configured meter diagnostic metadata; engine runtime requires second-unit diagnostic metadata. Latest telemetry uses bounded source lookback, not a complete historical telemetry import.
- Trips use reported kilometer distance and driving-duration TimeSpan. End location comes from the trip stop point; start location needs an actual LogRecord at the exact trip start, without interpolation.
- Faults use Geotab diagnostic numeric codes. A lookback feed is not an inventory of all older active faults; absence or dismissal does not prove physical clearance.
Check your connection
Connection capabilities reports its provider adapter and field support; it does not grant access or prove a reading exists. Combine it with connection health, actual dataset status, capture/publication times and per-reading availability. Independent dataset grants and the configured selection determine which resources you can read.
Telemetry coverage and adapter versions are derived from the provider registry; profile field coverage is derived from the normalizer. Dataset declarations and live validation notes are reviewed separately. Checked October 10, 2026.