Send a keyword, ASIN, seller ID, deal ID, or category and get structured JSON back. No brittle Amazon parsing layer, no custom request mapping across separate tools.
What this actually means
You sign up for ScrapingBot, get an API key, call the Amazon endpoint family, and receive structured Amazon data for catalog discovery, PDP enrichment, review mining, seller intelligence, and deals monitoring.
100 free credits to validate the workflow before you scale it.
# Open a product page by ASIN
curl -X POST "https://scrapingbot.io/api/v1/amazon" \
-H "x-api-key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"endpoint": "/product-details",
"params": {
"asin": "B07ZPKN6YR",
"country": "US"
}
}'
{
"asin": "B07ZPKN6YR",
"product_title": "Apple AirPods Pro",
"product_price": "$189.99",
"currency": "USD",
"product_byline": "Visit the Apple Store"
}
Keyword
Search discovery
Product lookup
PDPs, reviews, offers
Seller / deal ID
Seller and deal endpoints
Category
Discovery and browsing
How It Works
The flow is simple: create your account, choose the Amazon endpoint you need, send the input you already have, and store the JSON response.
Sign up once, get your API key, and test the Amazon API from the docs or dashboard playground before wiring it into production.
Use a keyword, ASIN, seller ID, category, promo code, or deal ID depending on whether you are doing discovery, PDP analysis, seller research, or promotions tracking.
Push the response into dashboards, pricing monitors, review analysis pipelines, seller tracking jobs, or internal tooling.
Free trial: Start with 100 free credits so you can validate the Amazon integration end-to-end before upgrading.
Endpoints
Use the same request pattern across search, product pages, reviews, seller data, deals, and category browsing.
Search Amazon by keyword and get product collections you can use for assortment research, competitor discovery, and pricing snapshots.
Enumerate category trees and fetch products by category when you need broader catalog context than a single keyword query provides.
Open an ASIN and retrieve the product detail page state you need for titles, pricing, brand context, attributes, and marketplace metadata.
Pull review streams and top reviews for sentiment analysis, defect tracking, feature requests, or competitor comparisons.
Go beyond the PDP with offer data, seller profiles, seller reviews, and seller product listings for marketplace monitoring.
Watch current deals, resolve products inside deal pages, and inspect promo-code pages when you need Amazon discount intelligence.
Need endpoint-by-endpoint details? Read the documentation or the full Amazon scraping guide.
Typical Workflow
Most teams start with search or category discovery, enrich the products they care about, then pull reviews, offers, or seller data depending on the workflow.
Start with /search for keyword-driven discovery or use /products-by-category when you already know the browse area.
This is where teams shortlist ASINs, brands, or categories worth deeper monitoring.
Use /product-details, /product-offers, and seller endpoints to capture PDP context, offers, and storefront metadata.
This is the stage where pricing, assortment, and seller dynamics become visible.
Pull /product-reviews for voice-of-customer work, /deals-v2 for promotions, or /asin-to-gtin for downstream catalog mapping.
This is the point where the Amazon data usually flows into dashboards, data warehouses, or alerting systems.
Good for pricing monitoring
Track product price shifts, offer mix, and seller changes over time.
Good for review analytics
Store ratings and review text for sentiment, QA, or product intelligence work.
Good for MVPs
Test the workflow with the playground before building production jobs around it.
Why ScrapingBot
The hard part is not sending a request. It is keeping multiple Amazon page types and workflows consistent over time. ScrapingBot gives you a packaged API surface so you can focus on the product or workflow you actually want to build.
Build and maintain it yourself
Use ScrapingBot instead
Use Cases
The API is flexible enough for internal tooling, recurring monitoring jobs, and productized ecommerce workflows.
Monitor catalog pages, open individual ASINs, and compare offer or seller changes across the products that matter to your market.
Pull review pages to detect sentiment trends, frequent complaints, feature requests, or emerging quality issues faster.
Resolve seller storefronts, inspect seller feedback, and enumerate seller product catalogs for marketplace research workflows.
Monitor current deal pages, fetch products inside promotions, and browse categories when you need broader catalog movement signals.
FAQ
These are the common questions from teams evaluating the Amazon API for the first time.
Depending on the endpoint, you can send a keyword, ASIN, seller ID, deal ID, promo code, category identifier, country, language, and other endpoint-specific params.
Yes. New accounts start with free credits so you can validate the request shape, inspect the returned JSON, and decide whether it fits your workflow before upgrading.
Yes. The Amazon API ships with dedicated docs, a guide article, and a dashboard playground so you can test requests live without building your own harness first.
Not entirely. Search, reviews, seller endpoints, and deals can return different top-level shapes. That is why the playground and docs are built around endpoint-specific examples rather than pretending every response has the same schema.
Open the playground, try the example requests, and validate the Amazon workflow with free credits before you scale usage.
Prefer docs first? Jump to Amazon docs.