The Amazon Product Advertising API: what happened to it, and what replaced it

If you are reading Amazon’s Product Advertising API documentation today, or a tutorial about it, you are reading about something that no longer answers. PA-API 5.0 was deprecated on 30 April 2026 and its endpoint was switched off on 15 May 2026. Requests return HTTP 403 with a pointer to the migration guide. No combination of old keys brings it back, because the credentials themselves were retired along with the service.

That belongs at the top because most of what still ranks for these terms was written before May and has not been touched since. What follows is the part that is still worth knowing: what the API did, whether it ever cost money, what the request limits were and are, which of Amazon’s several similarly named APIs you actually want, and what to do with a site whose product boxes went blank.

What the Product Advertising API was for

It had one job. You sent it an ASIN — Amazon’s ten-character product identifier — and it sent back the things you cannot lawfully copy by hand: the current title, the product image, the price, whether the item is in stock, the star rating and review count. Your Associates tag came back baked into the link, so a click from the box you built was attributed to you.

Everything an Amazon affiliate plugin does that looks automatic runs on that one call. A price that updates overnight, an image that changes when Amazon changes it, a box that greys out when the item goes out of stock — all of it is a product lookup on a schedule. Without the API, a product box is whatever somebody typed into it, frozen at the moment they typed it.

This is also why the API mattered legally rather than merely practically. Amazon’s Operating Agreement does not let you scrape product pages, and it does not let you present a price that you retyped and left to rot. The API was the sanctioned route to the same data, and it carried the freshness rules with it.

Was the Product Advertising API free?

Yes in money, and that is why the question keeps being typed into search boxes in exactly those words. There was never a fee, never an invoice, never a per-call price. There is no paid tier of the Creators API either. If you are budgeting for a project, the API line is zero.

The price is paid in sales instead, and it is steeper than a fee would be.

Getting in. API access is gated behind three qualifying sales within 180 days of applying — the same bar that decides whether your Associates account survives its trial at all. This part Amazon documents plainly. A brand-new account therefore has a working tracking tag and no API credential, which surprises nearly everyone who buys a plugin to build their first product boxes.

Staying in. The credential is not a certificate you keep. It carries a rolling sales requirement, re-tested continuously, and a quiet month takes it away from an account that has run for years. Historically the bar was three referred sales per thirty days. Reports through 2026 put the Creators API requirement at ten qualified sales in the trailing thirty days, surfaced as an AssociateNotEligible response. We mark that one as reported rather than documented, because Amazon has not published it anywhere citable.

Put the two halves together and you get the circle that no vendor in this category puts on its front page: the API you need in order to build product boxes is gated behind sales you are unlikely to make until you have product boxes. It is not a reason to avoid the programme, but it is the single most useful thing to know before you buy anything, and we set out the full shape of it in the requirements for an Amazon Associates account.

The rate limits, and why every figure you find is stale

PA-API 5.0’s published scheme had a shape worth understanding even now, because the replacement kept the principle: your quota was tied to the revenue you sent Amazon. New accounts started at a floor — the figure Amazon published was one request per second with a daily cap in the region of 8,640 calls — and both numbers rose as shipped revenue in the trailing thirty days rose. Sell more, ask more often.

Those exact numbers are now historical, and anyone quoting them as current is quoting a switched-off service. What we can say about the Creators API is what it does rather than what it promises: Amazon has not published its quota anywhere we can cite, and in practice you learn your ceiling by meeting it. Exceeding it returns HTTP 429, and retrying immediately makes the throttle worse rather than better.

Three things follow for anyone building against it, and they were true of the old API too:

• Cache the token, not just the data. Minting a fresh OAuth token on every product lookup is the most common way to burn a quota doing no useful work.
• Cache responses, but cap the cache at twenty-four hours. Caching hard is the obvious way to stay inside a limit, but a cached price older than a day stops being a performance decision and becomes a compliance problem.
• Fail soft on 429. Serve the last good response and try again later. A client that retries in a tight loop turns a brief limit into a long one.

The caching cap is the part that catches people out, because the two pressures point in opposite directions. The rate limit rewards holding data as long as possible; the Operating Agreement requires prices taken from the API to be refreshed regularly and shown with the time they were retrieved. Twenty-four hours is where those two meet.

Three Amazon APIs, one word apart

A measurable share of the people searching for the Product Advertising API end up in the wrong handbook, because Amazon runs several programmes whose names differ by a single word and whose documentation lives in separate developer portals.

The distinction that matters most: the Amazon Ads API — often written Advertising API — belongs to sellers, vendors and the agencies working for them. It is for buying sponsored placements and reading campaign reports. It uses a different account type, a different approval process and different documentation, and it will never return a product box for your blog. If you have arrived at a page about campaign budgets and negative keywords, you have arrived at that one.

The Creators API is the one you want. It does the Product Advertising API’s job with new plumbing: OAuth 2.0 client credentials instead of AWS Signature V4, a single host with the marketplace moved into a header, and a different response shape. Nothing written against PA-API works when pointed at it. We wrote up the migration in detail — request by request, including the parts that bite — in the guide to the Amazon Creators API.

What to do now, depending on where you are standing

Your boxes went blank in May. That is the endpoint being switched off, not a plugin fault and not an expired key. Fetch new credentials from Associates Central under Tools → Creators API, note that they are issued per region so working across Europe and North America means two pairs, and check that whatever plugin you use speaks the new API rather than the old one. A plugin that has not shipped an update since spring is a plugin that cannot fetch anything.

You wrote code against PA-API. The community wrappers — the Python packages in particular, which is where a good deal of affiliate tooling lives — were built around SigV4 request signing against the retired host. They are not broken in a way a version bump fixes; the service they sign for is gone. Budget for the authentication layer to be rewritten rather than patched. The token exchange itself is ordinary OAuth and is the easy half.

You have no credential yet, and no sales. This is the common case and it is not hopeless, because a surprising amount works with no API at all: tagged links, buttons, your own photographs and your own words. What you cannot do is show a price you typed yourself — not because it will look stale, but because a hand-typed price is not permitted in the first place. A button reading Check price on Amazon with no figure sidesteps the problem entirely and converts about as well. SiteStripe still builds those links for you, and what an affiliate plugin can and cannot do without a key sets out the rest.

You are choosing a plugin and the API decides it. Then the question to ask a vendor is not whether it supports the Creators API but whether it does so in the free version, and what it does on the days you have no credential. A plugin that treats a missing key as an error state is a plugin that is useless for exactly as long as you need it most.

Common questions

Disclosure, since this is our own site: Doozly is an Amazon affiliate plugin and talks to the Creators API. It does so in the free version, and it builds tagged product boxes with no credential at all for the stretch when you do not have one yet.