I work for fedex and answer questions about xml and tagged input files that are sent to our backend servers. I am here to try to clear up some information that is being reported in these forums.
To answer the most common question, Yes, fedex is doing away with the old legacy api server, if you are pointing your software to https://gateway.fedex.com:443/GatewayDC then this server will be shut down approximately June 2012, although I don't want to be quoted on that because things can always change. However, If you have a meter that was generated on this server and authenticates using only a fedex account and meter number to connect, you will still be allowed to generate a meter number with the module that was certified for use on this server. Unless things change, i am still able to use our own api front end application to generate meters on this server. IT WILL STILL WORK IF THE MODULE IS FUNCTIONING PROPERLY... i hope you all read that last part carefully.
The problem begins where if your meter is "fast routed" to transfer your transaction to our web services server, It will still calculate costs but might give back undesired results from what I have seen. I don't know the exact reason why the fedex programmers are fast routing meters to point to our web services app, the best reason I can think of would be so all the thousands of customers that are still using this authentication method will still have a working module come June 2012.
What we have been telling our customers since November 2007, although the programmers are the real persons responsible for developing the application is to start building new modules using our web services solution.
All the documentation and even sample code is available at fedex.com/developer. You dont need a fedex account to develop an application, you do need a fedex.com userid and password to agree to the terms and conditions which is free. Anyone can go in and obtain test credentials and point to a test server simply by changing their url from gatway.fedex.com to gatewaybeta.fedex.com in their wsdl file. * It is set to test by default* If you are **NOT **a programmer, please DONT try to implement the web services app yourself, hire someone to do it for you. You still have to have some programming ability to implement one of these modules.
Quick note, one easy way to tell if you are using a web services module and not a legacy application is by the authentication credentials.
If you connect using only a meter number and account number, then you are most likely using the old api module, if you are required to include a meter number, account number, key and password (not your fedex.com password) into your module, you are most likely connecting to our web services application server at https://gateway.fedex.com:443/web-services
I have not seen many free carts out there that offer a web services solution including Zencart. I am not a programmer but I would urge any knowledgable programmers to look into building a web services app that would work with zencart.
I hope this information has been helpful.
if anyone has any questions about FedEx, i will gladly respond given i have the time to do so, please, no programming questions, although I will be glad to look at xml or tagged input and output transactions either for api or web services applications.
I will not put my email in this forum, but if you respond with your info, i will be glad to try and get in touch with you.
Thanks for your time.
:bigups: