Collect marketplace product signals from Amazon without building brittle storefront scrapers.
Structured output
Use Crawlora's Amazon endpoints to collect public product detail, search results, and keyword suggestions without maintaining Amazon-specific request handling, anti-bot challenge handling, parsers, normalization, billing, and developer documentation.
Marketplace workflows
Amazon product, search, and suggestion data can support price monitoring, availability tracking, catalog research, competitive analysis, and demand discovery when teams need repeatable structured data instead of brittle storefront scrapers.
Plan Amazon product monitoringRequest schema
These parameters come from the active Retrieve Amazon product details catalog entry.
| Parameter | Type | Required | Description | Example |
|---|---|---|---|---|
| asin | string | Yes | Amazon ASIN | B0DGJ736JM |
| language | string | No | Amazon language | - |
| currency | string | No | Amazon currency | - |
Example JSON
This example is rendered from the active endpoint catalog so the page stays aligned with Docs and Playground.
{
"code": 200,
"msg": "OK",
"data": {
"asin": "B0DGJ736JM",
"title": "Apple Watch SE (2nd Gen) [GPS 40mm]",
"link": "https://www.amazon.com/dp/B0DGJ736JM/",
"rating": 4.4,
"review_count": 1055,
"price": 189
}
}Endpoint catalog
/amazon/product/{asin}Returns normalized product details for an Amazon ASIN on `amazon.com`, including pricing, availability, overview data, inline review samples, and descriptive content.
/amazon/searchReturns normalized Amazon search result cards for `amazon.com`.
/amazon/suggest/{keyword}Returns typeahead keyword suggestions from Amazon's public suggestion API for `amazon.com`.
Managed execution
Crawlora wraps supported public Amazon pages behind API-key protected endpoints with managed anti-bot handling, normalized responses, documented errors, Playground examples, and credit-based usage.
“Robot Check” / CAPTCHA handling with Chrome-impersonated requests and browser escalation where needed
Proxy routing and request execution kept outside your application logic
Normalized product, search, and suggestion fields where available
Documented upstream failure behavior for blocked, malformed, not-found, or empty responses
Docs and Playground pages generated from the active endpoint catalog
Credit-based usage tied to backend billing weights, billed on successful calls
Build or buy
Use this comparison to decide whether to maintain scraping infrastructure internally or call a managed endpoint.
| Requirement | Building internally | Crawlora |
|---|---|---|
| Anti-bot handling | Maintain proxy rotation and solve Amazon “Robot Check” / CAPTCHA challenges yourself. | Use managed challenge handling with Chrome-impersonated requests and browser escalation. |
| Endpoint coverage | Build separate collectors for product, search, and suggestion pages. | Call documented Amazon product, search, and suggestion endpoints from one API surface. |
| Parser maintenance | Track Amazon page layout changes and empty-result edge cases. | Use endpoint-specific parsers maintained behind the Crawlora API. |
| Schema normalization | Design product, price, and review models yourself. | Receive normalized JSON examples and schemas in Docs and Playground. |
| Usage billing | Build your own metering and pricing model. | Use credit-based endpoint weights billed on successful calls. |
Crawlora is not affiliated with, endorsed by, or an official API of Amazon. Crawlora provides structured public web data extraction endpoints for supported public Amazon pages. If your use case requires account-scoped seller, advertising, or order data, use Amazon's official APIs (such as the Selling Partner API or Product Advertising API). Collect only public data, and ensure your use complies with applicable laws, third-party rights, Amazon's terms, and Crawlora terms.
Related APIs
Connect this endpoint with adjacent Crawlora search, monitoring, docs, and pricing pages.
Compare Crawlora with Rainforest API, a deep Amazon-only product data API now part of ScraperAPI.
OpenCollect eBay item, search, and seller data for resale and marketplace research.
OpenAdd Shop.app product and merchant data to marketplace workflows.
OpenPlan price, availability, and listing monitoring across many ASINs.
OpenPlan catalog research, pricing, and product discovery workflows.
OpenReview credit-based usage for Amazon and other marketplace endpoints.
OpenFAQ
Answers for developers evaluating Crawlora for supported public search result pages.
Send a product ASIN to Crawlora's Amazon Product endpoint, or a query to the Amazon Search endpoint. You get structured JSON — title, price, rating, review count, images, and availability — without writing parsers or rotating proxies. Collect only public data and respect Amazon's terms.
Amazon shows “Robot Check” CAPTCHAs to datacenter IPs. Crawlora's managed execution uses Chrome-impersonated requests and escalates to a real browser when needed, so the product page returns instead of a challenge. It does not log in or access private, account-scoped, or paywalled data.
No. Crawlora is not affiliated with Amazon and is not an official Amazon API. It provides structured public web data extraction endpoints for supported public Amazon pages. For account-scoped seller, advertising, or order data, use Amazon's official APIs.
The active catalog includes Amazon product detail by ASIN, Amazon search results, and Amazon keyword suggestions. Product responses include title, price, availability, rating, review count, images, and overview fields where available.
Yes. Product and search responses can support price tracking, availability monitoring, and competitive research where price, stock, rating, and listing fields are available. Schedule re-runs and pay only for successful fetches.
Collecting publicly accessible product data is generally permissible if you respect Amazon's terms of use, robots directives, rate limits, and applicable law. Crawlora is for collecting public data you are authorized to access, not private or account-scoped data.
Fetch an ASIN in Playground, inspect the current response schema in Docs, and compare credit-based usage on the pricing page.