Community

I am using [/fleet/safety-events](https://developers.samsara.com/reference/getsafetyevents) to read safety events. The organization has [configured](https://kb.samsara.com/hc/en-us/articles/360043378832-Driver-Speeding-and-Speed-Limits#UUID-3f6f50a7-03b7-3572-cdcc-49b6598153d5_UUID-f6f7e181-27f6-7f4f-7473-4edc5c3cc852) thresholds for the speeding events and users are receiving email alerts when a speeding event is created. The events are not appearing in the response from the API though. The documentation for the API lists speeding as a valid event type. Is there a way to get the speeding events included in the [/fleet/safety-events](https://developers.samsara.com/reference/getsafetyevents)

I want to check the camera and other sensors on a vehicles whether they are OK or not using REST API, how can I achieve it?

Hello, What are the names of the sensors that capture the weights - cargo weight, load, etc. Can you provide some link to Samsara API documentation?

Is it possible to customize the looks of the page it opens when opening a live tracking link? Change colors? Add logos? Thanks,

Getting up to speed on the API for a client and am not sure where to look to find standard domain data for various objects. For example, calling the ELD-Events endpoint returns a structure with this object embedded: { "time": "2023-10-15T07:00:00.000Z", "eldEventType": 1, "eldEventCode": 1, "eldEventRecordOrigin": 2, "eldEventRecordStatus": 1, "accumulatedVehicleMeters": 0, "totalVehicleMeters": 0, "elapsedEngineHours": 0, "location": { "latitude": 33.44592464, "longitude": -112.25274009, "city": "Tolleson", "state": "AZ", "eldLocation": "0.5 mi SE Tolleson, AZ" }} Is there a place I can look up eldEventType, so I have some context what the value 1 maps to? Thanks!

We are getting this error from time to time while requesting HOS. An item with the same key has already been added. Key: System.Net.Http.Headers.HeaderDescriptor This is the endpoint we are consuming <https://api.samsara.com/beta/fleet/hos/drivers/eld-events> Any ideas on the reason?

We recently switched to Samsara and we're discovering that reporting detail and scheduling is a bit more lacking that we initially thought particularly with report scheduling. There is an inability to select specific days, specific times for start and end ranges and are forced to a full day or full week of reports with no way of adding conditionals to the report data (i.e. if a value is 0 like duration or distance then exclude it from the report). Our previous ELD provider had a PC report that would show all instances of personal conveyance usage the distance, duration of travel, and start and stop locations. On Samsara, we are limited to total duration for the selected date range with no detail at all. Aside from going to each driver's log and viewing the events individually, there is no way to generate a report that shows each instance of PC usage and the details associated with the usage of each. Has anyone else found a better method for reporting and auditing Personal Conveyance usage with drivers within Samsara?

Hello. I would like to embed the Live Sharing code on my WordPress site. If you go to the {Coverage Map} tab and take the link to Live Share there, you need to zoom in to see the drivers' routes. If you go to the {} tab and make a link to {Settings--Links&Sharring--Live Shaing} there, a separate page opens and it is inconvenient to insert it into the site in the <iframe> tag How do I embed a live map on my site?

I am looking for a way to get an alert when the fuel level goes up. Any ideas?

Hello, I have reviewed the API documentation and am trying to get all trailer locations (I am able to get the trailers with gateways connected, but not the ones without). Which APIs can I leverage to achieve this? I read in the documentation that it shows based on "last completed trip where the driver had the trailer selected with a vehicle in the mobile app". Based on the above, what are the necessary APIs I would need to call to get the necessary location of all trailers without gateways connected.