UPS] The XML structure of our order request has grown many years. Anytime we attached great importance to maintain the compatibility of the structure from the beginning until today. In this way the request could be enhanced successively if needed, e.g. measures, article data, special vehicles or driver and so on. Reading our short description of the order request structure could be overwhelming and so, a small but comprehensive example is the best way to get in. For most purposes this example may be sufficient . We have a fix -Header for each location (Hannover, Bremen, Berlin, Hamburg, etc.) The commission number will be your order number. [mandatory] The timestamp the order (tour) has to be executed/started can be sent as "normal" timestamp or better as UTC. [mandatory] Informations concerning the tour like accounting, processing et al. can be placed in . Similar to this in informations can be inserted for the driver. [optional] The unspecific tag structure .... .... .... serves as container for special tour values (IDs, Codes, etc.). These values will be used e.g. for sending them back in event responses. [optional] The tag aggregates all customer data with addresses, persons, companies. If the customer is a private person, please fill up the tag with the name! Inside each tag there is a tag structure, similar to the tag described above. These values will be stored for each station (customer) like a customer ID, hash, etc. If you want, please execute this script in an existing PHP environment to POST the request. You will get back a short XML response with our order number like OKnnnnnnnn Thank you very much! :-) Best regards, your Assecutor Team */ $req = " STF909266 STF909266 F80120 f288f46c5d79de67251ea00e6c7970f6e4da3b7fbbce2345d7772b0674a318d5b3758ba1faf81fdf9253465f6642dfee38853822faf9db66ed087d9e847f267a COMMNO1234 2020-07-23 12:00:00.000 0000 UTC .... "; $req = urlencode($req); ?>