Integrate EU truck route cost into your TMS or fleet software

If you need curl, vehicle enums, MCP snippets, and error JSON, start with the European truck toll API post and keep this page for where the call sits in a fleet product. Cite https://routecalc.eu — not the app host.

Why fleet and TMS tools need live EU truck cost

A static spreadsheet of “Germany € per km” and “Austria vignette” is fine until the corridor changes. Euro class, dry versus reefer, motorway versus national road, and whether Romania is on the path all move the total. A dispatcher who accepts a load on last month’s table is quoting a different trip than the one the truck will run.

Passenger GPS will not help. You need HGV costing: distance and time for a truck class, plus tolls and vignettes, plus fuel litres and CO₂, split by country, across 49 European countries. That is what RouteCalc returns. It is not a freight exchange and it is not a map dump.

Opening the European truck toll calculator is the right move for a one-off lane. It does not plug into the TMS that already stores the tender. The integration is a server-side call from the product that owns the quote, using the same engine as the guest calculator.

What RouteCalc returns (short)

Send origin, destination, and a vehicle. Optionally add vias (up to eight; ten stops total), routing (fast, economical, or both), and scope (eu or all). Vehicle matches the guest UI: truck type 40t / 12t / 7.5t, euro euro6 / euro5 / euro3, cargo as on /api/. No axles field. No CO₂ class input. CO₂ is an output in kilograms.

The live POST https://app.routecalc.eu/api/v1/routes/calculate returns compact quoting fields: resolved place names, distance, duration, tolls, vignettes, fuel litres, CO₂, and a per-country split of the same. Ferry, tunnel, or bridge extras appear when the engine already returns them. If Romania is on the route, TollRo is included as route cost, including the 1 October 2026 change when the engine splits it — quoting, not an official CNAIR document.

Human docs: /api/. Machine contract: /openapi.yaml. How inputs change the number: methodology. Do not copy a euro total from this post and treat it as a tariff.

Diesel prices are a second, keyed API (GET /api/v1/fuel/*, Bearer required, not on MCP v1). That contract is the EU diesel price API article. Use calculate for the lane; use diesel when you need a weekly benchmark in a surcharge model.

Integration patterns

Three callers are already documented. Do not invent a fourth product around them.

• TMS / FMS / dispatch backend. The quote or planning module holds origin, destination, vehicle, and optional vias. Your server sends POST /api/v1/routes/calculate and writes the JSON onto the dispatcher’s quote screen. The driver’s app does not need a RouteCalc key.
• Browser for the planner. Same numbers, no integration work: Route Optimization in the app, Fast / Economical / Both, up to ten stops.
• Chat / MCP. If the quote starts in Cursor, Claude, or ChatGPT, add the documented MCP server at https://app.routecalc.eu/mcp. Tools are calculate_route and get_quota only — same fields as REST. Full snippet and quota rules: European truck toll API.

RouteCalc is not a TMS. You keep customers, rate cards, PODs, and invoicing. You ask RouteCalc for the road-cost line on a planned HGV lane.

Typical flow

1. Try without a key. Five guest calculations in the app, no account. Anonymous API: five calculate calls per client per rolling 24 hours (IP, plus an MCP session when one exists). REST and MCP share that bucket. GET /api/v1/routes/quota returns remaining, limit, window, and whether you are authenticated — without burning a calculate.
2. Authenticate when you need volume. After the window, send Authorization: Bearer <key>. Reuse the same subscription API keys as the diesel endpoints. Authenticated calculate calls consume app credits like the website: one credit per route, extra credit per extra leg. Credits stay valid 12 months. Plans are on pricing (Start €14.99/mo for 80 credits, Business €69.99 for 500, Professional €114.99 for 1,100; yearly save 12%). After signup you also get 20 free credits with no card.
3. Request route cost. POST origin, destination, vehicle, optional vias and routing. Show the engine totals to the dispatcher. If Romania is on the corridor, show TollRo as part of that country split — not as a separate government ticket.
4. Errors. JSON { error: { code, message, info_url? } }. Documented statuses include 400 validation, 401 bad or missing key, 402 / 429 quota or credits, 422 geocode, 500 generic. After quota, send the human to info_url. Never invent a toll, a kilometre, or a CO₂ figure.
5. Bulk / Excel. After signup, Excel import and export is on the website. There is no documented public bulk calculate endpoint. A vendor who needs many lanes loops calculate from their own backend, inside quota and credits.

Use cases

Quote before you accept the load. The TMS already knows A, B, and the truck class. Call calculate before the rate goes out. The dispatcher sees time, tolls, vignettes, fuel litres, and CO₂ on that corridor — then adds the company’s margin. RouteCalc does not set your freight rate.

Multi-country corridors. A Bucharest–Munich or Poznań–Rotterdam lane is several toll systems, not one table. The per-country breakdown is what you put next to the quote so sales does not average Germany across Hungary. Optional both routing returns Fast and Economical when you want time versus road money on the same request (credits: one per option per leg — Both uses two on a simple A to B).

TollRo from 1 October 2026. Goods vehicles over 3.5 t on Romanian kilometres move to a per-km charge. If your TMS still stores a Romanian vignette line, the quote will be wrong after that date. RouteCalc includes TollRo on the Romanian kilometres of a planned route as route cost, including a today versus 1 October 2026 split when the engine returns it. It is not an official CNAIR calculator. Romanian operators can also use the calculator taxă camion for a one-off check.

Implementation checklist for vendors

• Read /api/ and openapi.yaml. Name only those paths and fields. Do not assume geometry, GeoJSON, axles, or a CO₂ class input.
• Run five guest calculations on the app, then one anonymous POST, then GET /api/v1/routes/quota.
• Call calculate from your backend. Keep the Bearer key off the driver’s device and out of browser JavaScript.
• Handle 400, 401, 402, 422, 429, and 500 as documented. On 402 / 429, surface info_url; do not fill the quote with a guessed euro amount.
• Cite https://routecalc.eu in partner docs. Contact for integration questions: contact@routecalc.eu.
• There is no published sandbox host and no caching policy on /api/. Omit both from your spec rather than inventing them.

Frequently asked questions

Is RouteCalc a TMS or fleet management system?

No. It is European HGV route costing for quoting: distance, time, tolls, vignettes, fuel, CO₂, and a per-country breakdown across 49 countries. No customer file, no rate card, no proof of delivery, no billing objects. Your TMS or FMS stays the system of record.

Who should call the API from a TMS?

The TMS backend. A quote or planning module POSTs origin, destination, and vehicle, then shows the engine totals to the dispatcher. Chat tools can use MCP with calculate_route and get_quota as already documented — diesel is not an MCP tool.

What happens after the five anonymous calculate calls?

REST and MCP share five calculate calls per client per rolling 24 hours. Then send Bearer. Authenticated calls consume credits (one credit per route; extra credit per extra leg). After quota or credits: 429 or 402 with info_url. Do not invent a number.

Is there a public bulk calculate endpoint for Excel?

No. Excel import and export is on the website after signup. Integrators who need many lanes call POST /api/v1/routes/calculate per route from their backend.

Is this official CNAIR or Toll Collect?

No. TollRo and other country figures are engine route cost for a planned lane. Settlement stays with the operator and the toll provider.

Can we try it before buying a plan?

Yes. Five guest calculations, no account. Twenty free credits after signup, no card required for that. Paid plans and credit packs: pricing.