Skip to content

Amazon Seller Profiles, Pulled at Scale

Amazon seller pages mix server-rendered text with JavaScript-driven widgets and sit behind active bot detection.

OUTPUT FORMATSHTMLJSONMarkdown

This page explains how a managed scraping endpoint handles the rendering and proxy layer so your code only has to send a URL and read back HTML or structured JSON.

What the endpoint does for you

You send a public Amazon seller URL plus your API key. The service renders the page in a real headless browser, routes the request through rotating or premium proxies, and returns the post-render HTML. If you supply extraction rules, it returns parsed JSON instead.

That division of labour matters because the hard parts of seller scraping are not the parsing — they are the browser fleet, the proxy pool and the anti-bot response. Keeping those off your side means your client stays a thin HTTP call rather than a maintenance project.

Typical reasons teams reach for this: collecting seller feedback for competitor analysis, tracking product pricing over time, and watching inventory levels for supply-chain decisions.

Field map: what public seller pages expose

Two groups of data come back from the same endpoint, and it helps to keep them separate when you design your schema.

Seller-level fields (from the public seller profile): business name and address, storefront URL, feedback rating, lifetime feedback count, return policy, and the active product catalog.

Product-level fields (from the catalog and product pages): prices, ratings, inventory levels, SKUs and product metadata.

A practical consequence: if you only need seller reputation, one profile call per seller is enough. If you need price or stock history, plan a per-product crawl and budget credits accordingly, because each product page is its own request.

Request options and when to use them

The advanced parameters are the part most teams get wrong on the first build. A short control map:

  • render_js=true — run the page in a headless browser and return post-render HTML. Use it whenever the data you need is injected by JavaScript.
  • country_code — route through a residential IP in that country. Use it when the seller page or catalog differs by marketplace.
  • extract_rules — map CSS selectors to field names and receive parsed JSON.
  • ai_extract_rules — describe the fields in natural language instead of writing selectors; the response is parsed JSON.
  • stealth_proxy — the higher-cost proxy tier for pages that block ordinary requests.
  • premium_proxy — a mid-tier proxy option, priced differently depending on whether JS rendering is enabled.

Start with the cheapest combination that returns the fields you need, then escalate one option at a time when a page fails.

Worked credit example

Per-request credit cost varies with the options you turn on. The reference figures are: 1 credit for a plain request, 5 credits when JS rendering is enabled, 25 credits for premium_proxy together with JS rendering, and 75 credits for stealth_proxy. Treat these as planning inputs and confirm them against current documentation before committing a budget, since pricing terms can change: [credit validity and rollover terms to be confirmed]. A worked example makes the spread concrete: a 1,000-seller feedback sweep that needs JS rendering lands near 5,000 credits, while the same sweep on stealth_proxy lands near 75,000 credits. That difference is the argument for sampling a small batch first and escalating to stealth only where the cheaper tier genuinely fails. Match your plan to expected monthly volume rather than to a single one-off batch, and leave headroom for retries and failed pages.

Telling failures apart

Three different problems look similar in a log but need different fixes:

  1. Empty or partial content — the page loaded but the data is client-rendered. Fix: enable JS rendering.
  2. Wrong marketplace content — the seller exists but the catalog or currency does not match. Fix: set country_code.
  3. Blocked or throttled responses — the request was refused or rate-shaped. Fix: escalate the proxy tier, and space out requests; the API applies concurrency limits per plan rather than per-target rate limits, so aggressive patterns can still be throttled by the target itself.

Diagnosing which of the three you are hitting before changing parameters saves both credits and debugging time.

Getting to a first request

The workflow is four steps: create an account to get an API key and starting credits; install an SDK or use raw cURL; send a seller URL to the endpoint; then add advanced parameters as needed. SDKs are published for Python, Node.js, Go, PHP, Ruby and Java, and plain cURL works for any stack.

If you would rather not write code at all, the same endpoint can be driven from n8n workflows, and the platform also offers AI extraction, screenshots, JavaScript scenarios, Markdown output and a Google search API as adjacent capabilities.

Decision checklist before you commit

  • Do you need seller reputation only, or product-level price and stock as well? The second case multiplies request volume, because each product page is its own request. - Is your target marketplace the default one? If not, plan for country_code from day one rather than retrofitting it later. - Have you measured how many pages actually need stealth_proxy versus plain JS rendering? The credit difference is large enough to change which plan makes sense. - Does your monthly volume fit inside a credit allowance that expires each month? Confirm the validity and rollover terms before you size the plan: [credit validity and rollover terms to be confirmed]. - Do you need structured JSON, or is post-render HTML enough for your own parser? - Will you call the endpoint directly, or through an automation tool such as n8n?
Plan comparison (reference figures)
PlanMonthly priceAPI creditsConcurrent requestsPriority supportAccount 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. JavaScript rendering, rotating and premium proxies, geotargeting, and screenshots/extraction rules are included on every plan. The figures in this table are reference values for planning and should be re-checked against current pricing before purchase. Price and credit values are subject to confirmation: [plan prices and credit allowances to be confirmed].

Frequently asked questions

How do I handle JavaScript when scraping Amazon Seller data?

Set render_js=true on the request. The page is executed in a real headless browser server-side, and you receive the post-render HTML rather than the raw source.

Can I scrape Amazon Seller data from a specific country?

Yes — pass country_code to route the request through a residential IP in that country. This matters when seller pages or catalogs differ by marketplace.

What's the rate limit for scraping Amazon Seller data?

Limits are applied per plan as concurrency caps, not as per-target rate limits. If the target itself throttles aggressive request patterns, space requests out or use multiple sessions.

How do I get structured JSON from Amazon Seller data?

Either map CSS selectors to field names with extract_rules, or describe the fields in natural language with ai_extract_rules. Both return parsed JSON in the response.

Which programming languages can I use to scrape Amazon Seller data?

Any language that can make an HTTP request. Published SDKs cover Python, Node.js, Go, PHP, Ruby and Java, and plain cURL works for everything else.

How much does it cost to scrape Amazon Seller data?

Free-credit and starting-plan terms are set by the operator and should be confirmed before you rely on them: [free-credit allowance and starting-plan terms to be confirmed]. Per-request cost depends on the options you enable: 5 credits for JS rendering, 25 for premium_proxy with JS, and 75 for stealth_proxy. A plain request starts at 1 credit.

Is seller feedback the same as product reviews?

No. Seller feedback is attached to the seller account and reflects the buying experience — shipping, accuracy, service. Product reviews are attached to individual listings. Both can be collected, but they come from different pages and therefore different requests.