Danube · Price calculator API

Road freight prices, inside your own system.

Send a route, a vehicle and a cargo. Get back a price without VAT, its breakdown and the transit time, in a few seconds. A pricing engine built for European road freight, available as an API you integrate for a fee.

  • Full truck (FTL) and groupage (LTL), with several stops
  • Price, cost breakdown, distance and delivery date in one answer
  • REST and JSON over HTTPS, with your own key
{"distanceKm": 1512,"transit": {"pickup": "2026-11-16","delivery": "2026-11-19","days": 3},"price": {"net": 2150.00,"vat": 0.00,"total": 2150.00,"currency": "EUR"},"breakdown": [ … ]}

Why an API

A quote that takes an hour is a quote the client already got elsewhere.

Today

Prices live in a spreadsheet.

Someone who knows the lanes fills in the table. When they are busy or on leave, quotes wait.

Today

Your website cannot answer.

The visitor fills in a form and waits for an email. Most of them ask three other companies in the meantime.

Today

Building an engine takes years.

Distances, tolls, vehicle types, groupage rules and service levels are a product in themselves, not a side project.

What you send, what you get

One request in, one priced shipment out.

Request

Describe the shipment the way a client would.

The route goes in as addresses or cities, with intermediate stops if there are any. You add the vehicle, the type of transport and what is being carried.

  • Route with two or more stops, domestic or international
  • Vehicle from van to 40-tonne truck; full truck or groupage by pallets, loading metres and weight
  • Cargo type: general, temperature-controlled or ADR; service level Economy, Standard or Express
GET /price/route?stops=Bucharest, RO ~ Munich, DE&vehicle=TRUCK_40T_TILT&transport=FTL&service=STANDARD&cargo=General Cargo&weightKg=22000&pickupDate=2026-11-16 Authorization: Bearer ••••••••••••
Answer

A price you can show, and the numbers behind it.

The answer carries the price without VAT, the VAT and the total, with the breakdown of what makes it up. The distance, the transit time and the pickup and delivery dates come in the same answer.

  • Round trip, customs formalities and loading extras are priced as options
  • Send the requested pickup day and get the delivery date that follows from it
  • Many lanes at once through the bulk endpoint, for tenders and price lists
{"distanceKm": 1512,"transit": {"pickup": "2026-11-16","delivery": "2026-11-19","days": 3},"price": {"net": 2150.00,"vat": 0.00,"total": 2150.00,"currency": "EUR"},"breakdown": [ … ]}
Your rules

Your margin and your brand on top.

The API returns a calculated price for the shipment. What you show the client is your decision: add your margin as a percentage in the call, or apply your own rules after it.

  • A surcharge percentage per call, for seasons, clients or channels
  • Works behind your own form, portal, TMS or ERP; the client never leaves your system
  • Each integration gets its own key and its own limits
Danube screen: Your margin and your brand on top.

Screens are from the platform, with sample data. Some show the Romanian interface; the app also runs in English.

Where it fits

Six places a price in seconds changes the outcome.

The engine is the same; what changes is where you call it from.

  • Instant quote on your website

    The visitor gets a price while still on the page and can order on the spot.

  • Inside your TMS or ERP

    The salesperson sees a reference price on the request, before calling carriers.

  • Tenders and price lists

    Hundreds of lanes priced in one run, exported to the table the client asked for.

  • Marketplaces and portals

    A shipping option with a real price for your own customers, under your brand.

  • Checking carrier offers

    A reference to compare an offer with before you accept it.

  • AI agents and chat

    An agent that answers “how much to Munich?” with a number it did not invent.

How integration works

From first call to production in four steps.

  1. 1

    Tell us your lanes

    Countries, vehicle types and volumes. We confirm coverage before you write any code.

  2. 2

    Get a test key

    Documentation, example calls and a key for trying it against your own routes.

  3. 3

    Integrate

    Your developers call the API, or we build the integration with you as a custom project.

  4. 4

    Go live

    A production key, a monthly fee by volume and usage you can follow.

Questions

What teams ask before integrating.

How much does the API cost?

It is a paid integration: a setup fee and a monthly fee that depends on the number of calls. Tell us your expected volume and you get a fixed offer before any work starts.

Which countries and lanes does it cover?

European road transport, domestic and international. Coverage depends on the lane and the vehicle, so we confirm yours with a test on your real routes before you integrate.

Is the price binding?

The API returns a calculated market price for the shipment you describe. How you use it (as an instant offer, an indication or an internal reference) is your commercial decision.

Do we need Danube TMS to use it?

No. The API works on its own, with any website or system. In Danube TMS the pricing engine is already built in on the Enterprise plan.

Can you build the integration for us?

Yes. If you do not have developers, we build the form, the portal or the connection to your system as a custom project, with a fixed proposal.

Send us ten of your lanes. We send back ten prices.

You compare them with what you quote today and decide whether the API earns its place in your system.