Amazon Offers Scraper API: One Request for the Whole Offer Box
An Amazon product page's offer box is where the buying decision actually lives: which sellers are on the listing, at what price, in what condition, and with what shipping cost.
That data sits behind JavaScript rendering and active bot detection, so a plain HTTP client usually returns an empty or blocked page. A hosted scraping API moves the browser, proxy rotation and fingerprint handling off your infrastructure and returns the post-render HTML or structured data from a single call. This page explains what you send, what comes back, how credits are consumed, and how to choose a plan before you build.
What the API actually does
You give the service an Amazon offer-listing URL and your API key. The service opens the page in a real headless browser, executes the page's JavaScript, rotates proxies and spoofs fingerprints so the request resembles ordinary traffic, then returns the rendered page. Your code stays a thin HTTP call — no browser fleet, no proxy pool, no CAPTCHA handling on your side. The same endpoint can also return parsed data when you supply extraction rules, or AI-driven extraction when you describe the fields you want in natural language.
What you can pull from an offer listing
Offer-listing pages expose, for a given ASIN, the full set of sellers and their terms. In practice teams use this for three jobs:
- Price collection — competitor pricing, lead generation and market positioning.
- Promotional detail capture — deal terms, coupons and promotional offers that affect effective price.
- Shipping cost capture — logistics and landed-cost comparison.
Because the page is rendered before it is returned, the seller rows, condition labels and shipping lines are present in the response rather than missing from a pre-render snapshot.
Request inputs and what each one changes
The core request is a GET with your API key and the target URL. Optional parameters change how the page is fetched:
- render_js — runs the page in a headless browser and returns post-render HTML. Needed for offer boxes that populate client-side.
- stealth_proxy — routes the request through stealthier proxies when a target is aggressive about blocking.
- country_code — routes through a residential IP in the chosen country, useful when offers or pricing vary by geography.
- extract_rules — CSS or XPath selectors that pull structured fields out of the rendered page.
- ai_extract_rules — natural-language field descriptions for AI-driven extraction when selectors are brittle.
A dashboard request builder lets you paste a URL, set parameters and copy a generated snippet in Python, Node, Go, PHP, Ruby or cURL, so you can start without writing the request by hand.
A worked example: one ASIN, one call
Suppose you want every seller row for a single ASIN. You build the offer-listing URL for that ASIN, then send one GET request with your API key, the URL, render_js set to true, and country_code set to the marketplace you care about. The response is the post-render HTML of the offer box. From there you either parse the seller rows yourself or attach extract_rules that target the seller name, price, condition and shipping cells.
Credit math: a request with JS rendering enabled costs 5 API credits. A Premium-proxy request costs 10 credits without JS rendering, or 25 credits with it. So a JS-rendered request on a Premium proxy is 25 credits. At the Hobby plan's 75,000 credits, that is 3,000 such requests per month; at the Startup plan's 1,000,000 credits, it is 40,000. Credits are valid for one month and do not roll over.
Telling failures apart
Three failure modes look similar but need different fixes:
- Blocked or CAPTCHA page — the response is a challenge page, not the offer box. Enable stealth_proxy on the request.
- Empty or partial offer box — the page loaded but the seller rows were not populated. Confirm render_js is true; if it already is, the page may need a JS scenario that scrolls or clicks before extraction.
- Wrong marketplace data — prices or sellers look like a different country. Set country_code to the marketplace you want.
If the target throttles aggressive patterns, space out requests or use multiple sessions; the API applies concurrency limits per plan rather than per-target rate limits.
Choosing a plan
Plans differ on three axes that matter for offer scraping: monthly API credits, concurrent requests, and whether priority support, a dedicated account manager and team management are included. Every plan includes JavaScript rendering, rotating and premium proxies, geotargeting, and screenshots and extraction rules. The jump from Startup to Business is where priority email support, a dedicated account manager and team management appear. If you need more credits or concurrency than the largest listed plan, contact sales. A free trial with 1,000 credits and no credit card is available to size your workload before committing.
SDKs and stack fit
Official SDKs cover Python, Node.js, Go, PHP, Ruby and Java, and raw cURL examples are provided alongside them. Each scrape becomes a single function call in the SDK, so the integration surface is small. If your team prefers no-code automation, the API can be driven from n8n workflows; if you want LLM-ready output, the Markdown scraper returns page content in a clean structured format.
| Plan | Price / mo | API credits | Concurrent requests | Priority email support | Dedicated account manager | Team management |
|---|---|---|---|---|---|---|
| Hobby | $19 | 75,000 | 25 | Not included | Not included | Not included |
| Freelance | $49 | 250,000 | 50 | Not included | Not included | Not included |
| Startup (Recommended) | $99 | 1,000,000 | 100 | Not included | Not included | Not included |
| Business | $249 | 3,000,000 | 200 | Included | Included | Included |
| Business + | $599 | 8,000,000 | 400 | Included | Included | Included |
| Enterprise 14 | $999 | 14,000,000 | 500 | Included | Included | Included |
| Enterprise 24 | $1,599 | 24,000,000 | 600 | Included | Included | Included |
| Enterprise 41 (Recommended) | $2,399 | 41,000,000 | 700 | Included | Included | Included |
| Enterprise 69 | $3,599 | 69,000,000 | 800 | Included | Included | Included |
| Enterprise 120 | $5,799 | 120,000,000 | 900 | Included | Included | Included |
Prices are exclusive of VAT. Credits are valid for one month and do not roll over. Requests start at 1 credit each; JS rendering adds 5 credits per successful request; Premium proxies cost 10 or 25 credits depending on whether JS rendering is enabled. All plans include JavaScript rendering, rotating and premium proxies, geotargeting, and screenshots and extraction rules.
Frequently asked questions
How do I start scraping Amazon Offers?
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 Offers?
Requests rotate residential proxies and use a real headless browser, so they look like normal traffic. If a target gets aggressive, enable stealth_proxy on the request.
Can I scrape Amazon Offers 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 Offers?
Pass render_js=true on the request. The page runs in a real headless browser, the JS executes server-side, and the post-render HTML is returned.
Can I scrape Amazon Offers from a specific country?
Yes. Add country_code to the request and the call exits through a residential IP in that nation. Reach for it whenever the offer set or pricing shifts from one market to another.
What's the rate limit for scraping Amazon Offers?
Throttling comes from the concurrency allowance attached to your plan; there is no separate per-site ceiling. When a site pushes back on fast, repetitive traffic, slow the cadence or distribute the work over several sessions.