Webhooks let Digital Permit Book tell your other systems, like a TMS, payroll, or an automation tool, the moment something changes. For example, when a driver is added, a document is updated, or a DVIR is submitted.
Plan: Webhooks are usually part of the Enterprise plan, so you may not see Webhooks in Settings. Contact support to turn them on for your company.
Add a webhook
- Go to Settings > Webhooks.
- Click + Add Webhook.
- Enter a Name so you can recognize it later, for example TMS sync.
- Choose the Type and enter where to send events:
- URL: enter the web address of the system that receives the events.
- Email: enter an email address. The same events are sent there as emails, handy for a person or a shared inbox.
- Under Events, choose one or more events to send (see the list below). If you choose a document event, a Doc Type field appears. Pick the doc types to send, for example only Medical Card and Vehicle Registration. Type to search the list.
- Optional: click + Add Custom Header to send extra headers with every event, such as an API key or token your system expects.
- Click Save.
The webhook appears in the list with its name, URL or email, events, and doc types. Use the Action column to edit or remove it.
Events you can send
| Area | Events |
|---|---|
| Drivers | Driver Created, Driver Updated, Driver Deleted |
| Vehicles | Vehicle Created, Vehicle Updated, Vehicle Deleted |
| Trailers | Trailer Created, Trailer Updated, Trailer Deleted |
| Documents | Document Created, Document Updated, Document Deleted |
| DVIR | DVIR Submitted |
| Forms | Form Submitted |
Tips
- Use Custom Headers to protect your URL: add a secret header, and have your system reject requests without it.
- Create separate webhooks if different systems or people need different events.
- Use Email webhooks to alert someone without any setup on their side, for example the safety manager when a DVIR is submitted.
- Want to read or change data instead of receiving events? Use the API. To connect an AI assistant, see MCP.