FedEx Web Services are moving to legacy-only status and will no longer be supported from 1 June 2026. All customers currently using the FedEx Web Service connection (product name "FedEx") in nShift TMS are strongly encouraged to migrate to the new "FedEx API" transport product. This article explains what actions you need to take to make sure your FedEx connection continues to work.
Introduction
FedEx will move the current Web Services API to legacy-only status on 1 June 2026. While the service will continue to function after this date, it will operate without vendor support — meaning any disruptions or issues will not be addressed by FedEx. nShift has secured an extension from FedEx covering all nShift customers, providing additional time to complete the migration. Although the current connection is approaching end of support, nShift will support customers throughout the transition to help ensure a smooth migration.
To maintain continued compatibility with FedEx services, nShift has introduced a new transport product called FedEx API, based on FedEx's modern REST API.
Moving to the new product enables:
- Continued access to all FedEx services currently supported
- Compatibility with future FedEx changes
- Improved security and performance
The new REST API is built as a separate transport product in nShift TMS, so you must switch from the old FedEx product to the new FedEx API product.
Exactly what you need to update depends on your setup, but you will always need to:
- Request new credentials
- Create new Transport Agreements
- Update or re-create Consignment Templates
If you have an integration with nShift that uses FedEx-specific references in the input data, you'll need to update the integration to point to the new transport product. If instead you reference a template where the product is preselected, it will in most cases be enough just to change the transport product in the template, with no changes required to the integration itself.
Setup
1. Request Production Credentials
Use your existing FedEx account number and request credentials here:
FedEx Registration Form
After submitting the form, your production credentials will be shown on the final page.
2: Create Transport Agreement
Once you receive your credentials, create new transport agreements for FedEx API and add them accordingly:
For more information on how to create a new Transport Agreement, click here.
Testing
Your own FedEx credentials are not available in nShift’s test environment. For this reason, we recommend that testing is carried out directly in the production environment.
If testing in the test environment is necessary, please contact nShift Support. In certain cases, we may be able to provide test credentials.
FedEx® Electronic Trade Documents (ETD)
How to Upload Letterhead & Signature
- Go to: FedEx Registration Form
- Scroll down and click Next to go to Page 2.
- Click:
MY ACCOUNT IS ACTIVATED ALREADY AND I WOULD LIKE TO UPLOAD LETTERHEAD AND SIGNATURE TO BE USED ON FEDEX GENERATED INVOICES - Enter your FedEx account number and click Verify Account.
- Upload your Letterhead and Signature.
- Save the images.