Amazon's PA-API Retires in 2026: How to Move to Monid

Here's how to move off Amazon's Product Advertising API, retired as of May 2026, and rebuild your product, pricing, and review data on Monid instead. Plus what Amazon's new Creators API does and doesn't replace, so you can pick the right path for your app.

Amazon retired PA-API v5 on May 15, 2026, with deprecation from April 30 and the Offers resource going dark earlier on January 31. If your app or affiliate plugin still authenticates with the old AWS Signature V4 scheme, it has already stopped returning data. The good news is that once you know what you actually pull from PA-API, moving it is a short job, whether you go to Amazon's official replacement or to a pay-per-call source.

Key dates for the PA-API retirement

Three dates matter, and they didn't arrive together. Find the earliest one that touched your integration; if you're reading this after May 2026, all three have now passed.

• January 31, 2026: the Offers V1 resource was cut off first. If you read buy-box prices or offer listings, this was your earliest deadline, months before the rest.
• April 30, 2026: PA-API v5 was deprecated. This was Amazon's recommended migration cutoff, after which you should assume no fixes and no support.
• May 15, 2026: the v5 endpoint was retired. Requests signed with AWS Signature V4 are now rejected, so anything not migrated stopped returning data with no grace period.

Dates and details are in the PA-API documentation and this auth-layer migration writeup.

Step 1: Take stock of what you pull from PA-API today

Before you migrate anything, list the calls you actually make. Most integrations lean on a small subset, and each maps cleanly to a replacement.

Product details (GetItems)

Titles, prices, list prices, images, feature bullets, availability, and the star rating with its review count. For most affiliate and catalog integrations this is the bulk of the traffic, often one GetItems call per product page render.

Search results (SearchItems)

Keyword-to-product listings with prices, identifiers, and ratings. If you build category pages, comparison tables, or price feeds, this is the call behind them.

Ratings and review counts (CustomerReviews)

The star average and the number of ratings, and nothing else. Worth flagging now, because it shapes your options: this is all PA-API has ever returned about reviews. There has never been review text, and the Creators API keeps that same limit.

Your authentication

PA-API v5 signs every request with AWS Signature V4, using an access key and secret tied to your Associates account. That signing scheme is exactly what retires on May 15, so even if every field you read still exists, the auth path itself breaks. Any migration is, at minimum, an auth rewrite, which is the real reason a "small" PA-API dependency is more work to move than it looks.

Step 2: Rebuild those calls on Monid

Monid is a pay-per-call data API marketplace: you discover an endpoint, inspect its schema and price for free, and only pay when you run it. Each PA-API call above has a direct replacement, and none of them need an Associates account or AWS signing. Here's how the three map over.

1. Product details. Swap GetItems for the Apify product-detail actor, which returns pricing, list price, discounts, availability, star rating, rating distribution, best-seller rank, categories, brand, and images by ASIN.

npm install -g @monid-ai/cli
monid keys add   # one time: paste your key from monid.ai
monid run -p apify -e /delicious_zebu/amazon-product-details-scraper \
  -i '{"Params": ["B0BSHF7WHW"]}' -w
# -> full product record, billed per result, price shown before it runs

Where PA-API wanted a signed AWS request and a live Associates account, this is one Monid key and one command. Expect to remap field names rather than rewrite your logic, and a free inspect shows the exact shape before you commit.

2. Search results. Swap SearchItems for the Apify search actor, axesso_data/amazon-search-scraper. It takes a keyword and returns titles, prices, identifiers, ratings, and result positions across marketplaces, so your category and price-feed pages keep working after a field remap rather than an auth rewrite.

3. Reviews (the upgrade PA-API never gave you). This is the part worth getting excited about. Because you were never getting review text from Amazon, moving off PA-API is the moment you can finally read it. The axesso_data/amazon-reviews-scraper returns each review's full text, verified-purchase flag, date, and helpful votes. See how to pull an ASIN's whole review history in one call, score those reviews for sentiment in fifteen minutes, or the best Amazon reviews APIs compared if you're weighing options.

Each of these bills per result, a fraction of a cent, with the pricing model and exact price shown by a free inspect before you run. Point an agent at Monid once with set up https://monid.ai/SKILL.md and it can make these calls itself.

PA-API alternatives, and why Monid fits

You have two honest paths off PA-API, and they aren't mutually exclusive.

The Amazon Creators API is the official successor. If you're a pure affiliate who only needs prices and ratings and wants to stay inside Amazon's blessed pipeline, it's the natural move. Be ready for real work: it's OAuth 2.0 client credentials, a new endpoint, and a new request shape, not a config flip. And it inherits the same limit, no review text.

Monid is the fit when you want more than PA-API gave you, or you'd rather not manage Amazon auth at all. Product data, search, and actual review text come through one pay-per-call wallet, with no Amazon account needed for the data itself, and the same balance is ready for the social or enrichment data your project needs next.

There's also a resilience argument that PA-API veterans will appreciate, since you've just lived through a single API being deprecated out from under you. On a marketplace, the same job usually has more than one endpoint: if a product-details actor breaks or a provider retires something, an alternative is one free discover away on the same wallet, so a dead endpoint is a flag change, not another migration project.

* Monid's data needs no Amazon account. You keep an Amazon Associates tag only if you still earn affiliate commissions, which is a separate concern from where your data comes from.

A migration you can do in an afternoon

You don't have to boil the ocean. A working migration is four steps, and the first two are free.

1. Inspect the replacements. Run monid inspect on the product-details, search, and reviews endpoints. You see the exact fields, the pricing model, and the price without spending anything, so you can confirm the data matches what you parse today.
2. Run one ASIN through each. Pull a single product you know well and diff the output against your current PA-API response. This is where you catch field-name differences before they reach production.
3. Swap your calls. Replace the signed GetItems and SearchItems requests with monid run calls. The response parsing largely carries over, since you're reading the same underlying Amazon data.
4. Add what you couldn't have before. Wire in the reviews endpoint for the text PA-API never exposed, gated to verified purchases when it feeds a decision.

Keep your first runs small with a low maxPages or item count, read the price the free inspect prints, then scale once the shapes line up.

FAQ

Do I actually have to migrate? If your app calls PA-API v5 after May 15, 2026, yes. The endpoint is retired and the old AWS Signature V4 auth is rejected, so requests fail regardless of which fields you use.

Is the Creators API a drop-in replacement? No. It's a new endpoint with OAuth 2.0 client credentials and a different request and response shape, so plan for an auth rewrite either way.

Can I finally get Amazon review text? Not from Amazon. Neither PA-API nor the Creators API returns review bodies. The text comes from a scraper, and on Monid axesso_data/amazon-reviews-scraper returns it, billed per result (one query pulls an ASIN's reviews), with the price shown by a free inspect.

Will my parsing code still work? Mostly. You're reading the same Amazon product data, so field mapping is close, but you should diff one product's output during migration to catch naming differences before they hit production.

Is scraping Amazon data allowed? Scraping public pages sits in a contested legal area that keeps shifting, and Amazon's own terms restrict automated access. Get your own legal read before running it at scale, and prefer verified providers.

What does it cost on Monid? Per result, a fraction of a cent for most Amazon calls, shown before the call runs, with no subscription or minimum. Current prices are at monid.ai/tools.

Last updated July 2026.