USPS Web Tools API platform removal
Stopped workingSubscribe to USPS Web ToolsShare
On January 25, 2026, the USPS Web Tools API platform was retired and service disruptions began. Calls directed to the host secure.shippingapis.com now fail. The retirement affects all requests relying on the legacy Web Tools API platform.
What to use instead of these calls
Migrate to the USPS APIs on apis.usps.com (OAuth 2.0) by mapping each Web Tools API to its equivalent: Addresses v3, Domestic and International Prices v3, Labels v3, Tracking v3r2, or Locations v3. Switching requires more than updating an endpoint, as developers must create a new account, configure OAuth credentials, and set up payment authorization on the USPS Developer Portal for labels.
The USPS APIs need a new account, OAuth credentials and, for labels, a payment authorization on the USPS Developer Portal.
In USPS Web Tools's words
The USPS Web Tools API platform was retired on January 25, 2026 and service disruptions are underway.
Facts
- API
- USPS Web Tools
secure.shippingapis.com - Kind
- Removal
- Takes effect
- January 25, 2026
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against USPS Web Tools's own pages
Questions
When does this change take effect?
Calls to the Web Tools API platform on USPS Web Tools stopped working on January 25, 2026.
What happens to calls after January 25, 2026?
They have failed since January 25, 2026.
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.
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.