Samsara (BYOK) — connector documentation
- MCP endpoint:
https://byok-samsara.connectorbay.com/mcp - REST API:
POST https://byok-samsara.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec athttps://byok-samsara.connectorbay.com/openapi.json - Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
- Authentication: your own Samsara Samsara API token (US cloud; give it read scopes only), sent in the
X-Upstream-Keyheader of every request (never stored, logged or cached) - Health:
https://byok-samsara.connectorbay.com/health· Tool schemas:https://byok-samsara.connectorbay.com/tools.json - Publisher: Unify Dynamics LLC · connectorbay.com/byok-samsara · agent@connectorbay.com
What Samsara (BYOK) is for
Samsara (BYOK) lets an AI assistant read your own Samsara data through the Samsara API with a key you supply (Samsara API token (US cloud; give it read scopes only)). Read-only: 12 tools (get_organization, list_vehicles, get_vehicle, get_vehicle_locations, get_vehicle_stats, list_trailers, list_equipment, list_trips, list_work_orders, list_upcoming_preventive_maintenance, get_vehicle_fuel_energy_report, list_tags). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.samsara.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Samsara. Samsara and its logos are trademarks of their owners and are used only to say which service the connector works with.
Ask your assistant things like:
- "Which Samsara organization is this token for?"
- "Which trucks are in my Samsara fleet?"
- "Show me the details of Samsara vehicle 281474976710655"
- "Where are my Samsara trucks right now?"
- "What is the engine state and fuel level of my Samsara trucks?"
- "Which trailers does my fleet have?"
What it does
get_organization: Show the Samsara organization the token belongs to: id, name and carrier settings (carrier name, USDOT number, main office address). Needs the Read Org Information scope.list_vehicles: List the fleet's vehicles with name, VIN, make, model, year, plate, gateway serial, vehicle type, tags and external ids. Up to 512 per page; page with the cursor. Needs the Read Vehicles scope.get_vehicle: Get one vehicle by its Samsara id (or an external id such as 'maintenanceId:250020'): name, VIN, make, model, year, plate, gateway, tags and gross weight.get_vehicle_locations: Get the last known position of each vehicle (or of chosen vehicles): latitude, longitude, heading, speed, time and a reverse-geocoded place name. Needs the Read Vehicle Statistics scope.get_vehicle_stats: Get the latest engine and fuel stats of vehicles: engine state, fuel percent, odometer, battery voltage, RPM, coolant temperature, GPS and fault codes. You must name 1 to 3 stat types.list_trailers: List trailers with name, plate, trailer serial number, installed gateway, tags and notes. Up to 512 per page.list_equipment: List non-vehicle equipment (generators, excavators and similar) with name, asset serial, installed gateway, tags and notes. Up to 512 per page.list_trips: List trips of up to 50 assets (vehicles or trailers) in a time window: start and end time, distance in meters, completion status and trip purpose. Locations are not returned. Needs the Read Trips scope.list_work_orders: List maintenance work orders with status, priority, category, description, linked asset, due and completion dates, odometer and engine hours. Needs the Read Work Orders scope.list_upcoming_preventive_maintenance: List upcoming and overdue preventive maintenance per asset: status, next due time and odometer, days left and the linked schedule. Up to 200 per page.get_vehicle_fuel_energy_report: Get a fuel and energy report per vehicle for a date range: distance, fuel used, efficiency, idle and run time, estimated cost and CO2. Needs the Read Fuel and Energy scope.list_tags: List the organization's tags (groups) with parent tag and the vehicles, trailers and addresses assigned. Up to 512 per page.
BYOK key
You bring your own Samsara Samsara API token (US cloud; give it read scopes only) (https://developers.samsara.com/docs/authentication). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.samsara.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.
Data sources
- https://developers.samsara.com/reference/overview (the API this connector calls, with a BYOK key)
Live from the Samsara API (api.samsara.com) with a BYOK key; documentation: https://developers.samsara.com/reference/overview. Endpoints checked against that documentation on 2026-10-16.
What it is not
Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Samsara. Samsara and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Samsara account.
Built for: Worldwide. Languages: English.