Your product boxes are empty. Prices have vanished, images won’t load, and your logs show the same line again and again: 403, AssociateNotEligible.
In most cases it’s temporary. Amazon has paused API access for your Associates account because your recent sales dropped below its threshold, and access comes back on its own once you’re over it again. The real question is how long you can afford to wait. That decides which of the fixes below you need.
Below you’ll find what the error means, how to confirm the cause in a few minutes, how to get access restored, and how to keep your site showing product data while you wait.
What the AssociateNotEligible error looks like
If you’re on the Creators API, the response body looks like this:
{
"message": "Your account does not currently meet the eligibility requirements.",
"reason": "AssociateNotEligible",
"type": "AccessDeniedException"
}
Older PA-API 5.0 integrations got the same error in a slightly different shape:
{
"Code": "AssociateNotEligible",
"Message": "Your account does not currently meet the eligibility requirements to access the Product Advertising API."
}
Both arrive with HTTP status 403. On forums you’ll also see it written as “associate not eligible,” but in the response it’s always one word.
What the AssociateNotEligible error means
403 is the HTTP status code for Forbidden. Amazon received your request and refused it, and AssociateNotEligible is the reason: the Associates account behind your API credentials doesn’t qualify for API access right now.
Developers started reporting the error in large numbers in November 2025, when Amazon began enforcing a much stricter sales rule. That rule carried over when Amazon replaced PA-API 5.0 with the Creators API in 2026. You now need at least 10 qualifying sales in the past 30 days. Fall below that and access is switched off until you’re back over it.
Your credentials still exist, and your code is probably fine. The account just isn’t eligible at the moment.
Why you’re seeing it even though you had sales
Most people who hit the error were sure they had enough sales. Three details usually explain the gap.
1. The 30 days roll forward every day
The window isn’t a calendar month. A site that averages 15 sales a month can still drop out after one slow week, like the lull after the holidays.
2. Only shipped items count
Amazon hasn’t published a full definition, but developers widely report that the threshold tracks items shipped rather than clicks or orders placed. Cancelled and returned orders don’t help, and an order placed today may not count until it ships.
3. Small and new sites rarely reach 10
A young niche site, or a tool that uses Amazon data without sending many buyers to Amazon, may never reach 10 in a month. If that’s you, waiting a few days won’t clear the error, and the fallback section below is the part to read.
How to fix the AssociateNotEligible error
1. Confirm it’s this error
Plenty of apps log only the status code, and Amazon returns 403 for several different problems. Log the full response body and check the reason or message text against the table below. The type field alone won’t tell you, because a Creators API AssociateNotEligible error is also labeled AccessDeniedException.
| What the response says | What it means | What to do |
|---|---|---|
| AssociateNotEligible | Fewer than 10 qualifying sales in the last 30 days, or another eligibility problem (see step 5) | Carry on with step 2 |
| “Product Advertising API is deprecated” | Your code still calls the retired PA-API 5.0 | Move to the Creators API with Amazon’s migration guide |
| Authorization errors right after you created new credentials | New credentials can take time to activate | Wait before regenerating them |
| Errors on one marketplace only | Credentials are issued per region (North America, Europe, Far East) | Use the credential set for that marketplace’s region |
2. Count your shipped items for the last 30 days
Sign in to Associates Central and open Reports. Set the date range to the last 30 days and look at items shipped, not items ordered. Under 10 means you’ve found the cause.
3. Get back over 10 qualifying sales
Start with the pages that already get traffic. Adding affiliate links to popular posts that don’t have any yet is usually the fastest win. After that, a roundup email of your best-converting products, or a push timed around Prime Day or Black Friday, can close the gap.
Don’t buy through your own links to hit the number. Amazon’s rules don’t allow it, and you’d be risking the whole account for a few days of API access.
4. Wait, and leave your credentials alone
Once your referred sales ship and you’re back above 10, access usually returns by itself within about two days. There’s no form to fill in and no one at Amazon to email.
Don’t regenerate your keys while you wait. Eligibility belongs to the account, not the key, and some developers report new keys taking up to three days to activate. Regenerating can make your outage longer.
5. If you have 10 sales and still see the error
A smaller group of developers get AssociateNotEligible with plenty of sales. These are the causes reported most often:
- your Associates account isn’t fully approved yet (new accounts need three qualifying sales in their first 180 days)
- the marketplace you’re calling runs its own eligibility check, which developers have reported on smaller stores such as Brazil
- Amazon deactivated your API key in a security audit without telling you, and here a fresh key from Associates Central is the fix
If none of these fit, contact Associates support. Name the marketplace and paste the exact error text, so they don’t send you a generic reply.
6. Keep your site from breaking in the meantime
An empty product box looks bad, but a wrong price is worse. Cache the last good response for each product so titles and images still show, hide any price you can no longer refresh, and fall back to a plain “Check price on Amazon” link.
How to fix the AssociateNotEligible error
1. Log the full response
Many apps only record the status code. Log the whole response body so you can see AssociateNotEligible written out, rather than guessing from a bare 403.
2. Count your shipped items for the last 30 days
Sign in to Associates Central and open your earnings reports. Look at items shipped over the last 30 days, counting back from today. Under 10 means you’ve found the cause.
3. Get back over 10 qualifying sales
Focus on the pages that already get traffic. Some quick wins:
- add affiliate links to high-traffic posts that don’t have any yet
- send your email list a roundup of your best-converting products
- time a push around a big sales event like Prime Day or Black Friday
Don’t buy through your own links to hit the number. Amazon’s rules don’t allow it, and you risk the whole account for the sake of a few days of API access.
4. Wait for access to come back
Once your referred sales ship and you’re back above 10, access usually returns on its own within about two days. You don’t need to contact Amazon.
Resist regenerating your credentials. New keys don’t change your eligibility, and reports suggest they can take up to three days to activate, which only makes the wait longer.
5. Stop your site breaking while you wait
An empty product box looks worse to a reader than an outdated one, but a wrong price is worse than both. A few safer defaults:
- cache the last good response for each product, so titles and images still show
- hide the price, rather than show one you can’t refresh
- fall back to a plain “Check price on Amazon” link
Check the Amazon Associates Operating Agreement for its rules on showing prices and product information before you decide what stays up.
Keep product data coming with a fallback
If two days is too long, or you know you won’t reach 10 sales any time soon, you need product data that doesn’t depend on your Associates account.
There are three realistic routes. SiteStripe links, made by hand from Amazon’s toolbar, work for a handful of products but never update. Scraping Amazon yourself means paying for proxies, solving captchas and fixing your scraper every time Amazon changes a page layout. A third-party Amazon product data API costs a monthly fee, and in return you send an ASIN and get structured data back.
Using Amazing API as a fallback
Amazing API returns Amazon product data by ASIN, and access doesn’t depend on your Associates sales. You get the fields most affiliate sites and price trackers display: title, description, current and previous price, availability, deals, images, category and bestseller rank. It covers 10 Amazon marketplaces, including the US, UK, Germany, Canada, Japan, India and Australia.
The cleanest setup keeps Amazon as your main source and only calls Amazing API when Amazon refuses the request. In Python:
import os
import requests
AMAZING_API_URL = "https://api.getamazingapi.com/v1/product/"
def is_not_eligible(resp):
# Works for both the Creators API and older PA-API response formats
return resp.status_code == 403 and "AssociateNotEligible" in resp.text
def get_product(asin, country="us"):
resp = fetch_from_creators_api(asin) # your existing Creators API call
if resp.ok:
return resp.json()
if is_not_eligible(resp):
fallback = requests.post(
AMAZING_API_URL,
headers={"x-api-key": os.environ["AMAZING_API_KEY"]},
json={"asin": asin, "country": country},
timeout=30,
)
fallback.raise_for_status()
return fallback.json()
resp.raise_for_status()
fetch_from_creators_api stands for the Creators API call you already have. The two APIs return differently shaped JSON, so map the fields you display (title, price, image) in one place, and the rest of your site won’t care which source answered.
Each request uses a credit from your plan, so cache results and refresh on a schedule. Once a day suits most listings.
One rule to keep in mind: this replaces your product data, not your affiliate links. Your links and tracking tag still come from your Associates account, so read the Amazon Associates Operating Agreement on how product information and prices must be shown before you use third-party data on affiliate pages.
Frequently Asked Questions
Why has my Amazon API suddenly stopped working?
Check the error text. AssociateNotEligible means your account is below 10 qualifying sales in the last 30 days. A message saying the Product Advertising API is deprecated means your code still calls PA-API 5.0, which Amazon retired in 2026.
How long until my access comes back?
Usually about two days after your referred sales have shipped and you’re back above 10 in the last 30 days.
Do my affiliate links stop earning while I have this error?
No. The error blocks API requests only. Links already on your site keep tracking sales, and those sales count toward getting your access back.
Is this the same as the three sales in 180 days rule?
They’re different rules, though both can trigger AssociateNotEligible. The 180-day rule decides whether a new Associates account gets approved at all. The 10-sales rule decides whether an approved account keeps API access.
Will creating new API credentials fix it?
No. Eligibility is tied to your account’s sales, not your keys, and new keys can take a few days to activate.
Can I get Creators API access with no sales?
Not with your own credentials. You’ll need to reach the threshold first, or use a product data source that doesn’t depend on your Associates sales.
Can I get Amazon product data without the Creators API?
Yes. Your options are manual links from SiteStripe, building your own scraper, or a product data API like Amazing API that doesn’t depend on your Associates sales.
Get your product data back today
If AssociateNotEligible has left your pages empty, you can try Amazing API before paying for anything. It’s in free trial right now, and your API key arrives by email when you sign up. Start your free trial or compare plans.
Need extra fields or higher volume? Get in touch.

I’m Samikshya Sapkota, a content and SEO writer. I write Amazing API’s guides on Amazon’s APIs and affiliate tools. When Amazon changes its rules or a new error starts showing up, I dig into what’s causing it and write up the fix in clear steps.

