UPS Legacy XML/SOAP Web Services (sunset)

The UPS legacy XML/SOAP web services were sunset on 2024-06-03. They covered the same operations now served by the UPS Developer APIs (Shipping, Rating, Tracking, Address Validation, Time in Transit, Locator), but used XML payloads with credentials embedded directly in the request body and a per-service WSDL. Calls against the legacy endpoints no longer succeed. This page exists because integrators still encounter the legacy endpoints in long-lived codebases, vendor scripts, and ERP plug-ins. The replacement is the UPS Developer APIs surface, which uses REST with JSON and OAuth 2.0 client_credentials. The migration changes more than the transport: rate-response shapes, tracking-event vocabularies, and error codes all evolved during the move. Plan the migration as a contract change, not as an endpoint swap. If an existing integration still references the legacy endpoints, treat that as a sev-2 incident waiting to happen at the next batch run. Schedule a cutover with parallel running against the new REST endpoints, validate label formats and rate parity in the UPS Customer Integration Environment, and only retire the legacy code path after a full reconciliation cycle in production.