Samsara sells vehicle gateways and AI dash cams and runs the cloud behind them. Its REST API at api.samsara.com, with regional hosts for the EU and Canada, exposes vehicles, drivers, hours of service, safety events, routes, and documents. The dashboard can push Alert Webhooks and Event Subscriptions to a URL you own.
Through Fibric, an operator polls the vehicle stats feed, reads HOS clocks and safety events, and proposes a route, a driver record change, or a webhook subscription. You approve each change. It is applied once and leaves a receipt: what changed, why, and how to undo it.
This is a reference listing. It documents what Fibric would read from Samsara and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.
Inputs
Vehicles through GET /fleet/vehicles: name, VIN, make, model, year, license plate, gateway serial, static assigned driver, tags, and external IDs
Vehicle stats through the stats feed: gps, engineStates, fuelPercents, obdOdometerMeters, faultCodes, and other types, cursored with endCursor and after
Hours of service through Get HOS Clocks, Get HOS Logs, and driver HOS daily logs, including remaining drive, shift, and cycle time
Safety events through GET /fleet/safety-events with behavior labels, maximum acceleration in g, coaching state, and video download URLs
Drivers through GET /fleet/drivers, filtered by activation status and by createdAfterTime or updatedAfterTime
Event Subscriptions such as AlertIncident, DvirSubmitted, GeofenceEntry, GeofenceExit, RouteStopArrival, RouteStopDeparture, SevereSpeedingStarted, and VehicleCreated
Proposed actions
Target capability: propose a route through POST /fleet/routes with a name, at least two stops, and a driverId or vehicleId
Target capability: propose a driver record update through PATCH /fleet/drivers/{id}, including deactivation by driverActivationStatus
Target capability: propose a webhook subscription through POST /webhooks with the eventTypes an operator needs
Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.
What you can build
Keep drivers inside their hours
HOS Clocks show remaining drive, shift, and cycle time per driver. When a planned assignment would exceed them, the operator proposes a swap and records why.
The stats feed carries faultCodes alongside engine state and odometer. The operator matches a new code to the vehicle and proposes a service booking for approval.
Safety events arrive with behavior labels, g-force, and video links. The operator drafts a coaching note per event and leaves it in needsReview until a manager signs off.
RouteStopArrival and RouteStopDeparture events show where a route stands against plan. The operator flags a missed sequence and proposes a revised route through POST /fleet/routes.
A Samsara organization and an admin who can create API tokens in the dashboard
Read scopes on the token for each endpoint, for example Read Vehicles and Read Vehicle Statistics, and write scopes selected explicitly
The regional host for your organization: api.samsara.com, api.eu.samsara.com, or api.ca.samsara.com
For webhooks, an HTTPS endpoint of yours that returns 2XX and checks the X-Samsara-Signature header
Authentication
An API token created under Settings > API Tokens in the Samsara dashboard, sent as a Bearer header, with tag access and granular scopes set per token; Marketplace apps use OAuth 2.0 at api.samsara.com/oauth2/authorize.
Limits
Each API token may make 150 requests per second and each organization 200; endpoint levels are lower, and 429 responses carry Retry-After
The stats feed returns updates since the last cursor; when hasNextPage is false, wait at least 5 seconds before the next call
GET /fleet/safety-events is marked legacy in the reference, with a newer alternative recommended
Webhook deliveries are retried a total of 5 times with exponential backoff; a webhook that never returns 2xx may be disabled
Access and pricing
Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.
Both. Alert Webhooks and Event Subscriptions are set under Settings > Webhooks or created through POST /webhooks with an eventTypes array. Samsara signs each delivery with X-Samsara-Signature, an HMAC SHA-256 over v1:<timestamp>:<body>. For high-frequency data such as GPS and engine stats, poll the stats feed with its cursor.
What does an API token need?
A name, tag access that restricts it to objects with selected tags, and granular scopes per endpoint group. New tokens get default read scopes for common resources; write scopes must be selected. The token is shown once at creation and cannot be viewed again.
Are there regional hosts?
Yes. The reference lists https://api.samsara.com, https://api.eu.samsara.com, and https://api.ca.samsara.com. Use the host that matches where your organization is provisioned.
Ask about Samsara
Ask about the capabilities and requirements in this listing.
This connector listing is developed, published, and supported by Fibric. It describes integration with Samsara through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy