Skip to content

Shopee Product and Review Scraper API

A hosted Shopee scraping API is useful when you want public product data without running your own headless browsers or proxy pool.

OUTPUT FORMATSHTMLJSONMarkdown

You send a Shopee URL plus your extraction logic; the service renders JavaScript, rotates proxies, and returns either structured JSON or rendered HTML. This page explains what comes back, which request options change the result and the credit cost, and how to tell the difference between a blocked request and an extraction rule that simply found nothing.

What a Shopee product page returns

For a public Shopee product page, the returned field set is: SKU, brand, price, discount tier, stock state, seller rating, review count, and the full image gallery. Those fields support the three workflows most teams start with — price intelligence, per-SKU stock tracking, and seller-quality research. The response format is your choice: structured JSON when you want to load the data directly, or rendered HTML when you want to parse it yourself. The same call can also return a full-page screenshot or a Markdown version of the page for LLM pipelines.

Three workflows that fit this field set

Price tracking. Pull competitor prices, discount tiers, and observed price drops per SKU to feed a pricing dashboard or promo tracker. Stock monitoring. Track stock state and restock cadence per SKU for supply-side modeling and merchandising decisions. Seller research. Collect seller ratings, response rate, and total review counts per shop to compare seller quality across a category. Each workflow uses the same request shape; the difference is which fields you extract and how often you schedule the call.

Choosing an extraction mode

There are four practical ways to get data out of a rendered Shopee page. Pick based on how stable the page structure is and how much control you want over the output shape.

  • Structured JSON with CSS or XPath extraction rules. Best when you know the page layout and want a fixed schema. You define selectors once and the API returns matching fields.
  • AI extraction rules. Best when the layout shifts or you want to describe fields in natural language instead of maintaining selectors. You send a spec and get structured JSON back.
  • Rendered HTML. Best when you want to parse the page yourself, run your own post-processing, or archive the raw markup.
  • Markdown. Best when the next step is an LLM that reads product text rather than a database that stores typed fields.

A useful rule of thumb: if you will query the data repeatedly, prefer structured JSON; if you will inspect the page visually, take a screenshot; if you will feed a language model, use Markdown.

Request options and what they change

The request options are the main lever on both output and credit cost. In plain terms:

  • JavaScript rendering changes the page from raw HTML to a browser-rendered result and has its own credit cost.
  • Premium or stealth proxies change how requests are routed and have their own credit cost, which depends on whether JS rendering is also enabled.
  • Geotargeting changes the apparent country of the request, which matters when Shopee shows different prices or availability by market.
  • Screenshots and extraction rules change the output shape rather than the page fetch.
  • Team management and support tiers are plan-level features, not per-request options.

Before you build a scheduler, estimate the per-request credit cost for the combination you actually need, not just the base request. Exact per-request credit rules: 5 credits for JS rendering, 25 for premium_proxy with JS, and 75 for stealth_proxy.

Worked example: one SKU through a price-and-stock check

Suppose you track a single SKU across a week. On day one you request the product page with JS rendering and an extraction rule that returns SKU, price, discount tier, stock state, seller rating, and review count. You store the result keyed by SKU and date. On day two you repeat the call. If the price field is present but the stock field is empty, that is an extraction-rule miss, not a blocked request — the page rendered but your selector did not match. If the whole response is a challenge page or an empty body, that is a fetch-level failure and the fix is at the request level (proxy or rendering options), not the selector level. Keeping those two failure types separate in your logs saves a lot of debugging time.

Blocked request vs. empty extraction

A blocked request usually shows up as a challenge page, a CAPTCHA, or a response that does not contain the product markup at all. An empty extraction shows up as a valid page response where one or more of your target fields are missing. The first is a request-configuration problem; the second is a selector or spec problem. Check the raw response before changing your extraction rules, and check your extraction rules before changing your proxy settings. Mixing the two up is the most common cause of wasted credits.

Setup path

Setup follows four steps: create an account and get an API key with free starter credits; install an SDK for your stack (Python, Node.js, Go, PHP, Ruby, or Java) or use plain cURL; send one HTTP call with your API key and a Shopee URL; and add advanced parameters only when the page needs them. A dashboard request builder lets you test without writing code. Code samples exist for every major language, so you can start in whatever stack you already use.

Pricing context

The plan table below runs from a low-volume hobby tier through enterprise tiers, with API credits, concurrent requests, and feature inclusions varying by plan. Prices and credit allowances are first-party commercial terms: {{OWNER_PRICING_TABLE}} and {{OWNER_FREE_CREDIT_OFFER}}. The per-request credit cost depends on which options you enable, not just on the plan tier, so pair any plan comparison with a request-option estimate. Cancellation terms are also first-party: {{OWNER_CANCELLATION_TERMS}}.

Plan reference
PlanPriceAPI creditsConcurrent requestsPriority supportAccount managerTeam management
Hobby$19 /mo75,00025Not includedNot includedNot included
Freelance$49 /mo250,00050Not includedNot includedNot included
Startup (Recommended)$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 (Recommended)$2,399 /mo41,000,000700IncludedIncludedIncluded
Enterprise 69$3,599 /mo69,000,000800IncludedIncludedIncluded
Enterprise 120$5,799 /mo120,000,000900IncludedIncludedIncluded

Prices are exclusive of VAT. All figures are a reference and should be checked against current pricing before use. JavaScript rendering, rotating and premium proxies, geotargeting, and screenshots/extraction rules are included on every plan shown.

Frequently asked questions

Do I need a Shopee account to use the scraper?

No. You sign up for an API key, send the public Shopee URL, and the service handles the fetch. The free starter credit allowance is a first-party offer: {{OWNER_FREE_CREDIT_OFFER}}.

Is scraping Shopee legal?

Public-facing pages can usually be scraped, but review the target site's terms of service before deploying and avoid post-login content. This is general guidance, not legal advice for your jurisdiction or use case.

What data can I extract from Shopee?

Anything that renders on the public page. Use CSS or XPath extraction rules for a fixed schema, or AI extraction rules to describe fields in natural language and get structured JSON back.

How do I start scraping Shopee?

Sign up, get an API key, and send a GET request with the target URL. The service renders the page, rotates proxies, and returns the data. The free starter credit allowance for testing is a first-party offer: {{OWNER_FREE_CREDIT_OFFER}}.

Which programming languages can I use?

Any. SDKs are published for Python, Node.js, Go, PHP, Ruby, and Java, and plain cURL works too. Pick whatever your stack already uses.

How much does it cost to scrape Shopee?

The free starter credit allowance and the paid plan prices are first-party commercial terms: {{OWNER_FREE_CREDIT_OFFER}} and {{OWNER_PRICING_TABLE}}. Per-request credit cost depends on options: 5 credits for JS rendering, 25 for premium_proxy with JS, and 75 for stealth_proxy.

Why did my extraction return empty fields?

An empty field usually means the page rendered but your selector or AI spec did not match the current markup. A blocked request looks different: you get a challenge page or a response with no product markup at all. Check the raw response before changing extraction rules, and check extraction rules before changing proxy settings.