If your shipping operation touches a FedEx account through any kind of software, whether your ERP, your TMS, an in-house integration, or a marketplace plugin, you have a hard deadline coming. FedEx is deprecating its legacy SOAP/XML API and forcing every account onto its REST API, gated behind multi-factor authentication (MFA). Miss the cutover, and your FedEx labels, rates, and tracking stop working.
This is one of those infrastructure moments that's easy to ignore until it isn't. Below we'll cover what's actually changing, the dates that matter, what shippers need to do, and the harder question every operations leader should be asking right now.
FedEx has been signaling this migration for over a year, but the deadlines are now close enough to matter. Here's what you need to know.
Translation: if you ship with FedEx and your shipping software hasn't already walked you through MFA, the clock is ticking.
FedEx is making this change for two reasons, and both matter for how shippers should think about it.
1. Security. SOAP-era credentials were generated and reused with very little verification, a known weak point. Tying credential issuance to MFA aligns FedEx with modern API security standards and meaningfully reduces account takeover risk. Anyone who's been on the receiving end of a freight invoice fraud incident understands why this is overdue.
2. Performance. The REST API isn't just newer. It's faster and more capable. Shippers who've already migrated report better rate-call latency, cleaner error handling, and access to newer endpoints that the SOAP version never supported. That matters most during peak, when every extra second on a rate quote compounds across thousands of shipments.
The specific steps depend on how you connect to FedEx, but every shipper falls into one of three buckets:
1. You connect to FedEx through a modern, actively maintained shipping platform. Your provider is doing the work. You'll see a prompt, usually in your carrier settings, to upgrade your FedEx connection. You'll enter the address on file with FedEx, pick a verification method, enter the PIN, and you're done. It takes a few minutes per account, and the rest of the work will be handled by your provider.
2. You connect through an ERP-native shipping module or an older TMS. This is the riskiest bucket. Older modules, particularly bolt-on shipping inside legacy ERP installs, may not have a clean MFA upgrade path. Some vendors are still scrambling to release support. If you haven't heard from your shipping software vendor about FedEx MFA by now, that silence is telling.
3. You have a custom or in-house FedEx integration. Your developers will need to implement the FedEx MFA flow against the REST API directly: address validation, OAuth credential exchange, the works. If you have more than 20 FedEx accounts, FedEx offers a bypass flow that reduces the per-account friction. This may be worth asking your FedEx rep about.
In all three cases, the address on every FedEx account must exactly match what's in FedEx's system. The most common error shippers hit isn't technical. It's a typo on a street address or a stale company name that doesn't validate.
Here's the question worth asking while you're already in your carrier settings: if FedEx forcing this migration is creating heartburn for your shipping setup, what happens the next time a major carrier deprecates an API? Or the next time you need real multi-carrier rate shopping, ERP-synced shipment data, or freight invoice auditing?
Carrier API migrations are a forced infrastructure moment. They expose which parts of your shipping stack are being actively maintained and which are quietly aging out. The shippers who handle FedEx MFA in an afternoon are the ones running on platforms that absorb this kind of change for them. The shippers who are scrambling are usually running on something that hasn't kept up, and FedEx won't be the last carrier to force the issue.
If you're already opening up your shipping setup to fix one carrier connection, it's the right moment to ask whether your platform is built to handle the next five.
If you're a current FreightPOP customer, you're in bucket one. We're actively rolling FedEx MFA into the platform and reaching out to customers to walk through the credential upgrade. The work on your end is minimal: verify the address on your FedEx account matches FedEx's records, choose a verification method, enter the PIN we route to you, and your connection is on the REST API. No downtime, no labels going dark, no scramble.
The same goes for new FreightPOP customers spinning up FedEx through us. The MFA flow is built into onboarding. You won't have to think about it.
FedEx is beginning broader SOAP deprecation on May 1, 2026. New FedEx accounts created through shipping platforms have required MFA and the REST API since March 1, 2026. Individual shipping software providers have set their own earlier cutover dates through spring 2026, so the deadline that matters most to you is the one your platform has communicated.
Multi-factor authentication is a one-time verification step FedEx now requires before issuing REST API credentials. You confirm the address on your FedEx account, choose a verification method (SMS, phone call, email, or invoice), and enter a PIN that FedEx sends. Once verified, your shipping platform receives REST-enabled credentials and your FedEx connection keeps working.
Yes. Once SOAP is deprecated, any integration still calling the old API will fail. That means no rate quotes, no label generation, and no tracking updates flowing through that connection until you migrate to the REST API with MFA-validated credentials.
Yes. Each FedEx account number connected to your shipping software must complete its own MFA flow. If you manage more than 20 FedEx accounts, FedEx offers a bypass flow that reduces the per-account friction. Ask your FedEx representative to enable it.
This is the most common failure point. The address on your FedEx account must match FedEx's records exactly, including company name, suite numbers, and ZIP+4. Pull a recent FedEx invoice to confirm what FedEx has on file, update your shipping platform to match, and try again. If the address itself is wrong on FedEx's side, contact FedEx support to correct it before retrying.
Your development team will need to implement the FedEx MFA flow against the REST API directly: address validation, OAuth credential exchange, and PIN verification. FedEx's developer portal has the current API documentation. Budget time for testing. Most teams underestimate how many edge cases the new API surfaces compared to SOAP.
Yes. FedEx MFA is built into the FreightPOP platform. Current customers are being walked through the credential upgrade with no shipping downtime. New customers connect FedEx through our standard onboarding, with MFA handled as part of the flow.
For most shippers, yes. The REST API offers faster rate calls, cleaner error handling, and access to newer FedEx endpoints that SOAP never supported. The performance gain matters most during peak season, when rate-quote latency compounds across high shipment volumes.
The FedEx SOAP deprecation is real, it's coming this year, and it's a hard cutover, not a soft warning. Every shipper should:
FreightPOP supports parcel, LTL, FTL, ocean, rail, and international air shipping across 1,500+ ERP, logistics, marketplace, and carrier integrations, including FedEx on its new REST API, MFA-ready. If you're rethinking your shipping stack in light of this migration, get a free demo and see what a platform built for change looks like.