Frequently asked questions
FREQUENTLY ASKED QUESTIONS
Find answers to common questions and concerns.
A. An API is just the gateway between your current business application and the FedEx logistic solutions that power the global FedEx enterprise. You can make use of this gateway to pull new information from these FedEx solutions into your own applications. To know more about APIs, please see the "What is an API?" page.
A. Your application communicates with FedEx processing systems by sending requests over the internet and, in return, receives real-time information that can be presented to your customers in a unified manner.
A. FedEx APIs contain functionality that can assist in order entry, customer service, reverse logistics and billing, as well as shipping operations. As an example affecting order entry, the address verification transaction can be used within a shopping cart or by phone-based personnel to verify the Ship-To Address in order to avoid address correction charges. This capability is completely separate from the act of shipping and can prevent mistakes that harm the customer's perception of your business. Discover APIs like Address Validation, Rate, Track, etc. in our API Catalog.
A. It depends on multiple factors, such as: How many functionalities will be implemented? How many programmers are assigned? Where does the FedEx integration project fall on your priority list? Are your programmers already fluent in implementing FedEx APIs? It can take as little as a few weeks to several months, depending on the factors above..
A. No, FedEx APIs are a set of technical schematics provided to a customer in conjunction with documentation and examples, from which the customer’s IT resources can incorporate numerous FedEx functionalities into their internal systems. For off-the-shelf solutions, see FedEx® Compatible.
A. Unfortunately, no. Since the programming is being done on a customer's internal systems and not FedEx-provided hardware, programming support is not an option. FedEx can provide assistance in the understanding of the FedEx API documentation, error messages, examples, etc.
A. No. Since this solution is simply a set of technical schematics for your convenience, there are no revenue requirements.
A. Yes. We offer a testing environment as well as a production environment.
A: Depending on the API you are using, you may need to submit your project for Basic Certification, Label Certification, or no certification.
A: FedEx Web Services encompass the systems that followed SOAP WSDL standards to communicate with FedEx processing systems. FedEx has elected to base future integrations on these new REST APIs to improve reliability and performance. For more information on the differences and to learn why you should migrate, please see the Why Migrate page.
Don't see your question here? Contact us.