Amazon Filter Trees, Parsed and Structured
Amazon filter pages are useful because they carry two things at once: the filter taxonomy (brand, price band, rating, feature, department) and the product list that the active filter set returns.
A managed scraping API can render that page, handle anti-bot measures, and hand back either HTML or structured JSON. This page explains what the API accepts, what it returns, how the credit model works, and where a managed approach fits versus a self-hosted one.
What a filter-tree request actually returns
The API takes an Amazon Filters URL plus your extraction logic. JavaScript rendering happens behind the scenes, and you receive clean structured output — either rendered HTML or JSON produced through extraction rules. The filter tree supplies the taxonomy; the product list supplies every item the active filter set returns. Typical jobs are product rankings, product variation data, and customer review trend analysis. The public page is the boundary: anything that renders there can be targeted, and post-login content should be left alone.
Request inputs and the options that change the result
You send the target URL by GET or POST. From there, the options you enable decide both the shape of the response and the credit cost. render_js turns on JavaScript rendering, stealth_proxy raises the anti-bot effort, country_code sets geo-targeting, and extract_rules or ai_extract_rules define the structured output. Use this map to pick the smallest configuration that still works for your job.
A worked credit comparison
Credit cost per request depends on which options are enabled. The published figures are: 5 credits for JS rendering, 25 for premium_proxy with JS, and 75 for stealth_proxy. Suppose you run 1,000 filter-page requests in a month. At 5 credits each (JS rendering only) that is 5,000 credits. At 75 credits each (stealth_proxy) the same 1,000 requests consume 75,000 credits — the entire Hobby plan allowance. The lesson is to enable stealth_proxy only for targets that actually push back, and to keep JS rendering on only where the page needs it. The plan table below shows the credit allowance and concurrency for each tier so you can match the configuration to the plan.
Blocked request vs. broken selector
Two failures look similar in a pipeline but need different fixes. A blocked request means the target refused the traffic — the response may be a CAPTCHA page, a 403, or an empty body. The fix is on the transport side: enable stealth_proxy, adjust country_code, or slow the request rate. A broken selector means the page loaded but your extraction rule no longer matches the elements you expected — the response is a valid page with missing or empty fields. The fix is on the extraction side: update the CSS or XPath rule, or switch to ai_extract_rules for a natural-language description of the fields. Check the response status and body shape before changing anything, so you fix the right layer.
When a managed API fits the job
A managed API is a good fit when you want to avoid running your own headless browser fleet and proxy pool, when you need JavaScript rendering and geo-targeting without building that infrastructure, and when you want structured output through extraction rules rather than hand-parsing HTML. It is a weaker fit when your job is a one-off page you can fetch directly, or when the target's terms of service prohibit the access you need. Review the target site's terms before deploying, and keep the scope to public-facing pages.
| Plan | Price | API credits | Concurrent requests | Priority support | Dedicated account manager | Team management |
|---|---|---|---|---|---|---|
| Hobby | $19 /mo | 75,000 | 25 | Not included | Not included | Not included |
| Freelance | $49 /mo | 250,000 | 50 | Not included | Not included | Not included |
| Startup (Recommended) | $99 /mo | 1,000,000 | 100 | Not included | Not included | Not included |
| Business | $249 /mo | 3,000,000 | 200 | Included | Included | Included |
| Business + | $599 /mo | 8,000,000 | 400 | Included | Included | Included |
| Enterprise 14 | $999 /mo | 14,000,000 | 500 | Included | Included | Included |
| Enterprise 24 | $1,599 /mo | 24,000,000 | 600 | Included | Included | Included |
| Enterprise 41 (Recommended) | $2,399 /mo | 41,000,000 | 700 | Included | Included | Included |
| Enterprise 69 | $3,599 /mo | 69,000,000 | 800 | Included | Included | Included |
| Enterprise 120 | $5,799 /mo | 120,000,000 | 900 | Included | Included | Included |
Prices exclude VAT. API credits are valid for one month and do not roll over. Requests start at 1 credit each; JS rendering, premium proxies, and stealth_proxy add credits per request. Check current pricing before committing to a plan.
| Configuration | Credits per request |
|---|---|
| Base request | 1 |
| JS rendering | 5 |
| Premium proxy without JS rendering | 10 |
| Premium proxy with JS rendering | 25 |
| stealth_proxy | 75 |
Credit costs are charged per successful request and depend on the options enabled. The figures above reflect the published credit model; confirm current rates before budgeting.
Frequently asked questions
Do I need an account to scrape Amazon filter data?
You do not need an Amazon account. You sign up for an API key, which comes with 1,000 free credits and no card requirement, then send the target URL. The API handles rendering and proxy rotation on its side.
Is scraping Amazon filter data legal?
Public-facing pages can usually be scraped, but the target site's terms of service govern what is allowed. Review those terms before deploying, and avoid any post-login content. This is general guidance, not legal advice.
What data can I extract from Amazon filter data?
Your reach is limited only by what the public page displays. To turn that into JSON, define field rules with CSS selectors through extract_rules, or describe the fields in plain language and let ai_extract_rules do the mapping. The filter tree itself carries brand, price band, rating, feature, and department taxonomy, plus the product list the active filter set returns.
How do I start scraping Amazon filter data?
Sign up, grab your API key, and send a GET request with the target URL. The API renders the page, rotates proxies, and returns the data. The 1,000 free credits let you test before choosing a plan.
Will I get blocked when scraping Amazon filter data?
The API rotates residential proxies and uses a real headless browser so requests resemble normal traffic. If a target becomes aggressive, enable stealth_proxy on the request. If the page loads but your fields are empty, the problem is the extraction rule, not the block.
How much does it cost to scrape Amazon filter data?
Signup includes 1,000 free credits with no card required. Paid plans start at $19/month for higher volume and concurrency. Per-request cost depends on options: 5 credits for JS rendering, 25 for premium_proxy with JS, and 75 for stealth_proxy. Credits are valid for one month and do not roll over.
Can I get the filter tree and the product list in one request?
Yes. The filter tree and the product list both render on the same public page, so a single request with the right extraction rules can capture both. If you need different fields from each, define separate rules within the same request rather than issuing two calls.
Should I use extract_rules or ai_extract_rules?
Use extract_rules when you know the CSS or XPath selectors and want deterministic, repeatable output. Use ai_extract_rules when the page structure changes often or you want to describe fields in natural language. The AI route is more flexible but less predictable, so it suits exploratory or fast-changing targets.