Skip to content

Amazon Best Sellers Scraper API: Request Parameters, Credits and Output

Bestseller lists change constantly, and the pages that hold them are built by client-side scripts and can differ by storefront.

OUTPUT FORMATSHTMLJSONMarkdown

This page is a practical reference for teams that want to feed an Amazon Best Sellers URL into a single-request scraping API: the shape of the request, the parameters that genuinely alter the response, how credits price a recurring pull, and the decisions the API leaves to you.

How a Best Sellers request is built

The flow is four steps. First, create an account; the API key and the starting credit allowance are issued immediately. Second, install a client for your stack — Python, Node, Go, PHP or Ruby — so each scrape becomes one function call rather than a browser farm you operate. Third, send a GET request carrying your API key and an Amazon Best Sellers URL on amazon.com. The service renders JavaScript, rotates residential proxies and returns rendered HTML ready to parse. Fourth, reach for advanced parameters only when the page needs them: render_js for script-built content, stealth_proxy when a target tightens its checks, country_code for geo-specific content, and ai_extract_rules for natural-language extraction instead of hand-written selectors. Treat the first three steps as the default path and the fourth as a per-target adjustment.

Three tracking jobs this fits

Most bestseller work falls into three shapes. Collecting product ratings supports competitor comparison: you can see which listings carry strong review signals and where your own catalogue sits relative to them. Capturing bestseller rankings supports positioning: repeated snapshots show movement within a category and let you track rivals over time. Extracting product descriptions supports messaging work: the feature lists and copy that top listings use become a reference for your own listings. Each shape is the same request with a different parsing target, so the pipeline can share one client and one credit budget.

Request parameters that change the output

Four parameters do most of the work, and each maps to a distinct failure. If the returned HTML is missing content that appears in a browser, the page was not rendered: pass render_js=true and the service runs the page in a real headless browser, executes the scripts server-side and returns post-render HTML. If requests start coming back challenged, enable stealth_proxy so traffic is routed through residential proxies that resemble normal visitors. If the leaderboard looks like the wrong marketplace, pass country_code to route through a residential IP in that country — useful whenever content varies by geography. If you would rather describe the fields you want than write selectors, ai_extract_rules takes a natural-language extraction instruction. Throughput is a separate matter: the API enforces concurrency limits per plan, not per-target rate limits, so if a target throttles aggressive patterns, space requests out or spread them across sessions.

What a request costs

Credits are consumed per successful request and the base rate is one credit. Enabling JavaScript rendering raises a successful request to five credits. Enabling premium proxies costs ten credits, or twenty-five when JS rendering is also on — the 25-credit premium-proxy rate already includes JS rendering, so the two charges do not stack. Credits are valid for one month and do not roll over, so a budget is really a monthly ceiling. Geotargeting reaches 200+ countries and territories, or 40+ on classic proxies. Team management lets an organization invite multiple users and assign each a custom quota of credits and concurrency, which is how a shared monitoring budget stays attributable. Worked example: a job that pulls 500 bestseller pages a day with JS rendering and premium proxies costs 500 × 25 = 12,500 credits per day, or roughly 375,000 credits over a 30-day month — enough to make the plan tier, not the per-request price, the decision that matters.

Before you point this at a category

Run through this before scheduling anything. Confirm the exact category URL you intend to poll and that it resolves on amazon.com. Decide whether the fields you need are present in the initial HTML or only after scripts run; that single answer decides whether render_js is on for every request or only some. Pick the marketplace with country_code if the leaderboard must match a specific storefront. Prototype in the dashboard request builder first — paste the URL, set parameters, and copy the generated snippet in Python, Node, Go, PHP, Ruby or cURL — then move that snippet into your codebase. Finally, estimate monthly credits from your page count and parameter mix before you commit to a plan tier.

What the API does not decide for you

The service handles rendering, proxy rotation and anti-bot friction, but it does not choose your polling cadence, your parsing schema or your retention policy. Concurrency is capped by plan, so a monitor that needs many parallel category pulls should be sized against the plan's concurrent-request allowance rather than assumed to scale freely. On data handling, the published position is that the service does not collect or store personal data from scraped sites unless the user explicitly requests it; any compliance statement on your own page should be confirmed with the provider rather than inferred from this description. Before publishing a compliance claim, decide what your own policy actually promises: whether you retain raw HTML, how long parsed records live, and who reviews deletion requests. A useful worksheet is to list each data category you collect, the lawful basis you rely on, the retention period, and the named owner of that decision. Treat any statement about the provider's data handling as something to verify directly with them, not as a fact this page can establish.

Published plan tiers: credits, concurrency and included features
PlanPriceAPI creditsConcurrent requestsJS renderingRotating & premium proxiesGeotargetingScreenshots & extraction rulesPriority email supportDedicated account managerTeam management
Hobby$19 /mo75,00025IncludedIncludedIncludedIncludedNot includedNot includedNot included
Freelance$49 /mo250,00050IncludedIncludedIncludedIncludedNot includedNot includedNot included
Startup (Recommended)$99 /mo1,000,000100IncludedIncludedIncludedIncludedNot includedNot includedNot included
Business$249 /mo3,000,000200IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Business +$599 /mo8,000,000400IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 14$999 /mo14,000,000500IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 24$1,599 /mo24,000,000600IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 41 (Recommended)$2,399 /mo41,000,000700IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 69$3,599 /mo69,000,000800IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 120$5,799 /mo120,000,000900IncludedIncludedIncludedIncludedIncludedIncludedIncluded

These are the plan values captured from the original product page on 2026-11-15 and are shown here as external reference, not as an offer from this page. All prices exclude VAT. Confirm current pricing, credit allowances and concurrency limits with the provider before purchase. If you are comparing tiers, build a small worksheet: list your expected monthly page count, the parameters each request needs, and the resulting credit total, then check that figure against each tier's allowance and concurrent-request cap.

Frequently asked questions

How do I start scraping Amazon Best Sellers?

Create an account to receive an API key and the starting credit allowance, then send a GET request with your API key and the target Amazon Best Sellers URL. The service renders the page, rotates proxies and returns the data. The published starting allowance is 1,000 free credits for testing. Before you rely on any free-credit figure, confirm the current allowance and its expiry terms directly with the provider, since trial terms can change.

Will I get blocked when scraping Amazon Best Sellers?

Requests are routed through rotating residential proxies and a real headless browser, so traffic resembles ordinary visitors. If a target gets aggressive, enable stealth_proxy on the request as the escalation toggle.

Can I scrape Amazon Best Sellers without writing code?

Yes. The dashboard request builder lets you paste a URL, set parameters and copy a generated snippet in Python, Node, Go, PHP, Ruby or cURL. You still need somewhere to run that snippet, but you do not need to write the request by hand.

How do I handle JavaScript when scraping Amazon Best Sellers?

Pass render_js=true on the request. The page runs in a real headless browser, scripts execute server-side, and you receive the post-render HTML rather than the initial source. Note that JS rendering raises a successful request to five credits.

Can I scrape Amazon Best Sellers from a specific country?

Yes. Pass country_code on the request to route through a residential IP in that country. This matters when the leaderboard or product content differs by marketplace.

What's the rate limit for scraping Amazon Best Sellers?

There is no per-target rate limit. The API enforces concurrency limits per plan instead. If a target throttles aggressive patterns, space requests out or spread them across multiple sessions.