Skip to content

Amazon Vendor Scraper API: Public Vendor Page Data as JSON

Amazon Vendor pages are the storefronts shoppers see, and the sold-by label on each one is the fastest way to tell a vendor-fulfilled SKU from a third-party listing.

OUTPUT FORMATSHTMLJSONMarkdown

This API takes a public Amazon Vendor product URL, renders the page, rotates proxies, and returns either the HTML or a structured JSON payload you define. The page below covers what the tool does, what it cannot do, how credits are charged, and how to plan a run before you commit to a plan.

What this API does

You hand over a public Amazon Vendor product URL. The service fetches the page with a real headless browser, rotates residential proxies so the request looks like ordinary traffic, and returns the rendered HTML or a JSON payload shaped by your extraction rules. That replaces the manual routine of opening hundreds of SKUs one at a time to check price and availability.

Three jobs come up most often. First, separating vendor-fulfilled SKUs from third-party listings by reading the sold-by field, which is the basis for market-share analysis. Second, tracking availability across a competitor set so stock signals feed inventory decisions. Third, collecting customer feedback — ratings and review text — to inform product and merchandising choices. Each of these is a public-page read; none of them requires a Vendor Central login.

From URL to structured JSON in four steps

  1. Create an account. You get an API key and 1,000 free credits to test with, no card required.
  1. Install a client. Python, Node, Go, PHP and Ruby SDKs are available, so a single page fetch becomes one function call — no proxy pool or headless Chrome to run yourself.
  1. Send the request. Pass any public Amazon Vendor URL to the endpoint with your API key. The service handles rendering and bot bypass and returns parsed HTML or structured JSON.
  1. Add parameters only when you need them. render_js turns on JavaScript rendering, stealth_proxy raises the anti-block level for aggressive targets, country_code sets the geotarget, and ai_extract_rules lets you describe the fields you want in natural language instead of writing selectors. If you prefer explicit selectors, extract_rules takes CSS or XPath rules and returns the same structured JSON shape.

Fields you can pull from a public Vendor page

The page-level fields below are the ones the source documents as parseable in a single call. Treat them as the target schema for your extraction rules; anything not rendered on the public page is out of scope.

Where the tool stops: public pages vs. Vendor Central

This is a public-page scraper. It reads what a shopper would see on the Amazon storefront — sold-by attribution, listed price, availability, ratings, A+ content, brand store link. It does not log into Vendor Central, does not touch post-login dashboards, and does not return retail-readiness reports, purchase orders or any account-scoped data. If your task needs those, this API is not the right tool and no amount of parameter tuning will change that.

Before you build, run this checklist:

  • Confirm every URL in your list resolves to a public product page, not a login wall.
  • Confirm the fields you need actually render on that page (some A+ modules are region-specific).
  • Confirm your use is permitted under the target site's terms of service; public-facing pages can usually be scraped, but review the terms before deploying.
  • Confirm your credit budget against the per-request cost table below before scheduling a large run.

How credits are charged, and a worked example

Credits are consumed per successful request and depend on which options you enable. A plain request starts at 1 credit. Enabling JS rendering costs 5 credits. Premium proxies cost 10 credits without JS rendering or 25 with it. stealth_proxy costs 75 credits. Credits are valid for one month and do not roll over. Plan prices and credit tiers below are the owner's current published figures; confirm them on the pricing page before purchase.

Worked example: suppose you monitor 1,000 SKUs once a day and every page needs JS rendering plus a premium proxy. That is 25 credits per request × 1,000 requests = 25,000 credits per day, or roughly 750,000 credits per month. The 1,000,000-credit tier covers that with headroom; the 250,000-credit tier does not. If you can drop the premium proxy on most pages and keep only JS rendering, the same run costs 5,000 credits per day — about 150,000 per month — and fits comfortably in the smaller tier. Run the math against your own SKU count and option mix before choosing a plan.

Three failure modes and what to check first

Not every bad result is a block. Distinguish these before you change parameters:

  • HTTP error or challenge page. The request was rejected. Check whether stealth_proxy is enabled and whether the target needs a different country_code. This is the only case where raising the anti-block level helps.
  • Empty or partial extraction. The request succeeded but your selectors matched nothing. The page probably rendered a different layout, or the field is region-specific. Re-check the selector against the returned HTML before assuming a block.
  • Wrong sold-by attribution. The page loaded and parsed, but the sold-by value looks off. This is usually a stale page or a marketplace variant, not a scraping failure. Verify the URL resolves to the marketplace you expect and re-fetch before treating it as a data-quality bug.
Public Vendor page field map
FieldWhat it tells youTypical use
Sold-byWhether the SKU is sold directly by Amazon (Vendor Central) or by a third-party sellerVendor vs. 3P split for market-share analysis
MAP priceMinimum advertised price enforced on the listingPrice-compliance monitoring
MSRPManufacturer suggested retail priceDiscount-depth benchmarking
Brand store URLLink to the brand's Amazon storefrontBrand-level rollups and storefront audits
A+ contentThe full enhanced-content block on the product pageCreative and merchandising comparison
Warranty infoWarranty terms shown on the listingPost-purchase and support analysis

Fields reflect what the source documents as parseable from public Amazon Vendor product pages in a single call; availability of any individual field depends on what renders on the target page.

Per-request credit cost by option
Request configurationCredits per successful request
Plain request (no options)1
JS rendering enabled5
Premium proxy, JS rendering disabled10
Premium proxy, JS rendering enabled25
stealth_proxy75

Credits are valid for one month and do not roll over. Per-request credit costs are fixed by the option mix; plan prices and credit tiers are the owner's current published figures and should be confirmed on the pricing page before purchase.

Frequently asked questions

Do I need an account to scrape Amazon Vendor data?

You do not need an Amazon Vendor account. You do need an API key from this service: sign up, get 1,000 free credits with no card, send the URL, and the service handles the rest.

Is scraping Amazon Vendor data legal?

Pages that anyone can view without signing in are generally fair game to collect, though you should still read the target site's terms of service before you deploy and steer clear of anything behind a login. This is general guidance, not legal advice.

What data can I extract from Amazon Vendor data?

Whatever the public page actually renders. Point extract_rules at CSS selectors, or let ai_extract_rules handle AI-driven extraction, and you get structured JSON back.

How do I start scraping Amazon Vendor data?

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. You get 1,000 free credits to test.

Will I get blocked when scraping Amazon Vendor data?

Requests go out through rotating residential proxies from a genuine headless browser, which keeps them looking like ordinary traffic. When a target turns aggressive, switch on stealth_proxy for that request.

How much does it cost to scrape Amazon Vendor data?

You get 1,000 free credits on signup with no card required. Paid plans start at $19/month for higher volume and concurrency. Per-request credit cost depends on options: 5 credits for JS rendering, 25 for premium_proxy with JS, and 75 for stealth_proxy. Plan prices and credit tiers are the owner's current published figures; confirm them on the pricing page before purchase.