About a year ago I setup calls to different AWS, I am now trying to get it working again by simply setting up a new key. The issue is that I keep getting 'Access to X denied.' and I'm not too sure what else I can do in terms of troubleshooting.
At the moment I am trying to access the GetReports API, and I get the following error:
Caught Exception: Access to Reports.RequestReport is denied
Response Status Code: 401
Error Code: AccessDenied
I have deleted the existing keys on email address B and created new ones.
I have tried a different API call.
I have checked all of the other config information (e.g. Merchant ID and Marketplace Token).
Following the steps from Amazon's documentation I attempted to authorize my developer account, which was met with the following error:
This Developer Account Number XXXXXXXXXXXX is not valid for the GB marketplace. Please make sure you are registering on the correct Amazon MWS site. If you are registering on the correct Amazon MWS site, please contact the developer you are attempting to authorise in order to obtain a valid Developer Account Number from Amazon MWS for any marketplace in the EU region. For more information, see “Registering to use Amazon MWS” in the Amazon MWS Developer Guide.
As far as I can see, the developer account is setup for the GB marketplace, and the last time I used this account it all worked fine and I have no reason to believe anything has changed.
What else can I try, what else could be wrong?
When logged in to Seller Central, you need to go to Apps & Services dropdown and select Develop Apps, from here you'll need to add a new app and fill out the form.
It can take up to 30 days for Amazon to process your request, but this will give you access to the MWS calls, once it has gone through you'll need to use the Access Key and Client Secret details listed in Developer Central under "My Developer Information" when making your MWS requests.
You'll also find your Developer ID here that you will be able to authorise using the process you mentioned in your question, once the app is authorised you shouldn't get the error you were previously getting.