RE: Amazon Selling Partner API (SP-API) -- RPG400-L

So I'm not too proud to admit that the whole "github and yum" are over my head. So I wouldn't know where to start. I guess it's just one of those things you have to "do" to understand.

Having said that, I already have the HMAC MD5 "signing" implemented with the legacy Amazon MWS API. I was hoping that I can simply modify my current service program to use SHA256 instead of MD5.

IMHO the most difficult part is understanding what to sign and the process of refreshing the restricted data tokens. Amazon doesn't go into the nitty gritty details - I think they assume you'll use an SDK to do it for you.

-----Original Message-----
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of mihael
Sent: Monday, July 4, 2022 4:11 AM
To: RPG programming on IBM i <rpg400-l@xxxxxxxxxxxxxxxxxx>
Subject: [EXTERNAL] Aw: R: Amazon Selling Partner API (SP-API)

As it seems that Amazon uses HMAC SHA256 this can be done with RPG and some system API calls. The JWT service program of the ILEastic project uses that combo to sign the Json Web Tokens. The source is available at GitHub.

Am 04.07.2022 um 08:46, john art <jhon_art@xxxxxxxxxxx> schrieb:

Hi all
as also me, i'm interested to amazon services, i would have this question : i know well RPG but not java or Node Js; do you think i need help of some people that are expert in java or Node js or only with RPG i could be in success to use this services ?
Thanks
________________________________
Da: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> per conto di Brad Stone <bvstone@xxxxxxxxx>
Inviato: venerdì 1 luglio 2022 16:15
A: RPG programming on IBM i <rpg400-l@xxxxxxxxxxxxxxxxxx>
Oggetto: Re: Amazon Selling Partner API (SP-API)

I would suggest if you have to learn something new and use an SDK from
Amazon to find one you're most comfortable with. I would prefer a Node.js
SDK if that's available. I think that's more popular than Java these days.

On Fri, Jul 1, 2022 at 8:36 AM Greg Wilburn <
gwilburn@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

So I jumped into the new Amazon Selling Partner API (SP-API)
documentation. This API replaces the MWS (Marketplace Web Services) that
will be obsolete by the end of 2022.

When I did the MWS stuff back in 2016, I had a LOT of help with "signing"
the requests. This was the absolute most difficult part of the whole
thing. The new SP-API also requires a "signature" using "AWS4-HMAC-SHA256"
(AWS Signature Version 4). The old MWS used MD5 and added the signature to
the query string. With SP-API the signature is added to the header of each
request.

https://developer-docs.amazon.com/sp-api/docs/connecting-to-the-selling-partner-api#step-3-add-headers-to-the-uri

What's even more complicated is having to request a restricted data token
for each type of request that access PII (i.e. a shipping address). In
other words, if you're listing orders you need one. Then when you list
items you need another (or at least that's how I understand it).

So what I'm getting at is this... I'm wondering how difficult it would be
(or even if its possible) to use one of the Java SDK's to handle all this
for me (calling within RPG). I have never really done anything like that
before. I don't know Java, or really any language other than RPG.

What are your thoughts?
Should I just take my old code and modify it for the new requirements?
Or, should I try to do this with a Java SDK?

Better yet, has anyone already figured this out?

TIA,
Greg
[Logo]<https://www.totalbizfulfillment.com/> Greg Wilburn
Director of IT
301.895.3792 ext. 1231
301.895.3895 direct
gwilburn@xxxxxxxxxxxxxxxxxxxxxxx<mailto:gwilburn@xxxxxxxxxxxxxxxxxxxxxxx>
1 Corporate Dr
Grantsville, MD 21536
www.totalbizfulfillment.com<http://www.totalbizfulfillment.com><http://www.totalbizfulfillment.com<http://www.totalbizfulfillment.com>>
--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com
--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com

--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com
[CAUTION! This email originated outside of the organization. Please do not open attachments or click links from an unknown or suspicious origin.]