Amazon Product Advertising API is retired: what to do now

If you’ve landed here looking for how to register for the Amazon Product Advertising API, I’ve got bad news and then some better news.

The bad news is that you can’t. Amazon deprecated PA-API v5 on 30 April 2026 and retired the endpoint on 15 May. Call it now and you get a 403 back, with a message telling you to migrate. It isn’t a fault at your end and there’s nothing to fix in your code.

The better news is that there’s a replacement, and getting onto it is mostly paperwork — as long as you clear one hurdle, which is the part nobody mentions.

What actually happened

Amazon replaced PA-API with the Creators API. Same idea — programmatic access to the product catalogue, prices, images, availability — rebuilt on a different foundation.

The dates worth knowing:

• 30 April 2026 — PA-API v5 deprecated
• 15 May 2026 — the endpoint retired and stopped responding
• 30 June 2026 — the final cut-off Amazon gave for migrating

All three are behind us. If you’re reading this because a widget stopped showing prices or a plugin started throwing authentication errors, that’s why.

The ten-sales rule

This is the bit that catches people, and it’s why half the searches landing on this page are about access requirements rather than how to register.

To get Creators API credentials you need:

• an Amazon Associates account in final accepted status
• at least ten qualifying referred sales in the last thirty days
• to be the primary account owner — not a team member on a shared login

The second one is the wall. It’s a rolling window, so it isn’t a threshold you clear once and forget about. Quiet month, no API.

And there’s the circularity. Plenty of publishers wanted the API in order to build the pages that generate the sales. Now you need the sales to get the API.

I’m not going to pretend that’s unreasonable from Amazon’s side. They’re paying for the infrastructure and they’d rather it served people sending them orders. But it does mean the API is no longer something you can simply sign up for — and if you’re a smaller publisher, it may never be available to you at all.

If you’re starting from zero, this is a deadlock

Worth spelling out, because it catches a particular kind of person hard.

You need ten sales to get the product data. You need product data to make the sales. If you are launching something new there is no route through that, and it isn’t only an Amazon problem.

• Skimlinks automatically rejects sites with fewer than ten original articles, or without regular verifiable traffic. Coming-soon sites are declined, and a refusal means ninety days before you can reapply.
• Impact starts at around $500 a month and is aimed at companies over $1m in revenue.
• Amazon wants ten sales in the last thirty days before it will talk to you.

So a new commerce site is locked out by all three at once — whether that’s a publisher launching a vertical, or someone who built a site over a weekend with an AI tool. The gate is on product data, and every incumbent has set it above where you are standing.

The way out is product data that isn’t conditional on sales you haven’t made yet. If you want to see what that looks like in practice, the quickstart gets you a live price in about five minutes.

What else changed

If you did clear the threshold and you’re migrating existing code, the main difference is authentication.

PA-API used AWS Signature Version 4 — derive a signing key, sign the request, mind the fifteen-minute timestamp window. Creators API uses OAuth 2.0 client credentials instead. You swap a Client ID and Client Secret for a bearer token and send that.

Parameter names have also moved from PascalCase to lowerCamelCase, so a straight endpoint swap won’t work. Budget half a day rather than half an hour. Product identifiers are unchanged, so if you were already working with what an ASIN is, that all still applies.

If you can’t get access

Three honest options.

Wait and build the sales first. If you’re close to ten a month, keep going. The threshold is achievable for most sites with genuine commerce traffic.

Use SiteStripe and manual links. Slower, and worth knowing that Amazon removed image and HTML link generation from SiteStripe back in 2023, so it’s more limited than it used to be.

Get your product data from somewhere that isn’t Amazon. This is the one most publishers land on eventually, and not only because of the threshold. There are product data APIs that aren’t tied to one retailer, and there are the networks themselves — Awin and Impact between them cover a very large share of what Amazon does, at rates that are frequently better.

What to do this week

Whether or not you’re getting back onto Amazon:

1. Find out what’s actually broken. Any plugin, widget or script still calling webservices.amazon.com is failing silently. Readers see stale prices or empty modules. You see nothing at all.
2. Check your Associates status. Final accepted, and are you the primary owner? If not, sort that before anything else.
3. Count your last thirty days of qualifying sales. That tells you whether this is a waiting problem or a different-approach problem.
4. Look at what a single-retailer dependency costs you. Amazon changed the rules with notice, publicly, and it still broke a lot of sites. If you live in someone else’s house you have to abide by their rules, and they can change them without notice.

That last point is the one worth sitting with. It isn’t really about Amazon.

One retailer is not a strategy

Amazon is the biggest single programme most publishers have, and it has just demonstrated how quickly that can stop being true. The answer isn’t a different single retailer. It’s not having one.

Squirrel connects to seventeen affiliate networks and several thousand retailers. Your own accounts always take priority — we fill the gaps where you don’t have a relationship, so a retailer going quiet doesn’t take a section of your site with it.

If you want to know what’s still earning on your site after all this, the free link audit will tell you in about a minute. No account needed.

Common questions

Is the Amazon Product Advertising API gone for good?

Yes. PA-API v5 was deprecated on 30 April 2026 and the endpoint retired on 15 May. Creators API is the supported successor.

Can I get an API key without the ten sales?

No. Ten qualifying referred sales in the last thirty days is a requirement for Creators API access, alongside final-accepted Associates status.

Does the requirement reset?

It’s a rolling thirty-day window, so access depends on continuing to generate sales rather than clearing the bar once.

Can someone else on my team register?

No. Only the primary account owner can register the application.

Will my old PA-API code work?

No. Authentication has moved from AWS Signature V4 to OAuth 2.0, and parameter names have changed casing.

How do I get product data for a brand new site?

Not from Amazon - the ten-sales rule blocks it, and Skimlinks and Impact have their own thresholds. You need a product data source that isn’t gated on sales history.