Polling track-and-trace over DSV-moved shipments. Lookups by DSV bookingId, DSV TMS shipment id or customer reference; responses carry house and master bill of lading numbers, air waybill numbers, container numbers, UN/LOCODE locations, SSCC package numbers, carrier SCAC codes and a DSV-proprietary event vocabulary.
DSV Tracking API (Air, Sea, Road EU, Rail) is one of 29 APIs that DSV publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Track and Trace, Shipments, and Event. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, API documentation, and authentication docs.
This API exposes
4 operations
across 4 paths,
organized into 2 resource areas,
and defines 45 schemas.
It is described by OpenAPI 3.0.1, at version v2.
Requests are made against a single base URL, https://api.dsv.com/my-demo/tracking/v2.
4 operations4 paths45 schemas3 GET1 POST
Metadata
The identity and technical contract details declared by the specification.
Specification
OpenAPI 3.0.1
API Version
v2
Base URL
https://api.dsv.com/my-demo/tracking/v2
Authentication
API Key, API Key
Resource Areas
2
Authentication & Security 2
DSV Tracking API (Air, Sea, Road EU, Rail) declares
2 security schemes
for authenticating requests.
An API key is passed in the header as DSV-Subscription-Key (apiKeyHeader).
An API key is passed in the query as DSV-Subscription-Key (apiKeyQuery).
By default, every request must be authenticated.
Paths & Operations 4
Across 4 paths, the API surfaces 4 operations — 3 GET, 1 POST. They span 2 resource areas: Shipment list, Shipment details. Each is listed below with its method, path, parameters, and response codes.
Shipment list 1
POST
/shipments/list
Shipment list
listPost1 parambody→ 200
Shipment details 3
GET
/shipments/bookingId/{bookingId}
Shipment details by DSV Booking ID
getShipmentByBookingId2 params→ 200400404
GET
/shipments/tmsId/{tmsId}
Shipment details by DSV Shipment ID
getShipmentByTmsId2 params→ 200400404
GET
/shipments/reference/{*reference}
Shipment details by Customer reference
getShipmentByReference2 params→ 200400
Schemas 45
The contract defines 45 schemas that model the data the API accepts and returns. The most detailed are PackageDTO (33 properties), ShipmentSummaryAPI (27 properties), ShipmentDetailsAPI (26 properties), DangerousGoodsDTO (21 properties). Each schema is shown below with its type and property counts.
DevelopmentDTO
object
Development
2 properties
ErrorDTO
object
Error
4 properties2 required
FieldDTO
object
Field
3 properties
DateFilter
object
Only include Bookings/Shipments where the Delivery date (actual/estimated/requested) matches selected filter
3 properties1 required
DatesFilter
object
Allows for searching Bookings/Shipments where the Booking/Pickup/Delivery date matches custom date range
3 properties
ListParamsDTO
object
This structure contains the filter parameters to limit the response
9 properties
Address
object
All fields related to the address of the business partner.
13 properties
ContactPerson
object
All fields related to Contact Person e.g. Name, Phone, email
3 properties1 required
Delivery
object
Name and address of the party where shipment is delivered
2 properties
GoodsSummaryDto
object
4 properties
Pickup
object
Name and address of the party shipment is picked up.
2 properties
Receiver
object
Name and address of the party receiving the shipment (consignee).
2 properties
Sender
object
Name and address of the party sending the goods (shipper). If address is not already available, it will be created from supplied address data.
2 properties
ShipmentSummaryAPI
object
27 properties1 required
ShipmentSummaryParties
object
All parties of the shipment summary are mentioned in this structure. See party definition for details.
4 properties
TypeValueDTO
object
References that can be used to identify linked information. It is allowed to send several references of the same reference type.
2 properties
BaseParty
object
The forwarder responsible for the transport
2 properties
Battery
object
Battery information
2 properties
BookingParty
object
Name and address of the party that created the booking.
2 properties
Carrier
object
Name and address of the carrier
2 properties
Container
object
Specify the required containers of a certain type. Additional attributes can be submitted for certain container types. More details on container types can be f…
4 properties
ContainerSummaryDTO
object
Summary of container information
4 properties
CustomsApiDto
object
Customs data
5 properties1 required
DangerousGoodsDTO
object
This section contains the details of the dangerous goods in the booking/shipment.
21 properties
DateTimeRange
object
Date with time range. Used e.g., for Pickup Date and Time.
3 properties1 required
DateTimeSection
object
Date and time specification for the shipment
2 properties
DocumentDto
object
This section contains all document details of Profs of delivery.
7 properties6 required
EventApiDto
object
Track and trace events
16 properties1 required
FreightPayer
object
Name and address of the party that receives the freight invoice.
2 properties
GoodsApiDto
object
This section contains the details of the goods from the booking/shipment.
13 properties
IncotermsDTO
object
Incoterms® describe the rights and obligations applicable between the buyer and seller of the goods being transported. They set out when transfer of liability…
2 properties
IssueAPI
object
This section contains Issues details from the booking/shipment.
11 properties
LocalTime
object
The requested pickup/delivery time (end of time window) using the 24 hours format hh:mm:ss
4 properties
LocationApiDto
object
Event location details
3 properties
Notify
object
Name and address of the party who will be notified
2 properties
PackageDTO
object
All package details in the booking/shipment.
33 properties1 required
PackageIdentifierDTO
object
This section contains Package identifier details from the booking/shipment.
2 properties
Parties
object
Contains all parties involved in the booking. See the party definition section for more details.
9 properties3 required
Party
object
Reserved for future use.
3 properties1 required
ProductApiDto
object
The product section carries the information about the main transport mode and some directly associated parameters, if any.
7 properties1 required
Service
object
This section contains additional Service details from the booking/shipment.
4 properties2 required
ServiceLevelDTO
object
This section contains details on the requested service level from the "Air", "Sea" or "Rail" booking/shipment
2 properties
ShipmentDetailsAPI
object
Shipment details
26 properties5 required
TransportApiDto
object
This section carries the information about the main transport and some directly associated parameters applicable for "Air", "Sea", "Rail" shipments.
9 properties
TrackingStatusResponse
object
Contains information about shipment status
1 property1 required
Specification
The full machine-readable OpenAPI contract behind this narrative.
Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.
Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.
MCP tools for apis
4 tools reach this content
search_api_evangelistSearch every content type across the network at once.
find_relatedThe shared-tag relevance graph — what else covers this.
get_tagEverything one tag labels, across all content types.
guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
A second provider on the same verified email joins the account you already have.
Your account
ⓘWhere this information came from
This is an independent, third-party profile of DSV Tracking API (Air, Sea, Road EU, Rail), published by
API Evangelist. We do not operate, host, resell, or
support these APIs, and we are not affiliated with or endorsed by the company unless stated above.
Everything here is built from publicly available information — the company's own site,
developer portal, documentation, public repositories, and the specifications it publishes for public use.
Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's
public API artifacts, scored against a published rubric. They are not certifications,
endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and
you do not need to justify the request. A removed company is recorded as unrated, never scored
zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy → On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.
