gee38l:
Ok got the demo to bring up quotes but for the life of me can't get my details to work. I spoke to the TNT help desk got RTT enabled and they said my current details should work fine
OK, before I go any further, I will explain how the 'Demo' works.
The TNT servers don't actually have a demo/test account for us developers to work with, so when the username 'Demo' is received by the ozpost servers, this name, the password, and the account details (if supplied) are replaced by real/valid details from a friends TNT account (used with permission), so this tells me/us that there is nothing amiss with the data being sent to the TNT servers, and that their servers are functioning correctly, at least for this friends account.
I've also verified that this 'Demo' account works (in fact I tested this before asking you to, which is why I was quite surprised when you said it didn't work when you first tried it), but as an additional test, I removed one of the digits from his account number just to be sure that TNT haven't changed their response codes, and as expected I received the "The account number supplied is invalid or not assigned to this login" response.
This has made it quite 'obvious' that it is indeed a username/password error associated with your account.
The problem now is what is wrong?
One of the things that come to mind is the length of the username or password. When I was 1st setting this up several years ago I discovered a flaw in their web interface in that it was truncating the input fields at 'x' number of characters (sorry, I can't remember the actual length. The result of this being if for example, the password entered was "thisinsmypassword" what was actually being saved by TNT was something like "thisismypass". Needless to say, because this was only applicable to their web interface. it was never seen as a problem until "thisismypassword" was entered into the ozpost settings which then caused a password mismatch. ozpost was sending "thisinsmypassword" but the TNT servers are/were expecting "thisismypass", so that is one possibility.
Another possible cause is if the username (or password) contains any 'special characters' that are filtered by their web interface, but not filtered by their API. I recall at least one case where this was a problem, and the solution was for the customer to change the username or password so it doesn't contain any of these 'special' characters.
Other than these two things I'm pretty much out of ideas. About the only thing I can say for sure is that it definitely is username/password related, and it is almost certainly caused by a difference between how thier website(s) handle these inputs vs how their API handles the same inputs.
Therefore, my suggestion is to firstly change both your username and password so they don't contain anything other than alphanumerics, and to keep both of them under 12-15 characters. If this STILL causes a problem then if I could get you to PM the details you are using (no need for the account number, because as noted, this gives a different error) and I'll be able to insert then directly into the ozpost server requests and investigate further.
Cheers
RodG
