There are two ways that you can receive notifications when a DVIR defect is reported by your mechanics or drivers: You can set up an alert from Samsara (see ) or you can set up a webhook to enable Samsara to send an HTTP request to your application when an event occurs.
If you Set up Alerts through the Samsara Dashboard, the alert will be triggered any time an individual defect is detected on a newly submitted safe or unsafe DVIR. Note that if a DVIR has 5 defects reported on it, 5 alerts and 5 incidents will be triggered, 1ms apart.
 |
 |
Additionally, you can request DVIR details (including defects) using webhooks, which is configurable for all currently available DVIR alerts. For more information on setting up webhooks, refer to the webhook documentation.
The webhook payload includes the following:
Payload Item |
Description |
|---|---|
Vehicle |
Samsara vehicle id and name for the vehicle |
Trailer |
Samsara trailer id and name for the trailer |
Driver |
Samsara driver id and the driver's name |
DVIR id |
The Samsara DVIR id that can be used in our Samsara API endpoints |
Odometer |
Number, the value from the DVIR, not the vehicle cable |
Inspection type (pre-trip or post-trip DVIR, or unset) |
String enum matching the return value from Samsara's API endpoints |
Photos |
Walkaround photos delivered as pre-signed S3 URLs which will be valid for 24hrs |
Safety status Upon reporting (safe or unsafe) |
String enum matching the return value from Samsara's API endpoints |
Defects |
A list of defects created, each with:
|
Note
Please note the following:
Webhook payload only includes newly added defects, not existing ones.
Odometer value in the webhook payload is always in meters.
DVIR defect alerts for the alerts Unsafe DVIR or Safe DVIR with defects (in the case that the DVIR defects alert is not being used) webhook payload includes all newly added defects for that DVIR, not just the one for which the alert generated.
Comments
0 comments
Article is closed for comments.