DSV integration

What is DSV?

DSV is a global transport and logistics company offering road, air, sea and rail freight. Software connects through DSV’s generic APIs on developer.dsv.com: Transportial uses the Booking API to book, the Label Printing API for package labels, the Tracking API for milestones and the Document Download API for proofs of delivery.

What syncs between DSV and Transportial

• → To DSV

  Consignments → DSV bookings

  When a trip forwarded under a capacity contract that uses the DSV integration is confirmed, each consignment is booked with DSV on your MDM account: road (groupage and part loads per package, or loads by loading metres), air, sea (LCL or FCL with the container types) or rail. The product follows the trip’s mode unless you choose one; goods bring weight, dimensions, volume, loading metres, package type and ADR details, the order its Incoterm, and the loading and unloading windows are sent as local times.

• ← Into Transportial

  Booking id first, shipment number and label later

  DSV confirms a booking with a booking id. As soon as DSV has processed it, the DSV shipment number, air waybill or bill of lading and the package label (PDF or ZPL) are added to the consignment.

• ← Into Transportial

  Milestones and stop completion

  Booking, pickup, departure and arrival at ports and airports, export and import customs, out for delivery, delivery and problems such as a customs hold come back on the consignment at the local time they happened. Pickup completes the loading stop and delivery the unloading stop; the proof of delivery is stored when DSV provides it.

• ← Into Transportial

  DSV numbers booked elsewhere

  Add a DSV booking id or shipment number — also of a DSV XPress shipment — to a consignment to follow a shipment booked in myDSV or by your supplier.

How to connect DSV

1. Parcel and freight carriers are switched on per platform: ask us to enable them for your Transportial account.

2. Sign up on the DSV developer portal (developer.dsv.com) and subscribe to the Access Token, Booking, Tracking and Label Printing APIs (and Document Download for proofs of delivery). Note the subscription keys and your MDM account number, and create a myDSV user for the API.

3. Add the DSV integration in Transportial with the myDSV username and password, the MDM number as account number, the subscription key — one for all DSV APIs or one per API — the default product or “mode of the trip”, the default Incoterm and the label format. You can start in DSV’s demo environment.

4. Set a capacity contract’s communication method to this integration. Trips forwarded under that contract are booked at DSV as soon as you confirm them.

Sync frequency and limits

• Bookings are made when the trip is confirmed; consignments added later are booked on the next trip update, never twice with the same integration.
• Before a booking leaves, Transportial checks what DSV requires for the mode — postcodes, field lengths, dimensions or volume, containers for FCL, UN number, class and packing group for dangerous goods on the road — and names what is missing.
• Open bookings are checked every 60 minutes by default — configurable per integration — until DSV reports them delivered or cancelled; a booking DSV does not know yet is simply checked again.
• Air bookings show the chargeable weight (actual or volumetric at 6,000 cm³ per kg, whichever is higher) in the integration log.
• DSV’s booking API cannot cancel: cancel a booking in myDSV or with your DSV office.

Typical use case

A forwarder in Rotterdam ships machine parts to customers in Germany by road and spare parts to the US by air. Road consignments are planned on a Trip under a DSV contract, air consignments on a Trip with mode air; confirming the Trips books them with DSV. The labels appear on the consignments once DSV has processed the bookings, customer service sees departure, arrival and customs clearance, and the delivery stop closes when DSV reports the delivery.

Frequently asked questions