Fedex Track Service v2 : Cannot Authenticate
I was trying to deploy the track service via api for one of my clients and I was using the fedex php examples they provided. Unfortunately, I kept on getting an authentication error. It seemed the credentials Fedex had provided me where invalid. I tested this across several servers and then moved on to other api calls... it seemed it was the track service that was causing the issue.
After much debugging, support tickets, and hair turned white - we were finally able to get to the bottom of it. If you look in the wsdl, the call to the gateway is being made to
https:///gateway.fedex.com:443/web.services
try changing this to
https://gatewaybeta.fedex.com:443/web.services
the simple difference is the beta in 'gatewaybeta'. This routes you to the testing servers vs the production servers.
Hope this helps you. I spent days going back and forth on this.
Labels: api, authentication, cannot, code, developer, error, fedex, gateway, key, login, meter, production, service, test, track, us, web services, wsdl
posted by mauricio @ 2:46 PM
11 Comments
11 Comments:
Thanks for posting this, I have been fighting with this for hours and FedEx's website was no help.
It's my pleasure. I appreciate that you left a comment - it lets me know that my posts actually help people and that is the goal.
Have a great day!
I downloaded their newest WSDL, PHP samples, obtained developer credentials...
I keep on getting the same authentication error - Authentication Failed.
The gateway address at the bottom of the WSDL is
https://gatewaybeta.fedex.com:443/web-services
Any ideas?
https://gatewaybeta.fedex.com:443/web-services
worked for me, make sure you fill out the developer key and password. Can you get their sample code to work?
It's not working for me and I don't know what the problem is. I tried different servers, different developer keys, but I still keep on getting this:
Error in processing transaction.
ERROR
prof
1000
Authentication Failed
I'm 100% sure that I filled out everything correctly.
if you want you can email me the code and i'll look at it for you. allen.battles@gmail.com
I have the same problem with both gatewaybeta and gateway urls.
did you manage to find out how to fix it?
I think their developer key and password system has an error in it. I requested a new developer key and password and my test project no longer worked. I got the same error you did. So I double checked everything and it still just didn't work. So I went looking through my emails and an old developer password they sent a couple of months ago and IT WORKED!! So here is my developer keys, feel free to use them. I am also including the newest password sent in case the old stops working (maybe they refresh their database).
Use This
Key = "8sC5QbaGrYCeB0Hj"
Password = "TGxPw7JKlF3Efn1EJMDGort5t"
AccountNumber = "510087348"
MeterNumber = "1227330"
If it stops working in a few days because they refresh their system use this
Password = "OFTy5fAp7qgLGEZqxrOuLijkr"
Let me know if this works for you.
Thanks all for posting your valuable comments. I just wanted to add something more into this.
I was trying so hard to get the API running but had no luck for couple of hours. I tried the test keys posted by Allen and it worked fine. The test keys I got was not working for some weird reasons. Then I has to reset the account to generate a new test security code and that worked.
So if anyone facing the same problem -- obtain a new key rather than scratching your head to figure out what's wrong with code.
I have been trying out the same for the last 2-3 days. I am using Java to generate the client program and I obtained the credentials from FedEx. But still, I am getting the 'Authentication Failed ' message when I tried to connect to the server. I contacted their tech.support and they confirmed that my credentials are valid and the only reason for me to get such an error is due to a wrong server URL. But I am sure I am using the URL which they provide (https://gatewaybeta.fedex.com:443/web-services) . I tried with what I found from here (https://gatewaybeta.fedex.com:443/web.services), but there is no difference in the result. Can some one help me on this??
if nothing else, keep pushing up the ladder at fedex. That is what I had to do... they will only validate the xml for you on the first level of support. I had to go up the ladder to talk to someone about authentication. Eventually that is how I ended up finding gatewaybeta,
Post a Comment
<< Home