I recently got access to the Amazon Product API, and I was trying to experiment with some requests both on my Node.JS environment and on ScratchPad.
But all my requests come back as Error 429 - Too many requests. So far, I haven't been able to make any successful requests using the API.
Has anyone had this issue before? How can I solve this?
I had this error message when trying to access the API via the python SDK. I figured out that besides acces_key, secret_key, and partner_tag I needed to set host, region, and marketplace to the country-specific values according to https://webservices.amazon.com/paapi5/documentation/common-request-parameters.html#host-and-region.
While this seems obvious in retrospective, the error message 429 "too many requests" does not really hint to fix that.
Related
We recently signed up for the tool Oribi. For some reason the Oribi platform is returning the following error and can't connect to our Analytics accounts via the API.
Forbidden: status 403 reading GoogleClient#getWebPropertyProfiles
We've been trying to solve this for weeks now and got the following message from them today - any advice or possible solutions to explore?
While the error we receive from Google indicates that there are insufficient permissions to access the Properties, when looking at your account, everything seems to be properly set.
The next step would be reaching out to Google to inquire about this.
While we won't be able to do this on your behalf, I'll be happy to assist with providing all the relevant information to make sure everything is clear so they can take a look into it.
The situation is as follows: When sending Google the API request to connect the Web Property, the following error is thrown back: Forbidden: status 403 reading GoogleClient#getWebPropertyProfiles.
The user connected to Google has Admin permissions on the account.
I am using scratchpad to explore this api. I am able to use item search and item lookup however I have not been able to successfully use cartCreate a single time. I am getting this error:-
Do i need to ask for a special permission to use cartCreate ?
Error! RequestThrottled
HTTP Status 503: Service Unavailable
AWS Access Key ID: __my_key___. You are submitting requests too quickly. Please retry your requests at a slower rate.
PS: So far I have only generated few sales from my affiliate account and signed up for this api. Could that be a reason for this throttling? Is there any developer account which is not subject to such throttling so that I can continue with the exploratory work.
Thanks
CartCreate has been removed in the new API version. Instead, you have to create your own Add To Cart link or form:
https://webservices.amazon.com/paapi5/documentation/add-to-cart-form.html
In general, you'll want to minimize the number of requests you're making, as it's very easy to bump up against those throttling limits.
Source : https://forums.aws.amazon.com/thread.jspa?threadID=318920
I had exactly the same problem :
I think you explore scratchpad from
https://webservices.amazon.fr/scratchpad/index.html#
with is the old API version
With your account (and mine) I get a disturbing error message : HTTP Status 503
You should use the new scratchpad version for the API 5 of Amazon Product Advertising :
https://webservices.amazon.com/paapi5/scratchpad/index.html
Make the same request, and you should see all is ok
I am using ExactOnline API to fetch the transactions, my API is working fine, but suddenly the Error 403: Forbidden - The division is blocked error occurs and API return the empty result.
Please help.
Thanks.
An HTTP 403 with reason "The division is blocked" typically means the administration is temporarily blocked by a process that needs exclusive access to the administration. Examples are:
One of the company's users is creating or restoring a backup of the administration.
Exact is moving the administration to a different database. (After office hours; users are notified in advance through Exact Online's workflow system.)
API clients should be able to handle this situation. The typical solution is to try again at a later time.
You can find a full list of response codes here:
https://support.exactonline.com/community/s/knowledge-base#All-All-DNO-Content-respcodeserrorhandling
I am trying to use the Amazon Product Advertising API. I have successfully used it before, but the Wordpress plugin I was using has stopped retrieving Amazon information, and seems to think my credentials are not valid.
I created a new Access Key / Secret Key pair (root, not IAM), but it still did not work.
I tried using the Amazon Product Advertising API Scratchpad with these new credentials, but no matter what I try I get an error "MethodNotAllowed".
I have a suspicion that my credentials are not valid, or that I've lost access to the product advertising API for some reason. However, when I try to sign-up again for Product Advertising API, I get told I've already got access.
I can't find any error messages or warnings in my AWS account.
I'm stumped. Any suggestions greatly appreciated.
Well each API request to Amazon Product API requires a new signature. Here are the steps for calculating the signature for an API request: http://docs.aws.amazon.com/AWSECommerceService/latest/DG/rest-signature.html#rest-signature-examples
I'm seeing a 403 "Access to the webpage was denied" error on one specific file being accessed via the Drive SDK. It was working earlier, the app permissions are set correctly, and we're having success with other files using different tokens against the same app.
We're getting the downloadUrl from the SDK successfully, then seeing the error message only after users are redirected to the downloadUrl. Because of that it's hard to track, but we've confirmed that it's working for some, but not for others — it hasn't fully stopped.
The full error text is:
Access to the webpage was denied
You are not authorized to access the webpage at [...] You may need to sign in.
HTTP Error 403 (Forbidden): The server refused to fulfill the request.
We're including the GET download and (valid) access_token parameters, all that.
My question is this: could this be related to the reported Google Drive outage that's currently happening, or is there some sort of throttle/limit to access of a single file over the drive API? I've never seen this behavior before, and this response isn't listed among the standard 403 responses.
I have just seen something similar. I was using a freshly acquired access token, so I don't think it's oauth related. My working theory is that the downloadUrl link was stale. When I got fresh meta data, which had a different value in downloadUrl, it worked using the same access token that had previously failed.
This is only a theory since it isn't documented anywhere, and I would actually expect 410 (or even 301) as a much more appropriate status than 403.