429 Too Many Requests – Amazon API Error Code

What does this error code mean and what can I do to fix it?

Here is exactly what the error code looks like, the way Amazon reports it…

Error calling PA-API 5.0!
HTTP Status Code: 429
Error Message: [429] Client error: `POST https://webservices.amazon.com/paapi5/searchitems` resulted in a `429 Too Many Requests` response:
{“__type”:”com.amazon.paapi5#TooManyRequestsException”,”Errors”:[{“Code”:”TooManyRequests”,”Message”:”The request was de (truncated…)

Error Type: TooManyRequests
Error Message: The request was denied due to request throttling. Please verify the number of requests made per second to the Amazon Product Advertising API.

Ever since Amazon shut down the old version of their API (version 4) on October 31, 2019 and made everybody switch to the new API 5 – we’ve gotten countless support requests here at AmaLinks Pro because our users keep getting this error message when trying to test their API connection or when trying to use AmaLinks Pro to search for products to promote.

AmaLinks Pro is NOT causing the Too Many Requests Error!!

When AmaLinks Pro tries to make a call to the API – we make one single request each time. We’ve checked and double-checked and triple-checked our code. AmaLinks Pro is absolutely not making more than one request at a time (or per second) from our user interface.

With that being said… we did have a few minor glitches and bugs in older versions of the plugin that were released right around October 31, 2019. If you are using AmaLinks Pro – please make sure you always update the plugin to its latest version! Any conflicts we had with other plugins or minor glitches or bugs have all been fixed.

To be honest… for about a week after Amazon shut down API 4 and we started using API 5 – we, ourselves, were getting this 429 Too Many Requests error across several of our sites when trying to use AmaLinks Pro to connect to the API. The only workaround that we could figure out was to keep trying our request over and over again until it worked. In most cases, it would work on the 2nd or 3rd try. But other times we’ve had to try up to 12 times before we could get our API connection to work and have it complete our product search.

I will say this… that issue only lasted for us for about a week. We aren’t experiencing it at all on our end anymore and we haven’t changed a thing. Our only guess is that Amazon must have fixed whatever the issue was on their end somehow. But this doesn’t explain why some of our customers are still getting the error message.

The request was denied due to request throttling

Request throttling – this is a significant clue within that error message from Amazon. Perhaps some users are getting this error message because their accounts have been throttled (or limited) for whatever reason. The only thing we can tell you to do at this point is to contact Amazon Associates support and ask them why you are getting this error message. You could try that if you want. Or you could just keep reading this post…

Amazon Associates Support regarding the 429 Too Many Requests error

If you were to contact Amazon Associates support, you might get an answer from them like the following…

Hello [Your Name],

This is [Rep Name] with Amazon Associates Program.

Efficiency Guidelines in the Product Advertising API are designed to promote efficient use of the API.

Given your current Associate revenue, we don’t have resources to grant additional limits to your account.

In order to be more efficient in calling the API, we recommend that you cache the data returned by the API in accordance to the Product Advertising API License Agreement, visit the Usage Requirements section of our Product Advertising API License Agreement at:


If your application is trying to submit requests that exceed the maximum request limit for your account, you may receive error messages from Product Advertising API.

You can verify your sales are being attributed to your calls to the Product Advertising API by checking for the following:

– You’re using the only links provided by the API when linking back to Amazon.
– You’re passing your Associate tag in all your requests to the API.
– Your Associate Account and Product Advertising API account are using the same Amazon Account (or email).

In order to be more efficient in calling the API, we recommend you cache the data returned by the API in accordance to the Product Advertising API License Agreement. More info:


We look forward to seeing you again soon.

We’d appreciate your feedback. Please use the buttons below to vote about your experience today.

Best regards,
[Rep Name].

So, what is the problem, exactly?

We’re really not sure. It seems like the error could be resulting from API restrictions or throttling – meaning Amazon isn’t giving access to affiliates whose accounts aren’t producing enough sales or revenue. But, we’ve had customers tell us that they are getting this error message despite having plenty of sales and thousands of dollars worth of revenue each month.

Are your Amazon affiliate links actually being attributed to the API?

This might be it right here! Amazon wants to restrict access to the API only to users who are making sales that are attributed to API links. So, how can you tell if your sales are being attributed to the API? It’s quite simple actually. Here’s how to find that report…

  • login to your Amazon Associates account
  • in the ‘Summary for This Month’ box (on the right), click the link on the bottom that says ‘View Full Report’
  • in the timeframe dropdown menu – set it to display the Last 30 Days
  • the 2nd box (below the earnings Report) has 3 tabs – ‘Ordered Items’ is selected by default – click on the ‘Link Type Performance’ tab
  • check to see if you have Clicks and Conversions that are being attributed to the PA-API (as shown below)

This is just one thing to check. Depending on what you find here – we suggest that you contact Amazon Associates support if you are continuously getting the 429 Too Many Requests error.

Troubleshooting Applications

Like I stated above… we use AmaLinks Pro continuously and so do hundreds and hundreds of our customers and most of us are no longer getting this error. The error must be attributed to specific accounts only, for whatever reason.

If you are an AmaLinks Pro user, you shouldn’t have to worry about most of the troubleshooting steps that Amazon suggests. We’ve already taken care of that for you. But if you do want to dig into it some more on your own – here is a link to official documentation from Amazon with suggestions and tips for troubleshooting…


So, what do I do if I’ve lost access to the API?

Well, I’m glad you asked! We actually have a solution for you that involves AmaLinks Pro! But this post is long enough… so we’ve written an entirely separate post on exactly what you should do if you lose access to the Amazon API.

We sincerely hope this helps somewhat clarifies for you one of the confusing errors associated with the Amazon API. Good luck getting your account straightened out and we’ll see you soon inside of AmaLinks Pro!

Explore All Features & Benefits


Sales Questions?

  • For all product support, please contact support

For Support, Click Here

(more links in the footer)