Understand provider webhook event processing
This guide explains that how invoice, job and location payloads are routed. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
Where to goPublic API route → /clm/webhook/{provider_slug}
What you’ll accomplish
Know how invoice, job and location payloads are routed. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects.
Follow these steps
- Go to Public API route → /clm/webhook/{provider_slug}.
- Check the source record and choose the supported action.
- Save or submit once, then reopen the record and verify the result.
Fields and options to review
invoice eventsImported into provider invoice records.
job eventsNormalised/imported or applied to linked jobs.
location eventsRetained/processed for operational snapshot where supported.
authenticationSignature-valid state retained with the webhook log.
Rules the system enforces
- Payload, hash, signature result and HTTP status are logged.
- External completion does not bypass local POD evidence.
How to confirm it worked
- The source record, status/history and any downstream notification, provider, POD or finance record should agree after the action.
Security, audit and operational checks
- Use the exact record and least-privilege role before changing any state.
- Verify the saved record after every action; a browser message alone is not evidence that every downstream step completed.
- Use protected document and image routes rather than exposing server filesystem paths.
- Keep customer, driver, provider, financial and credential data within the authorised workflow.
- For provider, finance, employment, transport and compliance decisions, follow the organisation’s authorised professional process.
Do not bypass the code flowDo not force database values, invent a status, mark a job completed without signed POD evidence, or expose encrypted credentials to make a screen appear successful.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.