Amazon Product Data API
Get a free sandbox key and pull your first ASIN record in minutes.
Get a free sandbox key and pull your first ASIN record in minutes.
The EcomSource Amazon product data API returns Amazon product records as clean JSON: send an ASIN or a UPC and get the title, brand, images, parent and child variations, buy box price, sales rank, and every cross-referenced identifier. No Associates account, no sales thresholds, no scraping. The sandbox tier is free with 10 calls a day.
TL;DR
- •One call: ASIN in, full Amazon-side record out, including the UPC and EAN behind the listing.
- •No Associates program required, which is the wall most developers hit with Amazon PA-API.
- •Variations, buy box, and sales rank are part of the record, not separate calls.
- •Free sandbox, then $49 per month for 10,000 calls (pricing current as of August 2026).
What is an Amazon product data API?
It is a web service that returns structured data about products listed on Amazon: identifiers, catalog details, variation families, and market signals like buy box price and sales rank. Developers use one to power seller tools, sourcing software, and analytics without scraping Amazon pages or qualifying for Amazon’s own restricted APIs.
Why developers look beyond Amazon’s official APIs
Amazon’s Product Advertising API is built for affiliates: access requires an Amazon Associates account, and keeping it requires qualifying sales (Amazon PA-API documentation). The Selling Partner API is built for sellers operating their own account, with scopes and approvals to match. Both are excellent at their own jobs. Neither is designed for the common case of a tool that simply needs product data by identifier. That gap is what this API fills, and our SP-API vs [product data API comparison](/blog/amazon-sp-api-vs-product-data-api) maps which tool fits which job honestly.
What you can pull
Data
Detail
Catalog record
Title, brand, images, category for any ASIN
Identifier bridge
The UPC, EAN, and GTIN behind the listing, and the reverse direction from barcode to ASIN
Variation family
Parent ASIN with child ASINs, so sizes and colors resolve correctly
Market signals
Buy box price and sales rank, plan dependent
Format
JSON built for pipelines, same shape as the rest of the product data API
There is also a practical throughput point. PA-API request limits scale with the revenue your Associates account generates, starting from a baseline of one request per second (Amazon PA-API documentation), so a new tool starts at the bottom of both ladders at once: it must qualify to get in, then earn throughput. A metered monthly plan with no revenue coupling is simply a different kind of deal, and for product-data tools it is usually the right one.
The call
curl -X POST "https://api.ecomsource.ai/api/v1/search/product" -H "X-Access-Key: your_access_key" -H "X-Secret-Key: your_secret_key" -H "Content-Type: application/json" -d '{"identifier": "B07FCZSC41", "identifierType": "asin"}'
The same endpoint accepts upc, ean, gtin, and isbn as identifierType, which is how barcode-first workflows reach Amazon data in one hop. Examples in Node.js, Axios, and Python are in the API documentation.
What teams build with it
Sourcing tools that take supplier UPC lists and surface the matching listings with rank and buy box, the workflow behind our UPC to ASIN converter.
Listing monitors that watch variation families for hijacks, merges, and drift.
Analytics pipelines that join Amazon signals to internal catalog data by GTIN.
AI agents that answer product questions with grounded lookups instead of guesses.
Migration notes from PA-API
Field mapping is the whole job: titles, images, and identifiers exist on both sides under different names, and one afternoon of mapping covers a typical integration.
Variation handling gets simpler: the parent and child family arrives in one record instead of chained calls.
Keep your caching layer: identifiers are stable keys, so cached records survive the switch untouched.
Run both in parallel on 50 ASINs first and diff the outputs, the sandbox makes that free.
Choosing between the Amazon APIs and this one
You need
Use
Affiliate links and commissions
Amazon PA-API, that is its purpose
Managing your own seller account: orders, inventory, fees
Amazon SP-API
Product data by identifier for a tool or pipeline
This API
Product data plus wider retail context beyond Amazon
This API, the record is marketplace-wide
Pricing follows the standard product data API plans: free sandbox at 10 calls a day, $49 per month for 10,000 calls, $149 for 50,000 with bulk exports and webhooks, custom above that (pricing page, August 2026). Our comparison of Amazon product APIs in 2026 puts these numbers next to the alternatives.
Pull your first record
Create a free sandbox key, send any ASIN, and inspect the JSON yourself. No Associates account, no card.
Frequently Asked Questions
Is EcomSource an official Amazon API?
No. It is an independent product data API whose records include Amazon intelligence. Use Amazon PA-API for affiliate features and SP-API for operating a seller account. Use this when a tool needs product data by identifier.
Why not just use Amazon PA-API?
PA-API access requires an Amazon Associates account and qualifying sales to maintain, per Amazon documentation. If your tool is not an affiliate product, that requirement blocks you by design.
Can I get the UPC behind an ASIN?
Yes, that bridge is the core of the record: every ASIN result includes the UPC, EAN, and GTIN registered to the product, and the lookup works in reverse from any barcode.
Does it return variations and buy box data?
Yes. The record includes the parent and child variation family, and buy box price with sales rank on plans that include Amazon intelligence.
Is there a free tier?
Yes, the sandbox is permanently free: 10 calls a day with full JSON responses. Production starts at $49 per month for 10,000 calls (August 2026).
Is scraping Amazon a real alternative?
It works until it does not: pages change, blocks escalate, and the legal ground is gray. An identifier API trades that fragility for one stable contract, which is why tools that outgrow prototypes almost always end up on one.