Amazon Scraper API for live, complete Amazon data
Turn product pages, search results, seller storefronts, Best Sellers and New Releases into production-ready data—without maintaining proxies or parsers.
POST /api/v1/scrape
{
"parserName": "amzProductDetail",
"site": "amz_us",
"content": "B0B4NLGCH5",
"format": "json",
"bizContext": {
"zipcode": "10041"
}
}{
"code": 0,
"message": "ok",
"data": {
"json": [{
"data": {
"results": [{
"asin": "B0B4NLGCH5",
"title": "…",
"price": "…"
}]
}
}]
}
}Built for ecommerce and development teams
From free account to usable Amazon data in one request
Choose a parser and marketplace, then copy production-shaped code. Register to replace the token and use your first 60 requests at no cost.
curl --request POST \
--url https://scrapeapi.pangolinfo.com/api/v1/scrape \
--header 'Authorization: Bearer YOUR_API_KEY' \
--header 'Content-Type: application/json' \
--data '{
"url": "",
"parserName": "amzProductDetail",
"site": "amz_us",
"content": "B0B4NLGCH5",
"format": "json",
"bizContext": {
"zipcode": "10041"
}
}'{
"code": 0,
"message": "ok",
"data": {
"json": [{
"code": 0,
"data": {
"results": [{
"asin": "B0B4NLGCH5",
"title": "Example product title",
"price": "$29.99",
"rating": "4.5",
"availability": "In Stock"
}]
}
}]
}
}The builder reflects the documented API schema. Example values are illustrative; Amazon availability and returned fields depend on the selected page and marketplace.
Amazon-native coverage, not a generic page wrapper
Ask for the Amazon object you need. Pangolinfo handles access, rendering and Amazon-specific parsing, then returns fields your application can use directly.
Complete product-page context by ASIN
Build product intelligence with current retail, seller, inventory, content, variation and ranking signals instead of stitching together a shallow set of generic fields.
Search results with paid and organic context
Track what shoppers can actually see: result position, page, keyword, product metadata and sponsored-placement evidence for research, attribution and monitoring.
Category supply, density and product mix
Collect category listings by Amazon node and compare the products, prices, ratings and merchandising signals that define the competitive shelf.
Seller storefront and assortment intelligence
Follow a seller’s visible catalog, filter by category and retrieve up to the documented page limit in one request for assortment and launch monitoring.
Current Best Sellers by category
Capture category leaders and their visible commercial signals to monitor demand shifts, ranking movement and product concentration over time.
New products before they become obvious
Collect New Releases by category to identify emerging ASINs, compare early traction and feed product-research or competitor-alert workflows.
Amazon Review API is a separate product with review-specific filters, media fields and billing. Keeping it separate makes the integration and cost model clearer.
If the ad position is missing, the search result is incomplete
Amazon keyword intelligence depends on separating sponsored placement from organic rank. Pangolinfo is purpose-built for this difficult Amazon signal—not just the HTML around it.
- 90%+ SP ad-placement capture rate
- Daily capture-rate monitoring
- Position-level evidence for paid and organic analysis
The displayed rate is Pangolinfo’s monitored SP placement capture metric. Actual visibility varies with keyword, marketplace, location and the live Amazon result.
What is an Amazon Scraper API—and what does it handle for you?
An Amazon Scraper API turns live Amazon pages into data an application can use repeatedly. Instead of maintaining browser automation, proxy access, retry logic and page-specific parsers yourself, your system sends a request for the Amazon object it needs and receives a consistent output such as structured JSON.
From a live Amazon page to a usable record
Downloading one page is only the first step. A production Amazon data workflow also has to preserve marketplace and delivery context, render the live page correctly, identify the right Amazon fields, recover from failures and keep the output stable enough for databases, dashboards, AI agents and monitoring systems.
For product-page extraction, this is often described as an Amazon product scraper API. Broader implementations add search results, seller storefronts, category pages, Best Sellers and other Amazon-native objects behind the same integration pattern.
Bot detection and access failures
CAPTCHAs, IP reputation, sessions and request volume can turn a working prototype into intermittent failures. A managed scraper API absorbs the access layer so your application does not have to operate proxy and browser infrastructure.
Dynamic and localized pages
Amazon pages can vary by marketplace, ZIP or postal code, delivery context and live rendering. Preserving that context matters because price, availability, delivery and search evidence may change with location.
Layout changes and parser drift
Amazon can change page structure without warning. Selectors that worked yesterday may silently lose fields tomorrow, so maintained parsers and field-level quality checks matter more than simply receiving an HTTP response.
Scale, retries and consistency
Recurring collection adds concurrency, retries, callback delivery and cost control. The useful metric is not whether one scrape succeeded, but whether the system can keep returning usable records as volume and frequency increase.
Use an API when current Amazon data belongs inside your product, data pipeline, monitoring system or AI workflow, but maintaining the crawling infrastructure is not the product you want to build. If your team needs complete control over browser behavior and is prepared to own proxy, anti-bot and parser maintenance, an in-house crawler can still be the better engineering choice.
A cheap response is expensive when your team cannot trust it
Choose the data layer by maintenance burden, Amazon depth and usable output—not by the first request price alone.
Generic scraper
Gets a page, but leaves Amazon-specific structure, ad detection and parser changes to your team.
- General-purpose extraction
- Schema built by you
- Amazon QA owned by you
Amazon-native data layer
Returns complete Amazon fields through maintained parsers, with marketplace, ZIP and sponsored-placement context.
- Six documented Amazon parsers
- Full Amazon field coverage
- 90%+ monitored SP capture
- JSON, Raw HTML or Markdown
In-house crawler
Maximum control, but every Amazon layout, proxy, CAPTCHA, retry and parser change becomes engineering work.
- Infrastructure ownership
- Continuous maintenance
- Longer time to usable data
Use the same API for an instant lookup or a data pipeline
Start synchronously, move long-running work to callback delivery, and choose the format that matches the next system in your workflow.
Send a request and receive the parsed result in the response. Ideal for validation, single-ASIN lookups and interactive applications.
Add bizContext.callbackUrl. Pangolinfo returns a task ID, then posts the parsed JSON result to your endpoint when it is ready.
Use structured JSON when you need parsed Amazon fields. Choose Raw HTML or Markdown when your own system will perform the next transformation.
Collect only when a current Amazon signal changes a decision
Use one data foundation across the workflows where freshness, field consistency and Amazon-specific context matter most.
Product research
Compare category density, price bands, BSR, rating depth and new-product momentum before committing inventory.
See product research workflow →Keyword and ad intelligence
Observe paid and organic placements together, then measure how visibility changes by keyword, market and delivery context.
Explore live search workflows →Rank and price monitoring
Record price, availability and ranking snapshots in your own database and act on meaningful movement.
See monitoring use case →Seller and catalog intelligence
Track visible assortment, category coverage and newly listed products across competitor storefronts.
View seller parser →AI and data products
Ground copilots, agents, BI tools and customer-facing products in live first-hand Amazon evidence.
Explore AI data solutions →Three predictable base plans, then tiered usage pricing
Test 60 real requests for $0. Start with one of three monthly plans, then scale through tiered usage pricing as volume grows.
Validate the data before you pay
Create an account, get an API key and test your real ASINs, keywords or categories. No credit card and no approval threshold.
9,600 Credits issued per billing month.
Choose Starter60,000 Credits issued per billing month.
Choose Professional240,000 Credits issued per billing month.
Choose ExpertTiered pricing applies as requests grow—without stopping at a package limit.
Calculate usage costPrices and credit rules shown here reflect the published plans at the time this page was prepared. The live Pricing page and account checkout govern current billing, overage tiers and plan terms.
Use the API when Amazon data belongs inside your product
Pangolinfo offers several delivery paths. The Scraper API is the right choice when your developers control the application, storage and downstream logic.
Build a product or pipeline
Call Amazon data from your backend, store it in your schema and control when every request runs.
YOU ARE HERETest the request →Give an AI agent live tools
Let MCP-compatible clients request Amazon evidence inside an agent workflow.
Explore Amazon Data MCP →Run guided analysis
Use a packaged Amazon research workflow when the user wants insight rather than raw integration.
Explore Amazon Scraper Skill →Monitor without building
Schedule collection and send structured Amazon data into team tables and operating workflows.
Explore AMZ Data Tracker →Amazon Scraper API FAQ
Answers on free testing, parsers, billing, review data and production use.
Can I test the Amazon Scraper API without paying?
Yes. Create an account and run the first 60 requests free. No credit card is required, and you can test your own ASINs, keywords, categories or seller IDs before choosing a plan.
What does “full Amazon field coverage” mean?
Pangolinfo parsers are designed around Amazon objects rather than a generic extraction schema. Depending on the parser and what Amazon displays, responses can include retail, offer, seller, fulfillment, variation, ranking, search-placement, content, media and delivery-context fields. Exact returned values depend on the live page, marketplace and availability.
Which Amazon pages can the main Scraper API collect?
The documented main endpoint supports six parser templates: product detail, keyword search, category products, seller products, Best Sellers and New Releases. It currently documents 13 marketplaces.
Is Amazon Review API included in this endpoint?
Review-page collection is offered as a separate Amazon Review API with its own review-specific parameters and 5-Credit-per-page billing. Use this Scraper API page for product, search, category, seller, Best Sellers and New Releases data, and visit the Review API page for large-scale review extraction.
How is the 90%+ sponsored-placement rate measured?
Pangolinfo monitors SP advertising-placement capture every day. The rate describes the system’s ability to identify sponsored placements present in monitored Amazon search results. Actual results can vary by keyword, marketplace, location and Amazon’s live delivery of ads.
How do base plans and usage-based pricing work together?
Starter, Professional and Expert are the three base monthly plans. They provide a predictable starting credit allocation. When workloads move beyond the base-plan range, tiered usage pricing applies according to the live formula on the Pricing page. This is not an unlimited flat subscription.
How many Credits does one request use?
The standard Amazon Scrape API uses 1 Credit per page for structured JSON and 0.75 Credit per page for Raw HTML or Markdown. Other APIs have different multipliers; for example, the separate Amazon Review API uses 5 Credits per page. Always check the live Pricing page for current rules.
Can I use synchronous and asynchronous delivery?
Yes. Use synchronous mode for a direct response. For asynchronous processing, provide bizContext.callbackUrl; the API returns a task ID and sends the structured result to your callback endpoint when complete.
Do I need my own proxies or CAPTCHA handling?
No. Pangolinfo manages access infrastructure, rendering, proxy rotation, anti-bot handling and Amazon-specific parsing. Your team defines what to collect and what to do with the returned data.
Can I target a marketplace and delivery location?
Yes. Send a documented site value and an optional matching bizContext.zipcode. Location matters because price, offer, availability and delivery signals may change by market and postal context.
Test live Amazon data before choosing a plan
Register, copy your API key and validate the fields that matter to your product. No credit card and no sales conversation required.
