FedEx Web Services (SOAP, legacy)

FedEx Web Services is the legacy SOAP and WSDL surface for FedEx Express. Each service (Ship, Rate, Track, Address Validation, Country, Locator) is published as a separate WSDL document, and integrators generate clients per service. Authentication uses a WS-Security-style block carrying API key, password, account number, and meter number directly in the SOAP request body, so credentials must be treated as live secrets that ride with every call. The most operationally important rule with FedEx Web Services is contract observability. Capture a checksum or canonical diff of the live WSDL and any imported schemas, compare it with the version your generated client was built against, and alert when the contract changes outside your planned deployment flow. WSDL drift is the most common root cause of a sudden FedEx SOAP outage that is not actually a code regression on the integrator side. FedEx is directing new integrations to the REST APIs at developer.fedex.com. Web Services still works at this page's last review, but the investment surface is REST. Plan any greenfield integration on REST and treat existing SOAP integrations as maintenance-only — keep the WSDL diff monitor running, keep the generated client up to date with each contract change, and budget a future migration window rather than rebuilding on SOAP.