Frequently Asked Questions
Find answers to common questions and concerns.
Yes, please view the Best Practices Guide for more details.
FedEx APIs contain functionality that can assist in order entry, customer service and reverse logistics, as well as shipping operations. For a full list of available APIs, see our API Catalog.
Email addresses can have multiple user IDs, but each user ID can only be associated with one organization at a time. You have two options when wanting to join another organization:
1. You can create a new user ID to associate to a new organization.
2. Leave your existing organization by following the instructions below:
- If you're an Administrator: click on Remove beside your name under the Users tab on the Manage Organization page.
- If you're a Contributor or Viewer: navigate to Settings by clicking on your name in the top right-hand corner of the FedEx Developer Portal. Once there, click on Leave Organization.
In order to use FedEx APIs in your product, you must read and accept our Developer Portal License Agreement (DPLA) when creating a project. In addition to the DPLA, your company must execute an End User License Agreement for each shipping account added to your organization.
Sample code in a variety of different programming languages can be found for each API on their corresponding docs page.
Yes. To view more information, please see FedEx API Versioning and Throttling Management.
Yes, you can track up to 30 shipments in a single transaction by using batch tracking.
Yes, there are many ways to accomplish this. Please reach out to Support to find out how.
The label buffer is a Base64 encoded string. You will need to decode the Base64 to see the label buffer in the format you selected in the request.
Unfortunately, no. The quality of a faxed label is below the acceptable evaluation standards. Faxed labels will not be evaluated for approval.
There are four reference fields available: reference, invoice, dept. and PO number. On the test server, FedEx reserves the right to return a fixed value in the reference field. The other three reference fields are available for testing your values.
The introduction of FedEx APIs will not affect existing integrations that are built using FedEx Web Services. However, for future integrations, FedEx Web Services will not support all of the new features. So, we recommend that you adopt FedEx APIs.
There are two levels of assistance available: consultation and general troubleshooting help. Please view the Support page to find out more.
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.
No. We provide our APIs, documentation, sample code and everything else found in the FedEx Developer Portal to businesses and developers for free, subject to terms of use.
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.
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.
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.
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.
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.
No. Since this solution is simply a set of technical schematics for your convenience, there are no revenue requirements.
Yes. We offer a testing environment as well as a production environment.
Depending on the API you are using, you may need to submit your project for Label Certification, or no certification.
Yes. FedEx APIs are a global solution that work well outside of the United States. For availability in your region, please check the Support page.
There are two levels of assistance available - consultation and general troubleshooting help. Please view the Support page to find out more.
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.
If your company is not ready to migrate yet from Web Services and FedEx Ship Manager® Server, you will still have access to the Developer Resource Center.
Don’t see your question here? Contact us.
