USPS Web Tools API Retirement Jan 2026

[jaminion]

Hello, we have been receiving notifications from USPS that they are retiring their current Web Tools API platform on Jan 25, 2026. This is similar to how UPS and Fedex have retired their older SOAP-based APIs, such as with issue #37534. This includes the RateV4, IntlRateV2 and TrackV2 APIs which are currently in use by the magento/module-usps package.

They have provided a reference to their "Industry Alert" at https://postalpro.usps.com/mnt/glusterfs/2025-02/INFORMATIONAL%20-%20Web%20Tools%20Retirement%20and%20Migration%20Dates.pdf identifying this.

Documentation for their REST APIs is available at https://developers.usps.com/.

According to https://experienceleague.adobe.com/en/docs/commerce-operations/release/planning/schedule there are two more releases currently planned before this date: August 12th, 2025 and October 14th, 2025. I cannot seem to find any information concerning efforts to update the USPS shipping module to support this new API endpoint, and I have also tried to search for another raised github issues in this project concerning this. I figured this request should go here rather than the feature-requests project because at the end of January 2026 it will become a serious bug for merchants who use the USPS shipping methods.

I am hoping to get some understanding into Adobe/Magento's position on this - if we can expect an update to that module before the impact date and which Magento versions will be supported.

Thank you!

[m2-assistant]

Hi @jaminion. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant]

Hi @engcom-November. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

[hostep]

Looks like Magento internal devs have fixed this in: 963fe57 in scope of AC-13257::Migrate USPS integration from outdated Web Tools APIs to new RESTful USPS APIs

[engcom-November]

Thank You @hostep for the contribution.

Hello @jaminion ,

Thank you for your report and collaboration.

Could you please review the above comment and let us know if you're still experiencing any issues?

Hence we will proceed with closing this ticket.

Thank you once again!