I put code in to trap the debug - the error didn't occur at all yesterday (or thus far today).
I would not be happy "trying again" if I were generating shipping labels. Let's just have someone stand there waiting until the UPS API decides to answer (SMH).
Googled the error... this appears to be a common issue with the API.
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Michael Fulmer via MIDRANGE-L
Sent: Monday, May 6, 2024 4:27 PM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Cc: Michael Fulmer <mfulmer@xxxxxxx>
Subject: Re: RE: [EXTERNAL] UPS JSON API Response
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".
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.