FedEx Web Services SOAP API removal
Deprecated, no dateSubscribe to FedEx Web ServicesShare
FedEx has deprecated the FedEx Web Services SOAP API without specifying a permanent shutdown date. Starting July 1, 2026, the service enters maintenance-only support, allowing existing integrations to operate temporarily. After full retirement, calls to these services will fail.
What to use instead of these calls
Migrate to the FedEx REST APIs on apis.fedex.com, such as POST /ship/v1/shipments, POST /rate/v1/rates/quotes, and POST /track/v1/trackingnumbers. Transitioning requires more than updating an identifier, as it involves obtaining new OAuth client credentials from the FedEx Developer Portal and rewriting integrations from SOAP to JSON.
Moving to the REST APIs needs new API credentials from the FedEx Developer Portal and a rewrite from SOAP to JSON.
In FedEx Web Services's words
Migrate to FedEx APIs – Act now to avoid service disruption Key date: Starting July 1, 2026: FedEx Web Services moves to maintenance-only support. Existing Web Services integrations may continue operating temporarily for existing customers
Facts
- API
- FedEx Web Services
ws.fedex.com - Kind
- Removal
- Announced
- January 30, 2026
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against FedEx Web Services's own pages
Questions
When does this change take effect?
FedEx Web Services deprecated the Web Services SOAP API without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: FedEx Web Services has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.