Help Needed: PA API 429 Error Even After 3 Sales & New Credentials

Question

Hi everyone 👋

I hope you're all doing well!

I'm running into a strange issue with the Amazon Product Advertising API and was hoping someone here might have some insights. I just completed the 3 required qualifying sales, received my API credentials, and tried making my first requests to the API — but I'm consistently getting a 429 Too Many Requests error every single time, even on the very first call.

Here’s what I’ve tried so far:

Used the paapi5-nodejs-sdk-example repo.

Tried the amazon-paapi NPM package.

Attempted to build the request manually using cURL from the official docs:
https://webservices.amazon.com/paapi5/documentation/quick-start/using-curl.html

None of these attempts returned a successful response. I also contacted Amazon support, but they weren’t able to help and referred me here to the forums.

A few more details:
The account is brand new — no previous traffic or usage.

Credentials are fresh — this is literally my first attempt at using the API.

Region is webservices.amazon.com, tag is US-based.

I’ve confirmed my system clock is synced and added a delay to avoid instant throttling.

Has anyone experienced something similar right after getting access to the API?
Is there possibly a delay after hitting the 3-sale threshold before the API fully activates?

Any tips, ideas, or even guesses would be hugely appreciated 🙏
Thanks so much in advance!

re:Post Agent · Answer

The issue you're experiencing with the Amazon Product Advertising API (PA API) is unusual, especially for a new account with fresh credentials. However, there are a few things to consider and potential solutions to try:

1. API Rate Limits: Even for new accounts, the PA API has strict rate limits. Make sure you're not exceeding the allowed number of requests per second. For new accounts, it's recommended to start with a very low request rate, perhaps 1 request every few seconds.

2. Implement Exponential Backoff: To handle potential throttling, implement an exponential backoff strategy in your code. This means if a request fails, wait for a short time before retrying, and double the wait time with each subsequent failure.

3. Verify Credentials: Double-check that you're using the correct Access Key ID, Secret Access Key, and Associate Tag in your API calls. Even a small typo can cause authentication issues.

4. Check Request Formatting: Ensure your API requests are properly formatted according to the PA API documentation. Incorrect parameters or formatting can sometimes result in errors.

5. Activation Delay: While not common, there could potentially be a short delay between qualifying for API access and full activation of your account. If the issue persists, it may be worth waiting 24-48 hours and trying again.

6. Region and Endpoint: Confirm that you're using the correct endpoint for your region. The webservices.amazon.com endpoint is correct for the US marketplace.

7. Time Synchronization: You mentioned syncing your system clock, which is good. Ensure your system time is accurately synced to prevent timestamp-related authentication issues.

8. API Console: Try using the API Console provided by Amazon to test your requests. This can help isolate whether the issue is with your code or with the API access itself.

If none of these solutions work, it may be worth contacting Amazon support again with detailed information about your attempts and the exact error messages you're receiving. They might be able to check if there's an account-specific issue on their end.  
**Sources**  
[Problem with Amazon API | AWS re:Post](https://repost.aws/questions/QUz3WKBBheRMq_AV8LOYCKfQ/problem-with-amazon-api)

Help Needed: PA API 429 Error Even After 3 Sales & New Credentials

Add your answer

Relevant content