Shopee product data scraping
Returns title, category path, images, description, attributes, variations and the item and shop identifiers. Use it to build competitor catalogues, audit listing quality or match the same product across sellers.
Pull Shopee listings, prices, seller scores and reviews into your own systems with one REST call. Compare the same product across Singapore, Malaysia, Indonesia, Thailand, Vietnam and the Philippines in each local currency, and keep watch on competitors, stock levels and promotions without running scrapers yourself.
# Request (replace the key and link with your own)
POST https://api.webfusiondata.com/v1/product
Authorization: Bearer $WFD_API_KEY
{ "url": "https://shopee.sg/product/123456789/9876543210",
"country": "SG" }
# Response (sample data, not a live listing)
{
"item_id": "9876543210",
"shop_id": "123456789",
"marketplace": "SG",
"title": "Example Air Fryer 4L",
"price": { "amount": 59.90, "currency": "SGD" },
"sold": 1200,
"rating": 4.8,
"stock": 85,
"seller": { "name": "Example Store", "rating": 4.9 }
}
Sample values for illustration only. Exact field names and nesting for your Shopee scope are confirmed in the API reference issued with your key.
Shopee is one of the largest online marketplaces in Southeast Asia, with thousands of independent sellers competing on price, shipping and reputation. A Shopee data scraping API returns what a Shopee product, shop or search page shows as structured JSON. You send a product link, a keyword or a shop and item ID, choose a country, and receive named fields such as price, units sold, rating, stock and seller details.
Shopee data is especially useful because every listing combines product, seller and social-proof signals: variations with their own prices and stock, a sold count, ratings, vouchers and a shop profile. Our collection layer handles rendering, proxies, bot checks, parsing and validation, so your team works with clean records instead of raw HTML.
Brands use it to police pricing across sellers, sellers use it to watch rivals, and analysts use it to compare demand across Southeast Asian markets. Our price monitoring and price intelligence services build on the same kind of data.
Six steps from choosing a market to acting on the results.
Decide which Shopee countries you cover and what you track: individual products, whole shops, keywords or categories.
Shortlist the fields that matter, such as price, sold count, stock per variation or shop rating.
Pass a product link, or a shop ID and item ID, in url. For discovery, use site and query. Add country for the market.
Pick /v1/product, /v1/search, /v1/monitor or /v1/bulk to suit the job.
Send your API key as a bearer token in the Authorization header.
Test in the sandbox first so you can confirm field mapping before spending live request credits.
We load the page for the chosen market, parse variations, price ranges, seller blocks and review summaries, and validate each field.
Large lists run asynchronously. Follow progress with /v1/status/:job_id or receive a webhook.
JSON is the default, and bulk exports can be CSV or XLSX. Every record carries a crawled_at timestamp.
Shopee prices and stock can change several times a day during campaigns, so timestamps are what make comparisons trustworthy.
Feed repricing rules, seller scorecards, review analysis or market-entry dashboards.
See Integration and Data Delivery for a worked example.
The main things you can do with Shopee data, and which are already documented versus agreed per project.
Returns title, category path, images, description, attributes, variations and the item and shop identifiers. Use it to build competitor catalogues, audit listing quality or match the same product across sellers.
Captures price, price before discount, discount percentage and currency, including the price range of multi-variation items. Monitors can alert you when a price drops or a promotion starts.
Returns stock status and, where shown, stock per variation, so you can spot sell-outs, restock patterns and thin inventory on competitor listings.
Returns shop name, shop rating, followers, chat response metrics, join date and badges such as Mall or Preferred where displayed, so you can rank sellers on more than price.
Returns the overall rating, star breakdown and review count, with review text, star level, date and purchased variation available as a project option.
Search a keyword or collect a rival shop’s listings, then compare prices, discounts and sold counts side by side to see who is undercutting whom and how quickly.
The country parameter selects the Shopee market, so you can compare price levels, demand signals and assortments across the region in local currencies.
Returns the units-sold figure and similar popularity counts where shown, a quick proxy for demand when you do not have access to a seller’s own sales data.
Schedule monitors, receive webhook callbacks and export bulk jobs to CSV, XLSX or cloud storage, so fresh Shopee data arrives without manual pulls.
The fields returned for Shopee listings and shops, what each contains and how teams use it. Availability follows what the page shows for the selected market.
| Data Field | Description | Business Application | Availability |
|---|---|---|---|
item_id / shop_id | Shopee item and shop identifiers taken from the product link | Matching, de-duplication, shop-level grouping | Core |
title | Listing title in the page language | Catalogue and keyword analysis | Core |
category | Category path shown on the listing | Category benchmarking | Core |
price.amount / price.currency | Current price in the market currency, with a minimum and maximum for multi-variation items | Price comparison, repricing inputs | Core |
price_before_discount / discount | Original price and discount percentage | Promotion and markdown analysis | Where displayed |
variations | Model options such as colour, size or bundle, each with its own price and stock | Variant pricing and stock tracking | Where displayed |
stock / availability | Stock status, and quantity where exposed | Availability monitoring | Core |
sold | Units sold figure shown on the listing | Demand estimation, sales velocity | Where displayed |
rating / review_count | Average star rating, star breakdown and number of ratings | Quality benchmarking | Where displayed |
reviews (text) | Review text, stars, date and purchased variation | Sentiment and NLP pipelines | Confirm at onboarding |
seller.name / seller.rating | Shop name and shop rating | Seller scorecards | Where displayed |
seller.followers / seller.response | Follower count and chat response metrics | Seller performance analysis | Where displayed |
seller.badge | Mall, Preferred or similar seller badge | Seller tiering | Where displayed |
vouchers / shipping | Voucher messages, free-shipping flags and ships-from location | Landed-price comparison | Where displayed |
product_url / marketplace | Listing link and the Shopee market it came from | Reference and validation | Core |
crawled_at | Timestamp of data capture | Freshness checks, time series | Core |
Core = part of the standard field set on our ecommerce API. Where displayed = returned when the Shopee page for that market shows it, so it can be empty for some listings or shops. Confirm at onboarding = settled per project. Images are also returned. Field names are illustrative; your API reference is the source of truth.
Shopee requests use the shared versioned endpoints of the Ecommerce Scraping API. Shopee-specific parameter names that are not yet published are marked.
| Endpoint | Purpose | Parameters | Expected response |
|---|---|---|---|
POST /v1/productDocumented |
One Shopee listing with price, variations, stock, sold count, rating and the seller block. | Required: urlOptional: country; separate shop_id and item_id fields are a confirm |
One JSON product record, returned synchronously. |
POST /v1/searchDocumented |
Keyword or category search on Shopee, returned as a ranked result list for competitor and market scans. | Required: site ("shopee"), queryOptional: country |
JSON with query, result_count and a results array. |
POST /v1/monitorDocumented |
Track a listing for price, stock and promotion changes, with webhook alerts. | Required: urlOptional: webhook URL and check frequency names: confirm |
A monitor ID you use to read tracked data later. |
GET /v1/monitor/:idDocumented |
Current values and change history for one tracked listing. | Required: id (path) |
JSON with the latest values and recorded changes. |
POST /v1/bulkDocumented |
Process a large list of item links asynchronously, for example a competitor’s full range. | Required: list of URLs Optional: delivery destination and format (JSON, CSV or XLSX) names: confirm |
A job ID, then results via webhook or storage export. |
GET /v1/status/:job_idDocumented |
State and progress of an asynchronous crawl or bulk export. | Required: job_id (path) |
JSON with job state and progress. |
| Situation | Typical HTTP status | How to fix it |
|---|---|---|
| Missing or malformed Shopee link | 400 | Send a full product link on a Shopee market domain, including https://, or the shop and item ID form your account supports. |
| Country does not match the link | 400 / 422 | Match country to the domain, such as SG for shopee.sg or TH for shopee.co.th. |
| Missing or invalid API key | 401 | Send Authorization: Bearer <key> and check the key belongs to the right environment (sandbox or live). |
| Listing deleted or unavailable | 404 or an empty record | Sellers remove listings often. Confirm the link still loads in a browser and drop dead items from your watchlists. |
| Request limit exceeded | 429 | Wait, then retry with backoff. Response headers show your remaining quota for the window. |
| Temporary processing failure | 5xx | Retry with exponential backoff, and use /v1/bulk for large lists instead of many synchronous calls. |
Status codes follow common REST conventions (429 is the one shown in our published dashboard example). The exact codes and error bodies are listed in the API reference supplied with your key.
Two common Shopee calls and what comes back. Illustrative sample data — not live marketplace information.
curl -X POST https://api.webfusiondata.com/v1/product \
-H "Authorization: Bearer $WFD_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"url": "https://shopee.sg/product/123456789/9876543210",
"country": "SG"
}'
curl -X POST https://api.webfusiondata.com/v1/search \
-H "Authorization: Bearer $WFD_API_KEY" \
-d '{"site": "shopee", "query": "air fryer", "country": "SG"}'
url or site + query select what to fetch; country selects the Shopee market. Keep the key in an environment variable — never hard-code it or ship it in client-side code.{
"item_id": "9876543210",
"shop_id": "123456789",
"marketplace": "SG",
"title": "Example Air Fryer 4L",
"price": { "amount": 59.90, "currency": "SGD" },
"price_before_discount": 79.90,
"discount": { "percent": 25 },
"stock": 85,
"sold": 1200,
"rating": 4.8,
"review_count": 560,
"seller": {
"name": "Example Store",
"rating": 4.9,
"followers": 15200,
"badge": "Mall"
},
"crawled_at": "2026-01-15T09:30:00Z"
}
{
"query": "air fryer",
"result_count": 60,
"results": [
{ "title": "Example Air Fryer 4L", "price": 49.90,
"sold": 3400, "rating": 4.7 }
]
}
Search results return a lighter record than the product call, so use /v1/product when you need variations, stock and seller detail. The final Shopee schema is confirmed in your API reference.
Shopee runs a separate site in each country, with its own currency, language and sellers. Select one with the country parameter. We do not claim coverage beyond what is confirmed at onboarding.
| Market | Shopee domain | Local currency | Status for the API |
|---|---|---|---|
| Singapore | shopee.sg | SGD | Confirm at onboarding |
| Malaysia | shopee.com.my | MYR | Confirm at onboarding |
| Indonesia | shopee.co.id | IDR | Confirm at onboarding |
| Thailand | shopee.co.th | THB | Confirm at onboarding |
| Vietnam | shopee.vn | VND | Confirm at onboarding |
| Philippines | shopee.ph | PHP | Confirm at onboarding |
This is a reference list of Shopee’s Southeast Asian markets, not a coverage guarantee. Need another region, such as Taiwan or Brazil? Tell us and we will confirm feasibility.
Why it matters: prices are only comparable once currencies are aligned, and each market has its own campaign calendar, including the double-date sales, so compare records captured on the same day. Titles and descriptions appear in local languages, so tell us if you need translation or normalised categories for cross-market analysis.
What is published today, and what we give you in writing before you go live. We do not publish numeric limits, latency or uptime figures on this page.
| Topic | How it works | Status |
|---|---|---|
| Authentication | Your API key is sent as a bearer token in the Authorization header. Use the sandbox key while testing. | Documented |
| Limits and concurrency | Per-minute limits and concurrent requests scale with your plan, and response headers show remaining quota. Campaign days drive traffic spikes on Shopee, so agree volume and refresh frequency ahead of them and use /v1/bulk for large lists. | DocumentedNumbers: your plan |
| Validation and errors | Missing or malformed parameters are rejected with a standard HTTP error (see Endpoints), and responses are schema-checked before delivery. | Exact codes: API reference |
| Timeouts and retries | Set a client timeout and retry reads on 429 and 5xx with exponential backoff. Move long work to /v1/bulk and /v1/status/:job_id, and avoid blind retries of POST /v1/monitor or /v1/bulk. | Recommended practice |
| Pagination | Search returns a result_count and a result list. How deep you can page for large keywords is scoped per project. | Confirm at onboarding |
| Usage monitoring | An account dashboard shows request volume, latency, success rate and job status. | Documented |
Send Shopee data to a repricing engine, a seller scorecard or a regional BI dashboard. The pattern is always a request layer, a store for results and a schedule.
Agree markets, products or shops, fields and refresh frequency, then test a few listings in the sandbox.
Keep authentication, timeouts and retry backoff in one small module that every Shopee job reuses.
Save price, stock and sold count per item, shop and market with each crawled_at, so you can derive sales velocity and price history.
Use monitors for key listings, bulk jobs for full ranges, and webhooks to trigger price, stock or seller alerts.
import os, sqlite3, requests
API = "https://api.webfusiondata.com/v1/product"
HEADERS = {"Authorization": f"Bearer {os.environ['WFD_API_KEY']}"}
def fetch(shop_id, item_id, country="SG"):
url = f"https://shopee.sg/product/{shop_id}/{item_id}"
r = requests.post(API, json={"url": url, "country": country},
headers=HEADERS, timeout=60)
r.raise_for_status()
return r.json()
db = sqlite3.connect("shopee_snapshots.db")
db.execute("CREATE TABLE IF NOT EXISTS snapshots "
"(item_id TEXT, shop_id TEXT, price REAL, sold INT, stock INT, at TEXT)")
for shop_id, item_id in [("123456789", "9876543210")]:
p = fetch(shop_id, item_id)
db.execute("INSERT INTO snapshots VALUES (?, ?, ?, ?, ?, ?)", (
p["item_id"], p["shop_id"], p["price"]["amount"],
p.get("sold"), p.get("stock"), p.get("crawled_at"),
))
db.commit()
Default response format for every endpoint.
Bulk exports of whole ranges or search runs, delivered as CSV or XLSX to S3, GCS or your own bucket.
Callbacks when a job finishes or a tracked price or stock value changes, plus recurring checks through /v1/monitor.
Managed warehouse connectors, client libraries and no-code paths.
Listed on the Ecommerce Scraping API page; availability for your Shopee scope is confirmed during onboarding. See also the AI Parser and ecommerce datasets. Related: product availability and MAP monitoring.
It is a REST API from WebFusion Data that returns structured JSON for Shopee listings, shops and search results. You send a product link or a keyword and a country, and receive fields such as price, stock, sold count, rating and seller details. It runs on the same endpoints and infrastructure as our Ecommerce Scraping API, so you do not manage proxies, browsers or parsers.
Core fields include item and shop IDs, title, category, price and currency, stock status, images, listing link, market and a capture timestamp. Discount, variations, sold count, rating, review count, vouchers and shipping details are returned where the page displays them. Review text and other advanced fields are agreed per project. The data fields table lists each one.
Yes, through the product link. Shopee listings are identified by a shop ID and an item ID, so you can build the product link from those two numbers and submit it to /v1/product with the right country. Both IDs are returned in the response so you can match records. Whether separate shop_id and item_id parameters are available is confirmed at onboarding.
Yes. POST /v1/monitor registers a listing for scheduled price and stock checks with webhook alerts, and GET /v1/monitor/:id returns the latest values and change history. Check frequency is scoped to your project, which matters on campaign days when prices change quickly. History starts from the day you register a listing, so store each crawled_at timestamp if you want your own time series.
Stock status is returned for each listing, and stock per variation is included where the page shows it. Teams use this to spot sell-outs, track restocks and see which competitor listings are running low. Quantity figures depend on what Shopee displays for that item, so some listings return a status only.
Where displayed, the response includes shop name, shop rating, follower count, chat response metrics, join date and badges such as Mall or Preferred. Combined with price and sold count, this lets you build seller scorecards and compare competitors on reliability as well as price. The exact metric list is confirmed for your scope.
The overall rating, star breakdown and review count are returned where displayed. Review text, star level, date and purchased variation can be scoped as a project option for sentiment analysis and product research, and whether review images are included is confirmed at onboarding. We collect only publicly visible reviews.
We do not claim blanket coverage. The country parameter selects the market, and the Shopee sites available to you, such as Singapore, Malaysia, Indonesia, Thailand, Vietnam and the Philippines, are confirmed during onboarding. Tell us which markets you need and we will confirm each one. See supported markets.
Each request carries your API key as a bearer token in the Authorization header, and every account includes a sandbox. Keep the key on your server and out of client-side code. JSON is the default format, and bulk exports can be CSV or XLSX delivered to S3, GCS or your own bucket. See Integration and Data Delivery.
Use the Request API Demo button or the form below and tell us the markets, products or shops, fields, refresh frequency and delivery format you need. We confirm the scope and set up access, including the sandbox. You can also email sales@webfusiondata.com or book a consultation.

At WebFusionData, we specialize in cutting-edge web scraping solutions to help you unlock valuable insights and drive business growth. Whether you need custom data extraction, real-time monitoring, or large-scale web scraping, our team is here to assist you.
Ready to get started? Contact us for a personalized quote.