Yes, I also get the "250002 Invalid Authentication Information" daily
while using the Address Validation API. I've supplied support with all of
my logs / documentation from cURL and QSHONI. The response I received from
support was, "just try again".
Sent: Monday, May 06, 2024 at 3:54 PM
From: "Greg Wilburn" <gwilburn@xxxxxxxxxxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion"
<midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: [EXTERNAL] UPS JSON API Response
I just switched over from the legacy XML API (we only use Street Level
Address Validation).
We are using the OAuth Client Credentials "Create Token" method
(integration owner is the UPS shipper).
So I'm not sure if this is the same...
While I have not received that specific message, we receive another error
every day (usually only one period of time per day).
"250002 Invalid Authentication Information."
Now the access token is supposed to be valid for 4 hours (14399 seconds).
So I store that in a DB file and request a new token when I'm within 5
minutes of the token expiring.
Based on my logs, I know when I would have received a new token at the
beginning of our workday. But this error occurs 2-3 hours later (which
doesn't seem right to me)
I have an open ticket with support... the want the entire post and
response, so I've turned on debug (HTTPAPI) to trap the error.
I'll post what I find if that will help.
Greg
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Michael Fulmer via MIDRANGE-L
Sent: Monday, May 6, 2024 1:47 PM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Cc: Michael Fulmer <mfulmer@xxxxxxx>
Subject: [EXTERNAL] UPS JSON API Response
A couple months ago I completed a Client’s interface with the new UPS JSON
API’s. Everything has been going along nicely until two weeks ago. In
place of the Oauth 2.0 Token response, we sometimes receive a text
response of “upstream request timeout”. Is anyone else receiving this
response? I’ve searched the Midrange Archives and found nothing. No where
in the UPS JSON API Documentation is this response listed. I’ve emailed
the UPS Developer API Support and haven’t gotten an answer. Is this simply
the Oauth Server being overwhelmed by traffic?
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: [1]
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
[2]
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
[CAUTION! This email originated outside of the organization. Please do not
open attachments or click links from an unknown or suspicious origin.]
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: [3]
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at [4]
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
References
Visible links
1.
https://lists.midrange.com/mailman/listinfo/midrange-l
2.
https://archive.midrange.com/midrange-l
3.
https://lists.midrange.com/mailman/listinfo/midrange-l
4.
https://archive.midrange.com/midrange-l
midrange.com
