We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Hello
I am facing an issue with this code
credentials = { refresh_token: ENV['AWS_REFRESH_TOKEN'], client_id: ENV['AWS_CLIENT_ID'], client_secret: ENV['AWS_CLIENT_SECRET'], aws_access_key_id: ENV['AWS_ACCESS_KEY_ID'], aws_secret_access_key: ENV['AWS_SECRET_ACCESS_KEY'], region: 'na', } # get the orders client = MuffinMan::Orders::V0.new(credentials, sandbox=true) response = client.get_orders([ENV['AWS_MARKETPLACE_ID']]) pp JSON.parse(response.body)
The 403 error: (notice the first successful OAuth call)
ETHON: performed EASY effective_url=https://api.amazon.com/auth/o2/token response_code=200 return_code=ok total_time=0.148155 ┃ ETHON: performed EASY effective_url=https://sandbox.sellingpartnerapi-na.amazon.com/orders/v0/orders?MarketplaceIds%5B0%5D=ATVPDKIKX0DER response_code=403 return_code=ok total_time=0.555431 ┃ {"errors"=> ┃ [{"message"=>"Access to requested resource is denied.", ┃ "code"=>"Unauthorized", ┃ "details"=>""}]}
I would highly appreciate any help or guidance, thanks a lot in advance!
The text was updated successfully, but these errors were encountered:
@tarekrahme apologies for a delayed response. My initial guess is that you likely need to provide sts_iam_role_arn
sts_iam_role_arn
https://developer-docs.amazon.com/sp-api/docs/tutorial-convert-a-public-amazon-mws-application-into-a-selling-partner-api-application#step-2-create-and-configure-iam-resources
Sorry, something went wrong.
No branches or pull requests
Hello
I am facing an issue with this code
The 403 error: (notice the first successful OAuth call)
I would highly appreciate any help or guidance, thanks a lot in advance!
The text was updated successfully, but these errors were encountered: