I have a question related with Fed Ex Tracking API. First of all I am using FedEx testing URL and credential which we generate for development. I am not using production creadential and URL. Basically I wanted to know limitation of fed ex testing credential and url. Actually I got a problem and not able to get answer of that problem neither in document nor by googling. I track the shipment via tracking number using fedex tracking web service(using testing URL and credential), Initially they shows the result but after sometime they stopped showing result and I get message in response that tracking number not found but when I used same tracking number on fed ex website then on there it shows the correct result. I don't know why it is behaving like this. Another thing for some tracking number it shows the result and for some it does not show. So anyone guide me in right direction.
Thanks, Awadhendra
If your using your own live/production tracking number in the FedEx test environment note that their testing environment only retains tracking data for a few months. Anything beyond that will return an error that the package information is not available even though you can still track it successfully in production.
Here’s a list of static tracking numbers that can be used in the FedEx test environment:
The above list of tracking numbers will work when pointed to the following server endpoint:
https://wsbeta.fedex.com:443/web-services/track
Note that the only time these numbers will not work is during FedEx's scheduled maintenance windows.
For testing you can use these tracking numbers 111111111111 or 123456789012.
When you use Live Tracking numbers with Testing Credentials, there are some confusions like you said.
Finally I solved this problem. Actually there is no confusion in behaviour of fedex services. Actually I am using specific service which is for ground service only and tracking number which I am using is not for ground service. Thats why I am facing problem. Second thing I am using v9 fedex tracking service, I changed it from v9 to v6 service and it works.
Thanks.