AuthorizerConfigurationException from getOrders (Vendor Direct Fulfillment Orders API) #514
Unanswered
virtutemdave
asked this question in
Q&A
Replies: 2 comments
-
I don't think that's causing the issue, it works fine for all other endpoints and is intended (accounts for all possible parameter name-styles/casing, Amazon ignores the others). Can you share how you're creating the rdt? Any errors there? |
Beta Was this translation helpful? Give feedback.
0 replies
-
I'm calling the Tokens endpoint to get the RDT. Here's the code for that. I'm sending the real LWA Client Id in my code.
I do not get any errors from this call and do get an RDT. Thanks, |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm calling the Vendor Direct Fulfillment Orders API getOrders endpoint (/vendor/directFulfillment/orders/v1/purchaseOrders). This requires a Restricted Data Token (RDT). I am able to get the RDT, but when I call getOrders I get an AuthorizerConfigurationException. When I was debugging, I noticed that the URL created added multiple marketplaceId parameters. They all had the same value, ATVPDKIKX0DER for the US. Do you think that would cause this issue?
This is the generated URL:
TIA,
David
Beta Was this translation helpful? Give feedback.
All reactions