Scott, Sorry for the delay. Laptop has been down for some maint.
I have done some services that require user/password.
Others require API key. And even one required using API key to get token that expires.
UPS seems to want BOTH user/password and API key.
Just unsure how to send it all.
My code was different ways of trying to accomplish it.
When I try and ask them questions about what they are looking for, they basically say it's standard web development. I tell them I am not using it for a web site, that I am calling it from an IBMi. Their response is "never heard of that".
Maybe if I had some web development experience I would have a clue on what they are asking for.
Once I get the connection I am getting better at sending and parsing the soap/xml/json docs. It's this connection stuff (headers) that I seem to have a harder time with.
And sorry about the copy/paste. Here it is cleaned up.
Header Name Constraint Description
transIdRequired: Yes
Type: Header
Length: 32
An identifier unique to the request
transactionSrcRequired: Yes
Type: Header
Length: 512
Identifies the clients/source application that is calling
AccessLicenseNumberRequired: Yes
Type: Header
Length: 16
Authorization: Access Key obtained through on-boarding process. Contact your UPS representative for additional information.
UsernameRequired: Yes
Type: Header
Length: 16
The customers MyUPS username
PasswordRequired: Yes
Type: Header
Length: 26
The customers MyUPS password
-----Original Message-----
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Scott Klement
Sent: Friday, September 25, 2020 2:58 PM
To: rpg400-l@xxxxxxxxxxxxxxxxxx
Subject: Re: HTTPAPI Headers
Jerry,
It looks like you copy/pasted from a table or something and the formatting was lost in your e-mail, making it very difficult to read. I THINK you're saying you need headers like this?
transId: some-32-char-string
transactionSrc: some-512-char-string
AccessLicenseNumber: some-16-char-string
Username: some-16-char-string
Password: some-26-char-string
Is that correct? I don't understand the code you provided where you are doing something with the Authorization header and some complex expression that I didn't understand. Or http_setAuth. Is that related, or a separate point? Can you explain what you want/need to know about the Authorization header? It seems bizarre to me that they would want both their own custom headers and also the standard one to do the exact same thing.
You also mention web development. Can you explain how web development relates to this?
I'm a bit lost.
-SK
On 9/25/2020 11:54 AM, (WalzCraft) Jerry Forss wrote:
Ok, on to UPS.
This is what they require for headers.
From UPS doc:
Header Name
Constraint
Description
transId
Required: Yes
Type: Header
Length: 32
An identifier unique to the request
transactionSrc
Required: Yes
Type: Header
Length: 512
Identifies the clients/source application that is calling
AccessLicenseNumber
Required: Yes
Type: Header
Length: 16
Authorization: Access Key obtained through on-boarding process. Contact your UPS representative for additional information.
Username
Required: Yes
Type: Header
Length: 16
The customers MyUPS username
Password
Required: Yes
Type: Header
Length: 26
The customers MyUPS password
What is the magic decoder values to use?
(Rc = http_xproc(HTTP_POINT_ADDL_HEADER : %paddr(SetHeader)); (Headers
= 'Authorization: Basic ' + %Trim(UPSUserName + %Trim(UPSPassword)) + CRLF +
'AccessLicenseNumber: ' + %Trim(APIKey) + CRLF
) vs http_setAuth( HTTP_AUTH_BASIC
: %Trim(UPSUserName)
: %Trim(UPSPassword));
I have the access key, username and password. I keep trying different combos without success.
Wish I had the time needed to really understand HTTP header. Maybe in the cold, dark winter that is a coming.
Web development is not my thing. Just trying to get access to different services.
Subject to Change Notice:
WalzCraft reserves the right to improve designs, and to change specifications without notice.
Confidentiality Notice:
This message and any attachments may contain confidential and privileged information that is protected by law. The information contained herein is transmitted for the sole use of the intended recipient(s) and should "only" pertain to "WalzCraft" company matters. If you are not the intended recipient or designated agent of the recipient of such information, you are hereby notified that any use, dissemination, copying or retention of this email or the information contained herein is strictly prohibited and may subject you to penalties under federal and/or state law. If you received this email in error, please notify the sender immediately and permanently delete this email. Thank You
WalzCraft PO Box 1748 La Crosse, WI, 54602-1748
www.walzcraft.com<
http://www.walzcraft.com> Phone: 1-800-237-1326
midrange.com
