I'm one of the old ASP folks.

Vince, would it be better to wait until there is a full fix to update our installation for that oAuth fix, or is the current oAuth fix all that we need to get back up and running now?

- Graham Slaughter

Will do, Vince.

Marshall
CENLYT Productions - ms designs
Affordable Web Design
Custom Ecommerce Designs
Responsive Websites
Cenlyt.com

Apologies if this isn’t helpful, but I ran the XML rate request that ServeLink support shared with us through GPT, and here’s its analysis:

===========

That trace indicates UPS is throttling the legacy XML Rate API call at the edge (Akamai) with error 10429 / HTTP 429.

It’s not an OAuth-token call — this is the old ups.app/xml/Rate endpoint on onlinetools.ups.com.

Given UPS’s 2024 migration to OAuth2/REST and its per-minute “spike arrest” limits, it appears the XML path is now rate-limited (or effectively retired) for your account or IP, so even a single request can trigger the 429 if the quota bucket is already exhausted.

Evidence from the curl trace:

Host & path: onlinetools.ups.com #8594; POST /ups.app/xml/Rate (legacy XML).

Response: HTTP/1.1 429 with errorcode: 10429.

Headers: repeated ak-grn-1 values, which identify Akamai edge throttling.

If accurate, this could explain why every UPS rate request is failing, even for a single customer query.

===========

ETA: I enabled XML debug emails for our site using $debugxmlemails=TRUE;, ran the results by GPT again, and it says:

===========

Yes. This is the same failure mode.

Facts from your debug:

It’s a legacy XML call (AccessRequest + RatingServiceSelectionRequest using AccessLicenseNumber/UserId/Password).

The response body contains ErrorCode 10429 / “Too Many Requests.”

That matches UPS throttling the XML Rating API (not an OAuth token call).

What this implies

You’re still hitting the old ups.app/xml/Rate workflow. UPS has moved developers to REST + OAuth2 and enforces per-minute spike limits; XML calls are now very prone to 429/10429 even on a single visible request if the quota bucket is already empty (e.g., shared IP/credentials or background calls).

===========

Hi All
From the first reports of this I really got the idea that this was mainly the new oAuth integration that was being hit, but that the old API was affected as well. I came here to mention that but I see that Pauld via Servelink is saying the same thing. If you contact UPS directly they can give you an extension. If they help you with the onboarding for the new oAuth system this won't work unless it is approved for Rating (and tracking too if you need that) and not just for oAuth. The steps in the ECT Admin are as follows...

quote:

---

Create a UPS Developer account by clicking here https://developer.ups.com/.
On the UPS Developer home page, click on "Create an Application"
Click on "Add App".
In answer to: "I need API credentials because " - "I want to integrate UPS technology into my business".
Select your UPS account that you want to link to this App.
Fill out your contact details.
Give the App a name, such as "ECTRatesApp".
"Authorization ( O Auth)" should already be selected, and you need to add, "Rating" and "Tracking" to the products included in the App by clicking the "+" sign. Then click "Save".
Enter your Client ID and Secret here in this admin page along with your UPS Account Number.

---

Vince

Click Here for Shopping Cart Software
Click Here to sign up for our newsletter
Click Here for the latest updater

This is from Marshall for how to select the Rating and Tracking...

quote:

---

Actually there is a “Select Category” screen on the page in an iframe, no plus sign. You have to type in the category search “ratings” then activate that, then type in “tracking” and active that and click save. It was approved in like 10 seconds and the site is now returning shipping information.

---

Thanks Marshall !!

Vince

Click Here for Shopping Cart Software
Click Here to sign up for our newsletter
Click Here for the latest updater

Thanks for this fix, Vince.

Configuring UPS API credentials per Vince's directions did restore UPS rates on our site, though for some reason our rates appear to be higher than in the past.

To match the rates we pay through PayPal / ShipStation it looks like we'll need something like $discountshippingups=-50; in our includes.php file.

Here's the setup screen from developer.ups.com that worked for us:

You're welcome, but a big THANK YOU VINCE is definitely warranted here.

Marshall
CENLYT Productions - ms designs
Affordable Web Design
Custom Ecommerce Designs
Responsive Websites
Cenlyt.com

I don't understand where to "Enter your Client ID and Secret here in this admin page along with your UPS Account Number."


Larry

Hi Larry, you need to go to the UPS developer page and follow the steps Vince posted.

quote:

---

Create a UPS Developer account by clicking here https://developer.ups.com/.
On the UPS Developer home page, click on "Create an Application"
Click on "Add App".
In answer to: "I need API credentials because " - "I want to integrate UPS technology into my business".
Select your UPS account that you want to link to this App.
Fill out your contact details.
Give the App a name, such as "ECTRatesApp".
"Authorization ( O Auth)" should already be selected, and you need to add, "Rating" and "Tracking" to the products included in the App by searching the various API's (use the slider to turn on rating and tracking). Then click "Save".
Enter your Client ID and Secret here in this admin page along with your UPS Account Number.

---

When you are done, you will get two alphanumerical fiels
there is a "copy to clipboard" button.
The first one copy into the rate code field
the second one copy into the password field.
the shipper number is your 6 digit UPS account number
access key - leave empty

That should take care of it.

Thanks,
David