A ready-made third-party data API is the quickest way to pull Amazon product, price and review data as clean JSON, with no approval process to wait on. Amazon's official API suits affiliate sites that meet its access rules, and a scraper API from a proxy company suits teams that need fields nobody packages.
Amazon's own product API documentation now sits under the name Creators API, complete with a guide for migrating away from the older PA-API. If you built on the old name, that's your first job. If you're starting fresh, it's a good moment to ask whether the official route is the right one at all.
There are three kinds of tool here. I'll weigh the types first, then list the APIs, then cover cost and a quick way to test one.
The official Amazon API: upside and downside
The upside: it's Amazon's own data, served by Amazon, with documentation and a stable contract. For an affiliate site that already earns commission and wants product titles, images and prices on its pages, it's the natural fit, and you're not relying on anyone scraping anything.
The downside: access comes with rules. There's an approval step, and at least one third-party provider pitches itself on having no approval process or affiliate quotas, which tells you where the friction sits. The rename and migration also mean any older code needs attention. Read Amazon's current terms for what your use is allowed before you build anything on it.
Ready-made data APIs: strengths and limits
Strengths: these services do the collection for you and hand back structured JSON for products, offers, reviews and search results. You call an endpoint with an ASIN or a keyword and get fields back, with no proxies to rotate and no parsers to fix when Amazon changes a page. Some add extras such as sales estimates or access through GraphQL and MCP for AI agents.
Limits: you depend on a third party staying ahead of Amazon's page changes, and on that company staying independent. Ownership shifts happen: Traject Data, maker of Rainforest API, has joined ScraperAPI, so check who you're signing with. Check, too, that the fields you need exist in their response, because each provider decides its own schema.
Scraper APIs from proxy companies: the trade-offs
Large scraping vendors sell a dedicated Amazon scraper alongside their proxy business. The upside is reach and control: they're built for scale, they handle blocking, and you can often pull fields a packaged data API leaves out. The downside is that you're closer to the plumbing. Expect more setup, more parameters and more parsing on your side than a ready-made product API asks of you.
I'd only go this way if you've outgrown a data API, or if you already scrape other retailers and want one supplier. For broader options, my list of web scraping APIs covers the general-purpose end of the market.
Amazon data APIs worth a trial
Amazon Creators API (formerly PA-API)
Amazon's official product data API, now documented under the Creators API name with a migration guide for anyone still on PA-API.
Rainforest API
A real-time Amazon product data API sold on monthly credit plans, now part of the ScraperAPI family after its maker joined that company.
Canopy API
Developers building apps or AI agents get Amazon product, pricing, review and sales-estimate data here through REST, GraphQL or MCP.
Axesso Amazon API
An Amazon data API and dataset provider that reaches beyond Amazon to Walmart and other retailers, sold direct and through RapidAPI.
DataForSEO Merchant API
Ecommerce data from Google Shopping and Amazon in one merchant API, useful when your reporting already compares both channels.
SerpApi Amazon Search API
Returns Amazon search results with organic listings, product ads and filters, a fit for rank tracking on Amazon's own search.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
ScraperAPI Amazon Endpoint
A structured-data endpoint inside the ScraperAPI scraper that turns Amazon product pages into JSON without you writing a parser.
Bright Data Amazon Scraper
From a large proxy and scraping company, this dedicated Amazon scraper API returns product records and suits high-volume collection.
Oxylabs Amazon Scraper API
Oxylabs' Amazon scraper for product data, a scraping-infrastructure option for teams that want a trial before they commit.
How the bill adds up
Third-party Amazon data is metered, and the meter differs by provider. Credits are common: a monthly plan buys a block of credits, and each request spends one or more depending on the endpoint, with an extra-credit rate once you run out. Others price per request or per record returned. Free plans, free trials and free starter requests all appear in this category, so you can test before paying.
The cost driver people miss is refresh rate. Tracking prices on a few hundred products once a day is cheap; checking them hourly is a very different bill. Work out products multiplied by checks per day before you compare plans, then read each vendor's pricing page for what a single request costs in credits and what happens on overage. Put as a range in words: the bottom is a free plan or a batch of free test requests, enough for a proof of concept; the middle is a monthly credit plan that covers a small price tracker refreshing daily; the top is high-volume collection, where the bill follows the records or credits you use. Prices change, so treat any figure you remember as stale.
Do you make Amazon product data APIs? Tool makers can ask to be considered for a featured place on this list.
Checking twenty ASINs against the live listing
Pick twenty ASINs that matter to you: a mix of your own products, competitors and a couple with lots of variations. Run them through the free plan or trial of two providers on the same afternoon.
Compare four things: whether every field you need came back (price, Buy Box seller, rating, review count, variations), whether the price matches what Amazon shows in your browser right now, how long each call took, and how many credits it used. A product with many variations is the hardest case, so look closely at that one.
If the numbers match and the fields are there, the cheaper provider wins. If one keeps missing variations or returns stale prices, that's the answer, whatever the plan costs.
Seller and research tools instead of code
If you're a seller, you may want this data inside a tool rather than as a raw feed. If you'd rather not write code at all, look at Amazon seller tools first; many of the reports you'd build from an API already exist there. Developers building a price tracker, a comparison site or an AI shopping agent are the people an API is really for, and for them the type of tool above matters far more than the brand.
Product research is the other common destination. Spotting a niche, sizing demand and checking how crowded a category looks are jobs that dedicated Amazon product research tools already do with their own data and estimates. I'd only build that from an API if the research is your product, or if you need it joined to data the tools can't see, such as your own sales and margins.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.

