1 General

1.1 Change History

Rev. Nr	Date	Company	Employee	Description of the change
1.0	16.09.2015	MHP	ML	Creation of the document
1.1	07.07.2016	MHP	MWi	Added the single layers of the optional fields and modified the format of the document.
1.2	05.09.2016	MHP	ML	Revised WSDL, Created an access for the test system
1.3	13.09.2016	MHP	LK	Added missing carrier short forms
1.4	12.06.2017	MHP	LRS	Added new optional fields
1.5	15.06.2017	MHP	LRS	Added new optional fields and carrier short forms
1.6	19.06.2017	MHP	LRS	General adjustments an added new parameters
1.7	22.06.2017	MHP	LRS	Invented shipment creation via PUT
1.8	23.06.2017	MHP	LRS	Added new WSDL files
1.8.1	16.08.2017	MHP	LK	Layout changes
1.8.6	09.04.2021	MHP	MWi	Update transmitted fields
1.8.7	08.07.2021	MHP	RS	Added missing carrier short forms
1.8.9	12.08.2021	MHP	MWi	Removed onlyUpdates parameter
1.8.9.1	27.09.2021	MHP	MWi	Added missing carrier shortcut AMM

1.2 Introduction

The SOAP interface is described below as offered by the Shiptrack.com Service. The interface works according to the SOAP standard. The authentication of the interface user is performed with the HTTP Basic authentication.

2.1 Collective query

URL: https://service.shiptrack.com:8443/shipments

2.1.1 GET

With the GET http method, all shipments which are assigned to the customers with the customer ID indicated in the client ID are open. The result is returned as a XML and transferred as a stream. The list of the shipment data which is returned can be limited with the following optional GET parameters:

• since:

If this parameter is selected, only data records are returned which have been added within the timeframe or for which new data were added.
Data type:
Date - Format(YYYYMMddHHmmss) in the time zone UTC or ISO-8601

• until:

If this parameter is selected, only data records are returned which have been added within the timeframe or for which new data were added.
Data type:
Date - Format(YYYYMMddHHmmss) in the time zone UTC or ISO-8601

2.2 Shipment tracking data

Via the SOAP interfaces, the shipment tracking data can be accessed using two functions which return a filtered result of the overall shipment tracking data of a customer. Both functions provide the result in the form of an XML string. Its format is explained in the next chapter. The correspponding WSDL which the SOAP web service describes is located in the Annex.

URL: https://service.shiptrack.com:8443/shipmentsSearch (Preliminary)

2.2.1 GetWithTrackingNr

Performs a search on the tracking number of a shipment or a package. The complete shipment is always returned also if the tracking number is located on the package level. Affected fields: shipment_tracking_id on the shipping level and send_id on the package level.

Parameters	Description
Client	Id of the Shiptrack.com customer. Is provided by MHP.
trackingNr	Tracking number which should be searched.

2.2.2 GetWithReferenceNr

This call allows a search on the reference numbers of a shipment both on the shipment and also on the package level. The value indicated is resarched in the following fields:: send_referenznr_01, send_referenznr_02, send_referenznr_03, send_referenznr_04, send_referenznr_05 on sending level and send_referenznr_06, send_referenznr_07, send_referenznr_08, send_referenznr_09, send_referenznr_10 on the package level.

Parameters	Description
Client	Id of the Shiptrack.com customer. Is provided by MHP.
referenceNr	Reference number which should be searched.

2.3 PUT

With the http verb PUT, one or more shipments can be sent to the service. The minimum fields which are indicated in the section 2.3.1 have to be filled for a successful transfer. After a successful transfer, the data are not immediately available for a call via the collective or single query but must instead be processed by the service.

2.3.1 Minimal Fields

Parameters	Description
shipment_tracking_id	Tracking shipment number of the freight carrier.
frachtfuehrer	Short form of the carrier with which the shipment is transported
send_versanddatum	Date on which the shipment was sent

2.3.2 Example of the creation of a single shipment

<?xml version="1.0" encoding="utf-8"?>
<workitem>
	<shipment collection="true">		
		<frachtfuehrer>HVS</frachtfuehrer>
		<send_versanddatum>
			<date>01/22/2017</date>
		</send_versanddatum>
		<shipment_tracking_id>365767978452</shipment_tracking_id>
	</shipment>
</workitem>

2.4 Shipment tracking data format

Below the format of the shipment tracking data which is returned from the interface and accepted is explained.

The data transfer is in located in XML format. The XML coding is always as as a UTF-8 and starts with the tag "workitem". Within the "workitem" tag, one more shipments can be transferred. Here a shipment is always introduced with the "shipment" tag. Here it is important for the "shipment" that the attribute "collection" always have the value"true" vorhanden ist. Also all tags which occur in XML are written in lower case letters.

Example of the basic structure:

<?xml version="1.0" encoding="utf-8"?>
<workitem>
  <shipment collection="true">
    <package collection="true">
      <article collection="true">
        
      </article>
    </package>
  </shipment>
</workitem>

Example of the basic structure with several shipments:

<?xml version="1.0" encoding="utf-8"?>
<workitem>
  <shipment collection="true">
    <package collection="true">
      <article collection="true">
        
      </article>
    </package>
  </shipment>
  <shipment collection="true">
    <package collection="true">
      <article collection="true">
        
      </article>
    </package>
  </shipment>
  <shipment collection="true">
    <package collection="true">
      <article collection="true">
        
      </article>
    </package>
  </shipment>
</workitem>

A shipment can include one or more packages. Here a shipment is always introduced with the "package" tag. Also for this tag, the attribute "collection" must be indicated with the value "true".

Example of a shipment with one package:

<?xml version="1.0" encoding="utf-8"?>
<workitem>
  <shipment collection="true">
    <package collection="true">
      
    </package>
  </shipment>
</workitem>

Example of a shipment with several packages:

<?xml version="1.0" encoding="utf-8"?>
<workitem>
  <shipment collection="true">
    <package collection="true">

    </package>

    <package collection="true">

    </package>

    <package collection="true">

    </package>
  </shipment>
</workitem>

Thus, at least the following message is transmitted:

<?xml version="1.0" encoding="utf-8"?>
<workitem>
  <shipment_count>0</shipment_count>
</workitem>

A query which includes data has the following structure:

<?xml version="1.0" encoding="utf-8"?>
<workitem>
  <shipment collection="true">
    <frachtfuehrer>UPS</frachtfuehrer>
    <abs_adr_01>MHP SOFTWARE GMBH</abs_adr_01>
    <empf_adr_01>ROSEN VERSENDER</empf_adr_01>
    <empf_adr_02>ZHD ROSENVERKAEFAUER 1</empf_adr_02>
    <abs_strasse>JUSTUS-VON-LIEBIG-STRASSE 3</abs_strasse>
    <abs_ort>NEUSTADT A. RBGE.</abs_ort>
    <abs_plz>31535</abs_plz>
    <abs_land_kurz>DE</abs_land_kurz>
    <empf_strasse>MARIA-KIRCHNER-STR. 32</empf_strasse>
    <empf_ort>ARNSTORF</empf_ort>
    <empf_plz>94424</empf_plz>
    <empf_land_kurz>DE</empf_land_kurz>
    <send_referenznr_01>5601519</send_referenznr_01>
    <send_abholdatum>
      <date>03/24/2014</date>
    </send_abholdatum>
    <send_versanddatum>
      <date>03/24/2014</date>
    </send_versanddatum>
    <send_gewichtgesamt>1.00</send_gewichtgesamt>
    <package collection="true">
      <collection_index>1</collection_index>
      <send_id>1Z7110966853336416</send_id>
      <send_gewichteinzel>1</send_gewichteinzel>
      <package_tracking_status collection="true">
        <status_country>DE</status_country>
        <status_code>Manifest Pickup</status_code>
        <status_path collection="true">
          <collection_index>1</collection_index>
          <status_code>data_transmitted</status_code>
        </status_path>
        <status_path_count>1</status_path_count>
        <status_date>
          <time>12:39:40</time>
          <date>03/24/2014</date>
        </status_date>
        <status_details>Order Processed: Ready for UPS</status_details>
        <collection_index>1</collection_index>
      </package_tracking_status>
      <package_tracking_status collection="true">
        <status_country>DE</status_country>
        <status_city>HERFORD</status_city>
        <status_code>Pick-Up</status_code>
        <status_path collection="true">
          <collection_index>1</collection_index>
          <status_code>pick_up</status_code>
        </status_path>
        <status_path_count>1</status_path_count>
        <status_date>
          <time>19:35:00</time>
          <date>03/24/2014</date>
        </status_date>
        <status_details>Origin Scan</status_details>
        <collection_index>2</collection_index>
      </package_tracking_status>
      <package_tracking_status collection="true">
        <status_country>DE</status_country>
        <status_city>HERFORD</status_city>
        <status_code>In transit</status_code>
        <status_path collection="true">
          <collection_index>1</collection_index>
          <status_code>transit</status_code>
        </status_path>
        <status_path_count>1</status_path_count>
        <status_date>
          <time>23:00:00</time>
          <date>03/24/2014</date>
        </status_date>
        <status_details>Departure Scan</status_details>
        <collection_index>3</collection_index>
      </package_tracking_status>
      <package_tracking_status collection="true">
        <status_country>DE</status_country>
        <status_city>NURNBERG</status_city>
        <status_code>In transit</status_code>
        <status_path collection="true">
          <collection_index>1</collection_index>
          <status_code>transit</status_code>
        </status_path>
        <status_path_count>1</status_path_count>
        <status_date>
          <time>05:54:00</time>
          <date>03/25/2014</date>
        </status_date>
        <status_details>Arrival Scan</status_details>
        <collection_index>4</collection_index>
      </package_tracking_status>
      <package_tracking_status collection="true">
        <status_country>DE</status_country>
        <status_city>NURNBERG</status_city>
        <status_code>In transit</status_code>
        <status_path collection="true">
          <collection_index>1</collection_index>
          <status_code>transit</status_code>
        </status_path>
        <status_path_count>1</status_path_count>
        <status_date>
          <time>19:43:00</time>
          <date>03/25/2014</date>
        </status_date>
        <status_details>Departure Scan</status_details>
        <collection_index>5</collection_index>
      </package_tracking_status>
      <package_tracking_status collection="true">
        <status_country>DE</status_country>
        <status_city>OETZING</status_city>
        <status_code>In transit</status_code>
        <status_path collection="true">
          <collection_index>1</collection_index>
          <status_code>transit</status_code>
        </status_path>
        <status_path_count>1</status_path_count>
        <status_date>
          <time>22:00:00</time>
          <date>03/25/2014</date>
        </status_date>
        <status_details>Arrival Scan</status_details>
        <collection_index>6</collection_index>
      </package_tracking_status>
      <package_tracking_status collection="true">
        <status_country>DE</status_country>
        <status_city>OETZING</status_city>
        <status_code>In transit</status_code>
        <status_path collection="true">
          <collection_index>1</collection_index>
          <status_code>transit</status_code>
        </status_path>
        <status_path_count>1</status_path_count>
        <status_date>
          <time>09:27:00</time>
          <date>03/26/2014</date>
        </status_date>
        <status_details>Destination Scan</status_details>
        <collection_index>7</collection_index>
      </package_tracking_status>
      <package_tracking_status collection="true">
        <status_country>DE</status_country>
        <status_city>ARNSTORF</status_city>
        <status_zip>94424</status_zip>
        <status_recipient>MUELLER</status_recipient>
        <status_code>Delivered</status_code>
        <status_path collection="true">
          <collection_index>1</collection_index>
          <status_code>delivered</status_code>
        </status_path>
        <status_path_count>1</status_path_count>
        <status_date>
          <time>13:41:00</time>
          <date>03/26/2014</date>
        </status_date>
        <status_details>Package/Shipment delivered</status_details>
        <collection_index>8</collection_index>
      </package_tracking_status>
      <package_tracking_status_count>8</package_tracking_status_count>
    </package>
    <package_count>1</package_count>
    <shipment_tracking_id>1Z7110966853336416</shipment_tracking_id>
    <shipment_id>3a7b13db-b20a-45bd-8e05-575e1311f2fb</shipment_id>
    <shipment_tracking_status>
      <status_first_refresh_date>
        <time>12:39:40</time>
        <date>03/24/2014</date>
      </status_first_refresh_date>
      <status_last_refresh_date>
        <time>13:41:00</time>
        <date>03/26/2014</date>
      </status_last_refresh_date>
      <status_code>delivered</status_code>
      <status_date>
        <timezone>
          <name>UTC</name>
          <offset>+0000</offset>
        </timezone>
        <time>09:26:12</time>
        <date>08/01/2014</date>
      </status_date>
    </shipment_tracking_status>
    <collection_index>1</collection_index>
  </shipment>
  <shipment_count>1</shipment_count>
</workitem>

2.4.1 Status Codes

In the returned result, both the status values on the shipment level can be found on the shipment level under the code shipment.shipment_tracking_id.status_code as well as on the level of the individual packages. They can be found under the code shipment.package.package_tracking_status.status_path. The codes indicated include status codes standardised by MHP. These status codes are listed in the Annex in separate tables.

The status code which can be found undershipment.package.package_tracking_status.status_code is the original status code sent by the freight carrier.

2.4.2 Minimum fields

The results can be included more or less depending on the existing information volume. In the following table, all fields are listed with a description which is at least sent along with every query.

Field	Description
shipment_tracking_id	Tracking shipment number of the freight carrier.
shipment_id	Unique Id of the shipment in the Shiptrack.com system.
frachtfuehrer	Short form of the freight carrier with which the shipment is sent.
package.send_id	Tracking package number of the freight carrier.
send_versanddatum	Date on which the shipment was sent.

2.4.3 Date values

Date values are always shown in the shipment data:

  <timezone>
    <name>UTC</name>
    <offset>+0000</offset>
  </timezone>	
  <time>09:26:12</time>
  <date>08/01/2014</date>

Field	Description
date	Date in format mm/dd/yyyy
time	Time in format hh:mm:ss
timezone	Time zone. Optional field. If the field is not indicated, the time zone is not known.
timezone.name	Name of the time zone
timezone.offset	Offset to the UTC time zone

2.4.4 Optional fields

The optional fields are listed below which are included in the response. The individual levels are separated using points.

Field	Description
abs_adr_01	Consignor Address 1
abs_adr_02	Consignor Address 2
abs_adr_03	Consignor Address 3
abs_strasse	Street of the Consignor
abs_plz	Zip code of the Consignor
abs_ort	City of the Consignor
abs_land_kurz	Two-digit consignor country shortcut (ISO3166)
empf_adr_01	Consignee Address 1
empf_adr_02	Consignee Address 2
empf_adr_03	Consignee Address 3
empf_strasse	Street of the consignee
empf_plz	Zip code of the consignee
empf_ort	City of the consignee
empf_land_kurz	Two-digit Consignee country shortcut (ISO3166)

2.4.4.1 Shipment Layer

All that fields can appear on the first layer: The Shipment-Layer.

Field	Description
send_referenznr_1	Reference number 1
send_referenznr_2	Reference number 2
send_referenznr_3	Reference number 3
send_referenznr_4	Reference number 4
send_referenznr_5	Reference number 5
abs_adr_01	Consignor Address 1
abs_adr_02	Consignor Address 2
abs_adr_03	Consignor Address 3
abs_strasse	Street of the consignor
abs_plz	Zip code of the consignor
abs_ort	City of the consignor
abs_land	Country of the consignor
abs_land_kurz	Two-digit consignor country shortcut (ISO3166)
abs_region	State/Province of the consignor
abs_mail	E-Mail Address of the consignor
abs_telefon	Telephone number of the consignor
abs_telefax	Fax of the consignor
abs_steuernr	Tax number of the consignor
abs_loc	Location of the consignor
empf_adr_01	Consignee Address 1
empf_adr_02	Consignee Address 2
empf_adr_03	Consignee Address 3
empf_strasse	Street of the consignee
empf_hnr	House Number of the consignee
empf_plz	Zip code of the consignee
empf_ort	City of the consignee
empf_land_kurz	Two-digit consignee country shortcut (ISO3166)
empf_land	Country of the consignee
empf_staat	State of the consignee
empf_iso	Iso code of the consignee
empf_nationalitaet	Nationality of the consignee
Empf_postfach	P.O. Box of the consignee
empf_mail	E-Mail Address of the consignee
empf_tel	Telephone number of the consignee
empf_kdnr	Customer number of the consignee
send_gewichtgesamt	Weight of all packages of a shipment
shipment_tracking_url	Link to a booking portal page with tracking information
send_abholdatum	Pickup-Date of the shipment
send_anz	Amount of packages in a shipment
send_kundenkennung	if necessary special customer number
send_termindatum	Delivery maturity
send_service_code	Code for additional information for the shipment
send_service_details	Additional information for the shipment
send_art_lademittel_01	Pallet, package ...
send_nachnahmebetrag	COD amount
send_nachnahmewaehrung	Currency of the COD amount
send_mandant	Client of a shipment
send_service_code	Service code
send_service_details	Details of the service type
send_customerservice	Designation of the service type (e.g. Express, Overnight)

2.4.4.2 Shipmentstatus-Layer

All that fields can appear on the Shipment-Tracking-Status-Layer.

Field	Description
status_date	Status date
status_code	MHP-Statuscode

2.4.4.3 Package-Layer

All that fields can appear on the Package-Layer.

Field	Description
send_referenznr_6	Reference number 6
send_referenznr_7	Reference number 7
send_referenznr_8	Reference number 8
send_referenznr_9	Reference number 9
send_referenznr_10	Reference number 10
send_anzahllademittel_01	Number of loading equipment 01
send_anzahllademittel_02	Number of loading equipment 02
send_anzahllademittel_03	Number of loading equipment 03
send_anzahllademittel_04	Number of loading equipment 04
send_artlademittel_01	Kind of loading equipment 01
send_gewichteinzel	Weight of the package
send_hoehe	Height of the package
send_laenge	Length of the package
send_breite	Width of the package
send_versandart	Kind of delivery
send_zusatz	Additional package

2.4.4.4 Package-Status-Layer

All that fields can appear on the Package-Status-Layer.

Field	Description
status_date	Date, on which the status is occurred
status_details	Details, which are available for the occurred status
status_code	Statuscode
status_path.status_code	MHP-Statuscode
Status_recipient	The recipient of the package
status_drop_location	details, where for example the package is stored
status_country	Shortcut for the country Code of the status
status_zip	Zip code of the status
status_city	City of the status
status_state	State of the status
status_street	Street, where the status occurred
status_depot_name	Name of the depot, where the status occurred
status_additional_info	Additional information for the status
status_loc	Location of the status

3 Annex

3.1 Possible status codes on the shipping level

Below all status codes are listed which are used on the shipment and package level.

Hauptstatus	Unterstatus	Beschreibung
data_transmitted		Parcel data has been transmitted
delay		Delayed
delay	car_damaged	Vehicle damaged
delay	customs	Parcel has been checked by customs
delay	delivery_attempt	Delivery attempt
delay	goods_receipt_closed	Goods department closed
delay	holiday	Holiday
delay	rerouting	Rerouting
delay	resources_exceeded	Resources exceeded (time, space,...)
delay	shelved	Shelved, based on holiday or customers request
delay	strike	Strike
delay	traffic	Traffic
delay	weather	Force majeure
delivered		Parcel has been delivered
delivered	at_neighbor	Delivered to a neighbor
delivered	autoDelivery	The delivery was automatically set to "Delivered" because no error status was received within 48 hours of receiving the delivery status
delivered	customer_picked_up	Picked up by the customer
delivered	picked_up_from_customs	Picked up by the customer at customs
delivered	defect_delivered	Defective delivered to the parcel shop or recipient
delivered	partially	Partially delivered
delivered	storage_location	Stored at the agreed storage location
delivered	po_box_deposit	Stored in the PO box
deny		Package refused
fault		Error
fault	canceled	Canceled by the sender
fault	damaged	Shipment was damaged
fault	destroyed	The consignment was destroyed on request. Tracking process ends
fault	incomplete	Shipment is incomplete
fault	missing	Shipment missing
fault	missing_documents	Missing, faulty documents
fault	no_label	Missing, faulty label
fault	not_allowed	Prohibited goods
fault	return	Sent back by the carrier
fault	stolen	Consignment was stolen
fault	wrong_address	The recipient is not known at the given address
fault	receiver_moved	The recipient moved
information		information
information	inserted_in_system	The shipment was added to Shiptrack.com
information	pod_available	Receipt added
out_for_delivery		Consignment on the way to the recipient
pick_up		Shipment was picked up at the recipient
transit		In transit
transit	accesspoint	Arrived at the packing station / post office / parcel shop and ready for collection
transit	customs_out	The shipment has been released by customs
transit	depot_in	Arrived at the depot
transit	depot_out	Left the depot
undefined		Unknown status

3.2 Freight carrier short form

All currently known freight carrier short form codes are listed below.

Kürzel	Frachtführer
ABCLOGISTIK	ABC-Logistik GmbH
APAEXPRESS	DHL Parcel Austria
DPDAT	DPD Österreich / Prime Time
ASR	DB Schenker Österreich
ATP	Österreichische Post (AG)
BDP	Belgische Post (Bpost)
BLM	Bleckmann Niederlande
BOOS	Boos Logistik Service
BRT	Bartolini Italien
BURSPED	Bursped Speditions-G.m.b.H. & Co.
CAM	Camion Transport AG.
CES	City Express Serbia
CHE	Schweizer Post Express
CHP	Schweizer Post (CH)
COLISSIMO	Colissimo FR
COU	Coureon Logistics GmbH
CPL	Planzer Transport AG (Schweiz)
CTT	Correios de Portugal
DCH	Dachser Intelligent Logistics
DHC	DHL Parcel Connect
DHL	DHL Paket
DHB	DHL Benelux
DHLEXPRESS	DHL Express
DHM	DHL Home Delivery 2-Mann-Handling
DHN	DHL Parcel Netherland
DKS	Logwin Holding Aschaffenburg GmbH
DPB	Deutsche Post AG (DV-Freimachung von Briefsendungen)
DPD	Dynamic Parcel Distribution - Geopost
DPDUK	Dynamic Parcel Distribution United Kingdom
DSV	DSV Air & Sea Germany GmbH
DSW	SwipBox
DTL	Deutsche Textil Logistik
DZS	DHL Freight (Danzas)
EAK	Azkar, Dachser Spanien
ECS	Correos ES . Public
EMS	Emons Spedition GmbH
ESR	SEUR (E)
ETS	TIP SA Spain
FCP	Colis Privé
FCR	Chronopost Frankreich
FDE	Delivengo
FDX	FedEx
FMR	Mondial Relay Distribution FR
FNT	TNT Express Frankreich
FPD	DPD Frankreich
FRP	La Poste (FR)
FSR	DB Schenker Frankreich
GEFCO	Groupages express de Franche-Comté
GEL	Express Logistik
GLS	General Logistic Systems
GLSFR	General Logistic Systems France
GLSHU	General Logistic Systems Hungary
GLSRO	General Logistic Systems Romania
GLSSL	General Logistic Systems Slovenia
GON	General Overnight (GO!) Express & Logistics
GPC	Geis Parcel Slovakia CZ
GSM	The Delivery Group (Secured Mail)
GWW	Gebrüder Weiss Gesellschaft m.b.H.
HEPPNER	Spedition Heppner
HES	Hermes 2 Man Handling
HVS	Hermes Versand Service
HWL	Hellmann Worldwide Logistics
IDSGEIS	Hans Geis
IDSKUN	Kühne & Nagel
IDSSCHMID	Spedition Andreas Schmid Logistik AG
INNIGHTBENELUX	Nox Nachtexpress NL, BE
INNIGHTDEAT	Nox Nachtexpress DE, AT
INS	Intersoft
JENTSCH	Jentsch Logistik
KIA	Kiala
KNUBBEN	Spedition Knubben (OSL)
KIESSLING	Spedition Kiessling
KLEINE	Spedition Kleine
KOESTERHAPKE	Köster & Hapke Internationale Spedition
LAGERMAX	Spedition Lagermax
NBR	Bring Parcel Norway
NCT	Neutral Carrier Tracking (MHP)
NELLENQUACK	Nellen & Quack Spedition und Logistik
NGL	GLS Netherlands
NOLIMIT	No Limits Trans GmbH Polen
NOTHEGGER	Nothegger Transport Logistik GmbH
NSE	Night Star Express
NTGLOGISTICS	NTG Logistik
NTS	National Transport Service GmbH
OETJEN	Spedition Oetjen
ONTIME	Ontime Logistics
OPL	Opal
PDK	Post Denmark
PHL	DHL Parcel Poland
PON	Post Nord
QUEHENBERGER	Quehenberger Logistics
PIP	Inpost Poland
PLP	Poczta Polska
PPL	Professional Parcel Logistic
RABEN	Raben Group
RHE	Rhenus Logistics
RUEDINGER	Rüdinger Spedition
SCHAEF	Schäflein Spedition GmbH
SDG	7Days Logistics
SEVENSENDERS	Seven Senders GmbH
SKP	Slovenská pošta
SKR	Schenker Deutschland AG
STRECK	Streck Transport Spedition
SWL	SkyNet Worldwide Express
TCS	TCS Sterne
THIJS	Thijs Logistiek
TMD	Transmed Transportmanagement
TML	TM Logistik & Services
TNT	Thomas Nationwide Transport
TOF	Trans-o-flex
TPG	Post (Niederlande)
UKM	DHL Parcel UK Mail
UPS	United Parcel Service
WLS	WLS Spedition GmbH
YDL	Yodel Delivery Network Limited
ZOBEL	Gebr. Zobel & Co. Speditions GmbH
UPS	United Parcel Service
WLS	WLS Spedition GmbH
YDL	Yodel Delivery Network Limited
ZOBEL	Gebr. Zobel & Co. Speditions GmbH
UKM	DHL Parcel UK Mail
UPS	United Parcel Service
WLS	WLS Spedition
ZOBEL	Spedition Zobel

3.4 WSDL

3.4.1 WSDL for shipments

<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex" xmlns:i0="http://tempuri.org/" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:wsa10="http://www.w3.org/2005/08/addressing" xmlns:wsp="http://www.w3.org/ns/ws-policy" xmlns:wsap="http://schemas.xmlsoap.org/ws/2004/08/addressing/policy" xmlns:msc="http://schemas.microsoft.com/ws/2005/12/wsdl/contract" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://mhp-net.de/services/vinfo/shipments" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" name="Shipments" targetNamespace="http://mhp-net.de/services/vinfo/shipments">
	<wsdl:import namespace="http://tempuri.org/" location="https://service.shiptrack.com:8443/shipments?wsdl=wsdl0"/>
	<wsdl:types>
		<xsd:schema targetNamespace="http://mhp-net.de/services/vinfo/shipments/Imports">
			<xsd:import schemaLocation="https://service.shiptrack.com:8443/shipments?xsd=xsd0" namespace="http://mhp-net.de/services/vinfo/shipments"/>
			<xsd:import schemaLocation="https://service.shiptrack.com:8443/shipments?xsd=xsd1" namespace="http://schemas.microsoft.com/2003/10/Serialization/"/>
		</xsd:schema>
	</wsdl:types>
	<wsdl:message name="Shipments_Put_InputMessage">
		<wsdl:part name="parameters" element="tns:Put"/>
	</wsdl:message>
	<wsdl:message name="Shipments_Put_OutputMessage">
		<wsdl:part name="parameters" element="tns:PutResponse"/>
	</wsdl:message>
	<wsdl:message name="Shipments_Get_InputMessage">
		<wsdl:part name="parameters" element="tns:Get"/>
	</wsdl:message>
	<wsdl:message name="Shipments_Get_OutputMessage">
		<wsdl:part name="parameters" element="tns:GetResponse"/>
	</wsdl:message>
	<wsdl:portType name="Shipments">
		<wsdl:operation name="Put">
			<wsdl:input wsam:Action="http://mhp-net.de/services/vinfo/shipments/Shipments/Put" message="tns:Shipments_Put_InputMessage"/>
			<wsdl:output wsam:Action="http://mhp-net.de/services/vinfo/shipments/Shipments/PutResponse" message="tns:Shipments_Put_OutputMessage"/>
		</wsdl:operation>
		<wsdl:operation name="Get">
			<wsdl:input wsam:Action="http://mhp-net.de/services/vinfo/shipments/Shipments/Get" message="tns:Shipments_Get_InputMessage"/>
			<wsdl:output wsam:Action="http://mhp-net.de/services/vinfo/shipments/Shipments/GetResponse" message="tns:Shipments_Get_OutputMessage"/>
		</wsdl:operation>
	</wsdl:portType>
	<wsdl:service name="Shipments">
		<wsdl:port name="BasicHttpBinding_Shipments" binding="i0:BasicHttpBinding_Shipments">
			<soap:address location="https://service.shiptrack.com:8443/shipments"/>
		</wsdl:port>
	</wsdl:service>
</wsdl:definitions>

3.4.2 WSDL for shipmentsSearch

<wsdl:definitions name="ShipmentsSearch" targetNamespace="http://mhp-net.de/services/vinfo/shipmentsSearch" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex" xmlns:wsap="http://schemas.xmlsoap.org/ws/2004/08/addressing/policy" xmlns:msc="http://schemas.microsoft.com/ws/2005/12/wsdl/contract" xmlns:i0="http://tempuri.org/" xmlns:wsp="http://www.w3.org/ns/ws-policy" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="http://mhp-net.de/services/vinfo/shipmentsSearch" xmlns:wsa10="http://www.w3.org/2005/08/addressing" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">
  <wsp:Policy wsu:Id="BasicHttpBinding_ShipmentsSearch_policy">
    <wsp:ExactlyOne>
      <wsp:All>
        <sp:TransportBinding xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
          <wsp:Policy>
            <sp:TransportToken>
              <wsp:Policy>
                <sp:HttpsToken RequireClientCertificate="false"/>
              </wsp:Policy>
            </sp:TransportToken>
            <sp:AlgorithmSuite>
              <wsp:Policy>
                <sp:Basic256/>
              </wsp:Policy>
            </sp:AlgorithmSuite>
            <sp:Layout>
              <wsp:Policy>
                <sp:Lax/>
              </wsp:Policy>
            </sp:Layout>
            <sp:IncludeTimestamp/>
          </wsp:Policy>
        </sp:TransportBinding>
        <sp:SignedSupportingTokens xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
          <wsp:Policy>
            <sp:UsernameToken sp:IncludeToken="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient">
              <wsp:Policy>
                <sp:WssUsernameToken10/>
              </wsp:Policy>
            </sp:UsernameToken>
          </wsp:Policy>
        </sp:SignedSupportingTokens>
        <sp:Wss10 xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
          <wsp:Policy/>
        </sp:Wss10>
      </wsp:All>
    </wsp:ExactlyOne>
  </wsp:Policy>
  <wsdl:types>
    <xs:schema elementFormDefault="qualified" targetNamespace="http://mhp-net.de/services/vinfo/shipmentsSearch" xmlns:xs="http://www.w3.org/2001/XMLSchema">
      <xs:import namespace="http://schemas.microsoft.com/2003/10/Serialization/"/>
      <xs:element name="GetWithTrackingNr">
        <xs:complexType>
          <xs:sequence>
            <xs:element minOccurs="0" name="client" type="q1:guid" xmlns:q1="http://schemas.microsoft.com/2003/10/Serialization/"/>
            <xs:element minOccurs="0" name="trackingNr" nillable="true" type="xs:string"/>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="GetWithTrackingNrResponse">
        <xs:complexType>
          <xs:sequence>
            <xs:element minOccurs="0" name="GetWithTrackingNrResult" nillable="true" type="xs:string"/>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="GetWithReferenceNr">
        <xs:complexType>
          <xs:sequence>
            <xs:element minOccurs="0" name="client" type="q2:guid" xmlns:q2="http://schemas.microsoft.com/2003/10/Serialization/"/>
            <xs:element minOccurs="0" name="referenceNr" nillable="true" type="xs:string"/>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="GetWithReferenceNrResponse">
        <xs:complexType>
          <xs:sequence>
            <xs:element minOccurs="0" name="GetWithReferenceNrResult" nillable="true" type="xs:string"/>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:schema>
    <xs:schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://schemas.microsoft.com/2003/10/Serialization/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://schemas.microsoft.com/2003/10/Serialization/">
      <xs:element name="anyType" nillable="true" type="xs:anyType"/>
      <xs:element name="anyURI" nillable="true" type="xs:anyURI"/>
      <xs:element name="base64Binary" nillable="true" type="xs:base64Binary"/>
      <xs:element name="boolean" nillable="true" type="xs:boolean"/>
      <xs:element name="byte" nillable="true" type="xs:byte"/>
      <xs:element name="dateTime" nillable="true" type="xs:dateTime"/>
      <xs:element name="decimal" nillable="true" type="xs:decimal"/>
      <xs:element name="double" nillable="true" type="xs:double"/>
      <xs:element name="float" nillable="true" type="xs:float"/>
      <xs:element name="int" nillable="true" type="xs:int"/>
      <xs:element name="long" nillable="true" type="xs:long"/>
      <xs:element name="QName" nillable="true" type="xs:QName"/>
      <xs:element name="short" nillable="true" type="xs:short"/>
      <xs:element name="string" nillable="true" type="xs:string"/>
      <xs:element name="unsignedByte" nillable="true" type="xs:unsignedByte"/>
      <xs:element name="unsignedInt" nillable="true" type="xs:unsignedInt"/>
      <xs:element name="unsignedLong" nillable="true" type="xs:unsignedLong"/>
      <xs:element name="unsignedShort" nillable="true" type="xs:unsignedShort"/>
      <xs:element name="char" nillable="true" type="tns:char"/>
      <xs:simpleType name="char">
        <xs:restriction base="xs:int"/>
      </xs:simpleType>
      <xs:element name="duration" nillable="true" type="tns:duration"/>
      <xs:simpleType name="duration">
        <xs:restriction base="xs:duration">
          <xs:pattern value="\-?P(\d*D)?(T(\d*H)?(\d*M)?(\d*(\.\d*)?S)?)?"/>
          <xs:minInclusive value="-P10675199DT2H48M5.4775808S"/>
          <xs:maxInclusive value="P10675199DT2H48M5.4775807S"/>
        </xs:restriction>
      </xs:simpleType>
      <xs:element name="guid" nillable="true" type="tns:guid"/>
      <xs:simpleType name="guid">
        <xs:restriction base="xs:string">
          <xs:pattern value="[\da-fA-F]{8}-[\da-fA-F]{4}-[\da-fA-F]{4}-[\da-fA-F]{4}-[\da-fA-F]{12}"/>
        </xs:restriction>
      </xs:simpleType>
      <xs:attribute name="FactoryType" type="xs:QName"/>
      <xs:attribute name="Id" type="xs:ID"/>
      <xs:attribute name="Ref" type="xs:IDREF"/>
    </xs:schema>
  </wsdl:types>
  <wsdl:message name="ShipmentsSearch_GetWithTrackingNr_InputMessage">
    <wsdl:part name="parameters" element="tns:GetWithTrackingNr"/>
  </wsdl:message>
  <wsdl:message name="ShipmentsSearch_GetWithTrackingNr_OutputMessage">
    <wsdl:part name="parameters" element="tns:GetWithTrackingNrResponse"/>
  </wsdl:message>
  <wsdl:message name="ShipmentsSearch_GetWithReferenceNr_InputMessage">
    <wsdl:part name="parameters" element="tns:GetWithReferenceNr"/>
  </wsdl:message>
  <wsdl:message name="ShipmentsSearch_GetWithReferenceNr_OutputMessage">
    <wsdl:part name="parameters" element="tns:GetWithReferenceNrResponse"/>
  </wsdl:message>
  <wsdl:portType name="ShipmentsSearch">
    <wsdl:operation name="GetWithTrackingNr">
      <wsdl:input wsam:Action="http://mhp-net.de/services/vinfo/shipmentsSearch/ShipmentsSearch/GetWithTrackingNr" mes-sage="tns:ShipmentsSearch_GetWithTrackingNr_InputMessage"/>
      <wsdl:output wsam:Action="http://mhp-net.de/services/vinfo/shipmentsSearch/ShipmentsSearch/GetWithTrackingNrResponse" message="tns:ShipmentsSearch_GetWithTrackingNr_OutputMessage"/>
    </wsdl:operation>
    <wsdl:operation name="GetWithReferenceNr">
      <wsdl:input wsam:Action="http://mhp-net.de/services/vinfo/shipmentsSearch/ShipmentsSearch/GetWithReferenceNr" mes-sage="tns:ShipmentsSearch_GetWithReferenceNr_InputMessage"/>
      <wsdl:output wsam:Action="http://mhp-net.de/services/vinfo/shipmentsSearch/ShipmentsSearch/GetWithReferenceNrResponse" message="tns:ShipmentsSearch_GetWithReferenceNr_OutputMessage"/>
    </wsdl:operation>
  </wsdl:portType>
  <wsdl:binding name="BasicHttpBinding_ShipmentsSearch" type="tns:ShipmentsSearch">
    <wsp:PolicyReference URI="#BasicHttpBinding_ShipmentsSearch_policy"/>
    <soap:binding transport="http://schemas.xmlsoap.org/soap/http"/>
    <wsdl:operation name="GetWithTrackingNr">
      <soap:operation soapAction="http://mhp-net.de/services/vinfo/shipmentsSearch/ShipmentsSearch/GetWithTrackingNr" style="document"/>
      <wsdl:input>
        <soap:body use="literal"/>
      </wsdl:input>
      <wsdl:output>
        <soap:body use="literal"/>
      </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="GetWithReferenceNr">
      <soap:operation soapAction="http://mhp-net.de/services/vinfo/shipmentsSearch/ShipmentsSearch/GetWithReferenceNr" style="document"/>
      <wsdl:input>
        <soap:body use="literal"/>
      </wsdl:input>
      <wsdl:output>
        <soap:body use="literal"/>
      </wsdl:output>
    </wsdl:operation>
  </wsdl:binding>
  <wsdl:service name="ShipmentsSearch">
    <wsdl:port name="BasicHttpBinding_ShipmentsSearch" bind-ing="tns:BasicHttpBinding_ShipmentsSearch">
      <soap:address loca-tion="https://service.shiptrack.com:8443/shipmentssearch"/>
    </wsdl:port>
  </wsdl:service>
</wsdl:definitions>

shiptrack.com SOAP Interface - english