Thankfully I am enormously competent with the Internet, and my incredibly extended experience made me aware of a very convenient, if somewhat confidential, service called Google. Interacting with this service for "UDIAuthToken" uncovered some pretty deep secrets, in particular that this parameter appears to be connected with a product called OMX from OrderMotion -- apparently a software platform for doing e-commerce. A parameter called "UDIAuthToken" is shown as part of some XML-based syntax in this document with this comment:
<!---- Info. by OM --->
From this information, I infer that the "UDIAuthToken" parameter is a value which, from the API user's point of view (that's you), is quite opaque and is supposed to be provided "as is" by the software vendor. Thus, it probably encodes some license information. 160 hexadecimal characters means 80 bytes; with Base64 it would be 120 bytes. That's more than a simple hash; that's actually enough to do some serious cryptography, including encryption and signatures. IF this cryptography was done properly (an always risky bet, given the average competence of developers in the whole industry), THEN you would have a hard time forging a fake value for this parameter that the server would accept. After all, the point of licensing tokens is to remain under exclusive control of the software vendor.