Samsara and Motive (ELD) integration
Connect your fleet's Samsara or Motive account with OAuth 2.0. Demurly only reads from it. Today it checks the connection; next, your trucks' GPS opens and closes waits at terminals and customer sites by itself.
Pro plan, admins only
Available today
- Connect Motive or Samsara by signing in there and allowing Demurly to read your fleet
- A read check that shows what Demurly can see (for example "Found 12 vehicles.")
- Check again at any time, and Disconnect, which also withdraws Demurly's access at the provider
Not yet
- Waits opened and closed by the truck's GPS at terminals and customer sites
- Matching ELD trips to records you already have
- Writing anything to Samsara or Motive: Demurly never changes your fleet data
Until then, send waits the way you do now. Be a pilot carrier.
Connect
- In Demurly, open Settings > Connected systems > Trucks (ELD).
- Click Connect on the Motive or Samsara card.
- Sign in to Motive or Samsara as a fleet admin and allow the read-only permissions below.
- You come back to the Trucks tab, which shows Connected and what the first check found.
If you cancel on the Motive or Samsara page, nothing is connected and the tab says so. If a card says the provider isn't set up on this Demurly server yet, contact us.
Permissions Demurly asks for
Motive
Every permission is read-only (12 in all). Motive lists them on its consent screen before you allow them.
| Scope | What it reads |
|---|---|
| companies.read | Your company's name and details |
| users.read | Users and drivers |
| vehicles.read | Vehicles |
| locations.vehicle_locations_list | Every vehicle's latest location |
| locations.vehicle_locations_single | One vehicle's location history |
| locations.driver_locations | Drivers' locations |
| geofences.read | Your geofences |
| geofence_events.read | Geofence entries and exits |
| ifta_reports.trips | IFTA trip reports |
| hos_logs.read | Hours of service logs |
| hos_logs.logs | Hours of service log entries |
| hos_logs.hours_of_service | Drivers' hours of service |
Samsara
Samsara sets the permissions on Demurly's app rather than in the sign-in request, and shows them when you allow access. They are read-only; today Demurly reads your vehicle list to check the connection.
Redirect URIs
After you allow access, Motive or Samsara sends you back to one of these addresses, and only these. If your security team keeps an allow list, these are the ones to add.
| Provider | Where | Redirect URI |
|---|---|---|
| Motive | Demurly | https://www.demurly.com/api/integrations/motive/callback |
| Motive | Demurly test environment | https://staging.demurly.com/api/integrations/motive/callback |
| Samsara | Demurly | https://www.demurly.com/api/integrations/samsara/callback |
| Samsara | Demurly test environment | https://staging.demurly.com/api/integrations/samsara/callback |
Check again and disconnect
- Check again reads the account once more. If it fails, connect again: access may have been removed on the provider's side.
- Disconnect deletes Demurly's stored access and asks the provider to withdraw it, so connecting again asks for your permission again. Your records aren't changed.
- Tokens are stored encrypted and are never shown in Demurly.
Help Center: Connect your trucks' ELD.