Toll API for TMS: quote, dispatch and audit routes
Direct answer: a TMS needs toll cost at three moments — quoting the customer, choosing the route at dispatch, and reconciling the operator invoice. All three hit the same toll API; only the timing and precision change.
Integration points
- Pre-billing: quote with waypoints and a standard unit profile via the costs endpoint; store the result flagged as an estimate.
- Dispatch: send each candidate polyline to the toll endpoint and compare true cost, not just kilometres; a toll-free detour often wins.
- Post-auditing: recompute with the actually driven geometry (GPS/tachograph) and diff against the invoice section by section.
Requirements
Per-plate vehicle profile (axles, mass, EURO class, transponder), a heavy-vehicle router producing polylines, and a rounding policy: an estimate is not a committed price until revalidated near travel date.
Figures are illustrative; live queries only.
Frequently asked questions
Does a toll API replace the TMS costing module?
No, it feeds it with toll, fuel and driver costs; margin and other items remain in the TMS.
When should the TMS call the API?
At quoting (waypoints), at dispatch (candidate polylines) and at invoice reconciliation (actually driven geometry).
What should be stored per query?
Amount, breakdown, profile, geometry and timestamp — without those you cannot justify the estimate at audit.