GET /reference-data

The reference data service retrieves the reference data used for MyDHL API shipment or upload invoice data service.

Servers

Request headers

Name Type Required Description
Plugin-Version String No

Please provide version of the plugin (applicable to 3PV only)

Shipping-System-Platform-Version String No

Please provide version of the shipping platform (applicable to 3PV only)

Webstore-Platform-Version String No

Please provide version of the webstore platform (applicable to 3PV only)

Message-Reference-Date String No

Optional reference date in the HTTP-date format https://tools.ietf.org/html/rfc7231#section-7.1.1.2

Webstore-Platform-Name String No

Please provide name of the webstore platform (applicable to 3PV only)

Shipping-System-Platform-Name String No

Please provide name of the shipping platform(applicable to 3PV only)

Message-Reference String No

Please provide message reference

Plugin-Name String No

Please provide name of the plugin (applicable to 3PV only)

Query parameters

Name Type Required Description
datasetName String Yes

Must provide at least one datasetName value. If providing just the datasetName with no filterBy fields - the response will return the entire data set from the dataset table (bulk).

Possible values:

  • "customerPackageReferenceType"
  • "invoiceReferenceType"
  • "country"
  • "packageTypeCode"
  • "unitOfMeasurement"
  • "documentTypeCode"
  • "countryPostalcodeFormat"
  • "invoiceItemReferenceType"
  • "trackingEventCode"
  • "all"
  • "registrationNumberTypeCode"
  • "serviceCode"
  • "returnStatusMessage"
  • "commodityCategory"
  • "dangerousGoods"
  • "productCode"
  • "incoterm"
  • "customerShipmentReferenceType"
filterByAttribute String No

Use filter by attribute to define the list of supported attibuted for the specified datasetName.
List of supported attributes per dataset
(eg. dataset: supported filterByAttributes values)

a) country: countryCode, countryName
b) countryPostalcodeFormat: countryCode
c) dangerousGoods: serviceCode
d) incoterm: incoterm
e) productCode: productCode, countryCode, docNonDocIndicator
f) serviceCode: serviceCode, countryCode, chargeCodeTypeCode, serviceGroupDescription
g) packageTypeCode: packageTypeCode
h) documentTypeCode: customsDocumentTypeCode
i) customerShipmentReferenceType: shipmentReferenceTypeCode
j) customerPackageReferenceType: packageReferenceTypeCode
k) invoiceReferenceType: invoiceReferenceTypeCode
l) invoiceItemReferenceType: itemReferenceTypeCode
m) registrationNumberTypeCode: registrationTypeCode
n) commodityCategory: commodityCategoryCode, commodityCategoryGroup, commodityCategoryDescription
o) returnStatusMessage: statusCode, serviceName, operationName, protocol
p) trackingEventCode: eventTypeCode, eventTypeDescription, visibleToCustomer
q) unitOfMeasurement: unitOfMeasurement

comparisonOperator String No

Use comparison operator to define the specific match condition for optimized search.

Possible values:

  • "contains"
  • "notEqual"
  • "equal"

Default value: "equal"

queryString String No

Use queryString for additional filter criteria in format of '[attribute]:[value]:[comparisonOperator]'.
All additional filters are applied together with logical connector 'AND'.
Maximum of three additional attribute-value-comparisonOperator combinations.
Multiple queryString parameters will be separated by comma "," separator

filterByValue String No

Use filter by value to query based on the specific string for optimized search.

List of supported filterByValue per dataset (eg. dataset: filterByAttribute| supported filterByValue)

a) returnStatusMessage: serviceName|CreateShipment,DocumentImageRequest,RateRequest,RequestIdentifier,RequestPickup,AddressValidateRequest,TrackingRequest,UpdatePickup,UpdateShipment,UploadInvoiceData,DeleteShipment,DocumentRetrieve-ePOD
b) returnStatusMessage: operationName|get-image,identifiers,address-validate, RouteRequest, shipments, tracking, upload-image,landed-cost,rates,upload-invoice-data,pickup,proof-of-delivery
c) returnStatusMessage: protocol|REST,SOAP,XMLPI
d) productCode: docNonDocIndicator|Y,N

How to start integrating

  1. Add HTTP Task to your workflow definition.
  2. Search for the API you want to integrate with and click on the name.
    • This loads the API reference documentation and prepares the Http request settings.
  3. Click Test request to test run your request to the API and see the API's response.