Skip to content

Amazon URL Scraper API for Product Page Data

Amazon product pages combine server-rendered markup with JavaScript-driven modules and bot defenses.

OUTPUT FORMATSHTMLJSONMarkdown

A hosted scraper API moves the browser fleet, proxy rotation, and rendering work off your client so your code can focus on the URL list and the fields you need. This guide explains what the API accepts, how to choose an extraction mode, and where the common failure points sit.

What the API does with an Amazon URL

You send a public Amazon product URL plus your API key. The service loads the page in a real browser, rotates the outbound IP, and returns the response your scraper can act on. Because the browser work happens server-side, your application does not need to maintain a headless Chrome pool or a proxy vendor relationship.

The same request can return raw HTML, structured data via CSS or XPath rules, AI-extracted JSON, a screenshot, or Markdown. The choice depends on whether you need exact selectors, flexible natural-language extraction, or a visual record of the page.

Three common Amazon research workflows

Most Amazon URL jobs fall into one of three shapes:

  • Price trend tracking. Collect the displayed price and availability on a schedule, then compare movements across a category or competitor set.
  • Specification comparison. Pull structured attributes such as dimensions, materials, or compatibility to map competitor offerings and spot gaps.
  • Bundle analysis. Capture what is grouped together in a product bundle so you can evaluate positioning and profitability.

Each workflow needs a different field list, but they share the same request pattern: a URL plus extraction rules that name the elements you want.

Choosing an extraction mode

Start with CSS/XPath rules when the page structure is predictable. Switch to AI extraction when selectors break often or when the field is easier to describe in words than to locate in the DOM.

Request controls and what they change

  • render_js=true runs the page in a real headless browser and returns the post-render HTML. Use it when product modules or pricing widgets appear only after JavaScript executes.
  • stealth_proxy adds a stronger proxy layer for targets that respond aggressively to automated traffic.
  • country_code routes the request through a chosen country or territory so the page reflects that locale.
  • extract_rules accepts CSS or XPath selectors and returns structured JSON.
  • ai_extract_rules accepts natural-language field descriptions and returns structured JSON.

These controls are independent: you can combine rendering, stealth, geotargeting, and extraction in one request.

Telling failures apart

A blank or partial result usually comes from one of three causes, and each has a different fix:

  1. JavaScript did not run. The HTML contains placeholders or empty containers. Confirm render_js=true is set and that the page does not require interaction before the data appears.
  2. The request was blocked. You see a CAPTCHA page, a bot-check interstitial, or an unusual status code. Enable stealth_proxy and retry; if the block persists, reduce request rate or change the target locale.
  3. The selector missed. The page rendered but your field is empty. Inspect the post-render HTML and update the CSS or XPath rule, or move that field to ai_extract_rules.

Separating these causes prevents wasted retries against a page that is actually rendering correctly.

Worked example: price and specification from one product URL

Suppose you have a public Amazon product URL and want two fields: the displayed price and the item weight.

  1. Send the URL with render_js=true so the price widget is populated.
  2. Add an extract_rules object with a CSS selector for the price container and another for the weight row in the specification table.
  3. If the weight row moves between page variants, replace that selector with an ai_extract_rules description such as "item weight from the product details section."
  4. Store the returned JSON with the request timestamp and the source URL so later comparisons remain traceable.

This pattern scales to a list of URLs: the same rules apply to each product page, and only the URL changes per request.

Matching plan limits to your workload

Plans differ on monthly API credits, concurrent requests, and support level. JavaScript rendering consumes 5 credits per successful request, and premium proxies consume 10 or 25 credits depending on whether rendering is also enabled. Credits are valid for one month and do not roll over.

A practical check: multiply your expected monthly page count by the per-request credit cost of the features you plan to use, then compare that total with the plan's credit allowance. Concurrency matters separately: it caps how many requests can be in flight at once, which affects how quickly a large URL list can be processed.

Plan comparison (captured reference)
PlanPriceAPI CreditsConcurrent requestsPriority Email SupportDedicated Account ManagerTeam Management
Hobby$19 /mo75,00025Not includedNot includedNot included
Freelance$49 /mo250,00050Not includedNot includedNot included
Startup$99 /mo1,000,000100Not includedNot includedNot included
Business$249 /mo3,000,000200IncludedIncludedIncluded
Business +$599 /mo8,000,000400IncludedIncludedIncluded
Enterprise 14$999 /mo14,000,000500IncludedIncludedIncluded
Enterprise 24$1,599 /mo24,000,000600IncludedIncludedIncluded
Enterprise 41$2,399 /mo41,000,000700IncludedIncludedIncluded
Enterprise 69$3,599 /mo69,000,000800IncludedIncludedIncluded
Enterprise 120$5,799 /mo120,000,000900IncludedIncludedIncluded

Prices are exclusive of VAT. Credits are valid for one month and do not roll over. JavaScript rendering costs 5 credits per successful request; premium proxies cost 10 or 25 credits depending on whether rendering is enabled. This table reflects a captured reference period and should be checked against current plan terms before purchase.

Choosing an extraction mode
ModeBest forWhat you supplyWhat you get back
Raw HTMLCustom parsing already in placeURL onlyPost-render HTML
CSS/XPath extraction rulesStable, known page structureSelectors per fieldStructured JSON
AI extraction rulesChanging layouts or natural-language field descriptionsField descriptionsStructured JSON
ScreenshotVisual verification or archivalURL and viewport optionsImage
MarkdownLLM-ready text inputURLClean Markdown

Frequently asked questions

Is scraping Amazon legal?

Pages that are openly accessible to anyone can generally be collected, but check the site's terms of service first and keep your jobs away from anything behind a login. Legal review of your specific use case remains your responsibility.

What data can I extract from Amazon?

Any field that appears on the publicly rendered page. You can target elements with CSS selectors through extract_rules, or describe the fields in plain language with ai_extract_rules; either path returns structured JSON.

How do I start scraping Amazon?

Sign up, grab your API key, and send a GET request with the target URL. The service renders the page, rotates proxies, and returns the data. 1,000 free credits are available to test.

Will I get blocked when scraping Amazon?

Requests are routed through rotating residential proxies and a genuine headless browser, which makes them resemble ordinary visitor traffic. When a target tightens its defenses, turn on stealth_proxy for that request.

Can I scrape Amazon without writing code?

Yes. The dashboard request builder lets you paste a URL, set parameters, and copy the generated snippet in Python, Node, Go, PHP, Ruby, or cURL.

How do I handle JavaScript when scraping Amazon?

Pass render_js=true on the request. The service runs the page in a real headless browser, executes the JavaScript server-side, and returns the post-render HTML.

How do I avoid wasting credits on failed requests?

Test your selectors and rendering settings against a small URL sample first. Because JavaScript rendering and premium proxies each consume multiple credits per successful request, confirming the request shape before scaling up keeps credit use predictable.