Using Web Service Code to Track FEDEX Packages

Environment: Web Services, .NET Web Service; written in VB.NET and Visual Studio 2003


There was a need to track Federal Express Packages for my company from within my application. This Web Service was created with one public ally-accessible function—GetFedexTracking. This function takes two parameters. The first is an internal reference number or a FEDEX tracking number. The second is a string indicating the method of tracking. An XML document with the tracking information—or error information—is the result of this method call.

Things Necessary to Make This Work for You

If you do a search for word CHANGE, you will find four occurrences, including the one in this comment. Simply make the three necessary changes:

  1. Set the FEDEX_ACCOUNT constant to your account number.
  2. Set the FEDEX_URL constant to the URL given to you by FEDEX.
  3. Set the referrer property of the req object to your company name.

Use Restrictions

Feel free to use this as you see fit. All I ask is that if you make any enhancements, please send them to me. I know that this code is not very complex, but it was a pain to figure out because I could find no good samples around on how to do some of the things necessary to accomplish this.


Download source - 11 Kb


  • Please provide me the FedEx URL

    Posted by panda_biswajit on 06/10/2008 02:28pm

    Please provide me the FedEx URL. I have the Fedex account with me but don't know the URL. Thanks Biswajit

  • Fedex?

    Posted by Legacy on 07/11/2003 12:00am

    Originally posted by: Ummite

    Fedex charge a fixed 12.50 for custom, + the normal taxes that apply. They are thief and I suggest you to use another company to ship!

Leave a Comment
  • Your email address will not be published. All fields are required.

Top White Papers and Webcasts

  • On-demand Event Event Date: November 17, 2015 Although enterprise adoption of open source has accelerated, some are still wary of it. But not all open source technologies are the same: some are designed with enterprises in mind. In this webinar, we'll discuss trends in open source development, innovation impacts, and what it means for the future.

  • Moving from an on-premises environment to Office 365 does not remove the need to plan for disruptions or reduce the business risk requirements for protecting email services. If anything, some risks increase with a move to the cloud. Read how to ease the transition every business faces if considering or already migrating to cloud email. This white paper discusses: Setting expectations when migrating to Office 365 Understanding the implications of relying solely on Exchange Online security Necessary archiving …

Most Popular Programming Stories

More for Developers

RSS Feeds

Thanks for your registration, follow us on our social networks to keep up-to-date