Re: QSYS2.HTTP_GET problem with the USPS APIs -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: QSYS2.HTTP_GET problem with the USPS APIs
From: Jack Woehr <jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Mon, 3 Jan 2022 13:05:55 -0700
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

On Mon, Jan 3, 2022 at 1:01 PM Peter Dow <petercdow@xxxxxxxxx> wrote:

Hi Jack,

You need a valid USERID. "The USERID is correct, just XXXed out here."

True but possibly not germane, methinks, Peter ...

When I try with the ?API=Verify&XML url_encoded I get an XML error.
When I try with them concat'ed in plaintext and url_encoding the rest of
the request, that's when I get the auth error

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: QSYS2.HTTP_GET problem with the USPS APIs , Brad Stone
Re: QSYS2.HTTP_GET problem with the USPS APIs , Peter Dow

This mailing list archive is Copyright 1997-2024 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.