USPS Web Tools API is obsolete

They may have turned off the Web Tools API last night. My rate requests are not getting responses.

They apparently turned Web Tools back on. Watchdog has 200 status on USPS responses since 14 Jan 2025.

It seems easiest to use the Oauth2_client to authenticate integrating the existing Commerce USPS module and adding the new API calls.

Is anyone working on this???

We're using the USPS module in our bookstore, so we're interested in the update as well.

The first issue is Oauth2 authentication. I have installed the Oauth2_client and modified the schema yml file to add the crid and mid needed to get a token, and uspsbase php and one other file. The form did change so I am working on the proper USPS api authorization pages

It appears the API is the same but there is an issue of xml along with the Oauth2 authentication.

USPS lists the deprecated and new calls that can be manually changed.

There is a notice that USPS works with Oauth2 v3 and it appears Drupal 10 Oauth2_client is v4 possibly. Do not know if it is backward compatible if so.

My credentials work as I used that first script to test a flow connection - it connected but threw an error on the code for request

I have not modified the Oauth2 client for the USPS requests in commerce_usps yet because until I get the API information config section working with the four values I have ready to there it matters not. There is also an issue it may use the "key" module.

Once I do that the Oauth2_client will see the client and register it.

Where is the live and test mode urls stored or entrered???

Any ideas and suggestions are welcome

@bobburns asked "Where is the live and test mode urls stored or entrered?"
[site-root]/admin/commerce/config/shipping/methods/usps/edit is where the live url and username are stored, under the form field names "commerce_usps_connection_address" and "commerce_usps_user", respectively.

I don't remember where the test url is.

I just received my biweekly warning from USPS API Communications about their Web Tools platform shutdown in Jan 2026.

If I was capable of programming a new module to replace Commerce USPS, I would, but I just don't know PHP well enough to do that. I've done a few alters, but that's about it.

Is there going to be a 7.x-capable replacement for it with OAuth 2 login in time? It's ok if there won't be; I can develop some conditions in a rule and create our own estimates of customer shipping costs. In time those will get close to actual shipping costs.

If someone were to update Commerce USPS, however, I may be capable of semi-duplicating those to update the Commerce UPS module that has been non-function due to failed OAuth 2 logins since January of this year.

I truly appreciate the work of anyone who has this or is putting this on their plate!

Cheers

@rvhovland -- does it look like the change to the new USPS API (in D10/11) will happen in time? (I won't hold you to it. :-) Feel free to give me odds rather than a yes/no.

I ask because I have a small non-profit still on Drupal and if it's unlikely, I need to prepare my client so they can can change to UPS or Fedex, and this will be a workflow change for them, so I want to give them time to prepare.

I really appreciate that you're working on it. Happy to test or help in any way.

Thanks.

The existing code can be used once authentication is complete to Oauth2. I have completed this step using the Oauth2_client.

A PHP API is not needed in actuality as the new USPS API does both PHP or XML

I went through a challenge to get the first authentication to wotk from USPS.

The existing in API can modified.

You need a usps business account to even get API credentials to request Oauth2 access, so I am not holding my breath this upgrade will get done by the maintainers

Is anyone actually working on this besides me, and I am sorry I cannot share code.

hi, any update on this?

Do I understand correctly, version 8.x-1.8 will stop working Jan 2026 because it is using USPS Web Tools API which is obsolete and this module does not use new USPS Label APIs?

Any progress on the rewrite?

Thank you, rhovland, for taking on this task, and thanks to the Commerce USPS for integration! We are biting our nails in anticipation out here!

rszrama: Any update yet?

Opened a 2.x branch for this as it contains breaking changes.

There's a typo in the MR - USPSRateRequest extends UspsRateRequestInterface, but the actual class is named USPSRateRequestInterface.

it might be useful to add a link to https://developers.usps.com/ in the configuration form.

An amusing detail - https://developers.usps.com is a Drupal site :-)

The setup instructions says you need to create an account on https://cop.usps.com/cop-navigator, which results in an infinite redirect loop.

I downloaded the posted version 2 tar but it didn't have any merge requests in it. Basically a 1.8 version. The git hub version was the same.

I manually applied the changes figuring I could see how the code worked.

I copied my working version 1 and and blinded the info. yml to info__yml and named the directory similarly

Maybe I made an error applying the merges but iti nstalled but accssing the shipping method page it white screened as not working

Also someone hard coded client credentials in the test files

I see it works with factory fles and stansbury oauth plugin, 3 and greater which I have installed

I did not do a composer install because backing out of that is more involved if the modules fails

I will try a composer install but a working tar gz file should exist

I have a proper USPS API credentials account

Is there a tar gz file that is current posted somewhere???

Yesterday USPS is sent additional warning emails to Web Tools API users:

"The USPS Web Tools API platform will be retired on January 25, 2026. To avoid service disruptions, migrate now to the new USPS APIs."

If this module's stable version is not going to be completed by Jan 25, it needs to be marked obsolete.

To facilitate testing, I merged the MR into the 2.x branch.
The latest USPS dev version can be tested.

I downloaded and installed the working uploaded version 2 with the merge requests incorporated.

https://www.drupal.org/project/commerce_usps/issues/3470815#comment-1640...

It seems to be working

The shipping dows not show in the review page, but in the total order it does

I have not tested through Stripe to see if it is adding the full amount for charging yet

The "Account number" does not exist according to the USPS delevoper Documentation - it apparently should be "MID" for Mailer ID, so I used that in the account number place. Account Number can mean three different things depending on if one is a Business or an Individual.

Also I changed the hardcoded client id and secret in the USPSRateRequestTestBase.php file to my own in tests/src/Kernel

Dont know if anything but a true MID would work there.

That is a releif that beats the Janauary 25, 2026 deadline

Great work!!! Elegant code

Thanks for getting the module to this point, it's truly appreciated.

Looking at the module setup it's not clear what should be set for these fields:

• Account type
• Account number
• Customer registration ID

I added a MR with some improvements to the README.md and adds links to the setup form.

I've done some testing with the module and it seems to be working correctly - in "test" mode at least, API requests are returning shipping options for both domestic and international orders. Great work tBKoT!

The checkbox options for filtering the mail classes displayed to customer seems to be missing

Because I have a full USPS EPS business and developer account I am running "live"

Certain mail class options I dont want displayed like "Mefia Mail" etc

Because someone had put a clientid and secret in the Krrnel Test file, test likely will work without a real sccount.

See also my post at https://www.drupal.org/project/commerce_usps/issues/3470815#comment-1640...

Can someone restore the mail class filter options to the shipping methods config page?? - or are they now located elsewhere???

Our client has also asked about being able to filter the list of available rates, similar to #41.

It might be worth marking this issue fixed, tagging a beta release, and then doing separate issues for improvements, maybe add a plan issue to coordinate the list of tasks that need to be completed.

I manually added the merge requests - the filter appears is working properly

Thank you

Will a stable release be available for installation before 25 January? If not, can someone provide a detailed description of what needs to be done to install the needed updates?

Changes are merged. Followup improvements should be made in separate issues.

Will a stable release be available for installation before 25 January? If not, can someone provide a detailed description of what needs to be done to install the needed updates?

I'm thinking of tagging a beta1.

3 days till drop dead. Status for this is FIXED, above states changes are merged, but no release, no beta, not even a recent devel listed yet on project page?

Information describing the 2.x development release can be found here:

https://www.drupal.org/project/commerce_usps/releases/2.x-dev

I just installed it using composer. That process went smoothly. I also had to follow the steps described here to re-create my USPS API credentials:

https://git.drupalcode.org/project/commerce_usps/-/blob/2.x/README.md?re...

You then need to add those credentials to your store's USPS shipping method configuration:

admin/commerce/shipping-methods

I've done some basic testing, and I'm able to retrieve both domestic and international rate information. Thank you! As described above, there's still some work to do in terms of filtering rates that are shown to your customers. For example, if you enable the Priority Mail rates, your customers will see all of the available Priority Mail options (Priority Mail, Priority Mail Flat Rate Envelope, Priority Mail Large Flat Rate APO/FPO/DPO, etc.). That may cause some confusion until we have the ability to be more selective about the specific rates exposed for customer selection. That issue is being tracked.

When I try to create an app I get the message:

| You are currently NOT Enrolled in USPS SHIP Outbound and Returns.Enroll in USPS SHIP to get access to the Shipping Suite API products.

I did not see "Select the APIs Available."

I tried creating the app anyway but it is not working. Is there a step missing somewhere?

It would be helpful to update the project page explaining that only the 2.0 will work after Jan25 and link to dev.

2. Install the dev version of 2.x
This may require you to edit your composer.json file. Change the line
"minimum-stability": "stable"
to
"minimum-stability": "dev"

You shouldn't do this. This sets the default allowed release on all dependencies, so the next time you do "composer update -W" you'll give it permission to install dev versions of everything it wants to, which is a bad idea.

The single "composer require" line is enough to make your site download the dev version.

When you add the module via "composer require 'drupal/commerce_usps:2.x-dev@dev'" the "@dev" part tells Composer to ignore the normal "minimum-stability" setting and install the dev version, it should just work that way.