Shopee Seller & Shop Intelligence Scraper
Pricing
$5.00 / 1,000 dataset items
Shopee Seller & Shop Intelligence Scraper
Get Shopee seller & shop profiles from product URLs, shop URLs, IDs or usernames in any Shopee region: shop name, ID, rating, rating count, followers and logo, plus listings, badges and account signals when Shopee's shop API answers. Structured JSON for lead-gen and seller research.
Pricing
$5.00 / 1,000 dataset items
Rating
0.0
(0)
Developer
axly
Maintained by CommunityActor stats
0
Bookmarked
35
Total users
18
Monthly active users
18 hours
Issues response
6 days ago
Last modified
Categories
Features
Share
Turn any Shopee shop link, ID, or username into a seller profile: shop name, username, shop ID, exact rating and rating count, followers and logo, plus the full profile (listings, rating breakdown, badges, account signals, dates) whenever Shopee's shop API answers. Clean, structured JSON for lead generation, seller vetting, and marketplace competitor intelligence.
Feed it product URLs, shop/storefront URLs, bare shop IDs, or usernames. Works across Shopee storefronts (Indonesia, Singapore, Malaysia, Thailand, Vietnam, Philippines, Brazil, Taiwan; Mexico accepted as input). No login, no CAPTCHA solving, no request signing.
Status (November 2026): Shopee now refuses its shop API (HTTP 418) in every region unless the request carries the app's signature. With the default
dataSource: autothe actor checks the API once per run and, while it is refused, reads each shop's public shop page instead. Those rows carry the fields marked "page" below (profileSource: "shop_page"). The full API profile (profileSource: "shop_api") comes back automatically if Shopee reopens the API.
Who it's for
- Lead-gen agencies & B2B sales — build seller lists with ratings, review volume and follower counts for outreach.
- Brands & brand-protection teams — find and vet resellers of your products and monitor their reputation.
- Marketplace analysts & researchers — study the Shopee seller landscape: rating distribution and review volume across shops.
- Dropshippers & sourcing teams — qualify suppliers by rating and review volume.
What you get — output fields
Each row is one Shopee shop. "page" = returned from the public shop page (current default path); "API" = returned only when Shopee's shop API answers.
| Field | Type | Source | Description |
|---|---|---|---|
shopId | integer | page, API | Shop ID (page: from the shop URL or its product links; omitted for a shop with no listed products looked up by username) |
username | string | page, API | Storefront username |
name | string | page, API | Shop display name |
region | string | page, API | Shopee region (e.g. co.id) |
shopUrl | string | page, API | Canonical storefront URL |
ratingStar | number | page, API | Average rating, 0–5 |
ratingCount | integer | page, API | Total ratings |
avatarUrl | string | page, API | Shop logo / avatar image URL |
followerCountText | string | page | Followers as Shopee displays them (rounded, e.g. 4,8RB, 59.9k, 5.1萬) |
followerCountApprox | integer | page | That display value as a number (e.g. 4,8RB → 4800); approximate |
followerCount | integer | API | Exact followers |
profileSource | string | page, API | shop_page or shop_api |
userId | integer | API | Owner user ID |
description | string | API | Shop description (if any) |
followingCount | integer | API | Accounts the shop follows |
itemCount | integer | API | Number of live listings |
ratingGood / ratingNormal / ratingBad | integer | API | Rating breakdown |
responseRate / responseTimeSeconds | integer | API | Chat response rate (%) and time; only for shops where Shopee returns them |
isOfficialShop / isShopeeVerified | boolean | API | Official Shop / Shopee-verified badges |
isPreferredPlusSeller / isShopeeChoiceShop | boolean | API | Preferred+ / Shopee Choice badges |
isSeller | boolean | API | Account is a seller |
phoneVerified / emailVerified | boolean | API | Contact verification signals |
facebookId | string | API | Linked Facebook ID (when public) |
sellerAvgStar | number | API | Seller average star |
createdAt / lastActiveAt | string | API | Shop creation / last active (UTC) |
status / onVacation | mixed | API | Shop status code, vacation flag |
scrapedAt | string | page, API | Scrape timestamp (UTC) |
Fields are omitted when the source doesn't return them (never coerced to 0).
Not currently returned (since 25 Oct 2026): cancellationRate,
preparationTimeSeconds, shopLocation, country, isCrossBorder,
showsPreferredBadge and updatedAt. They came from Shopee's get_shop_detail
endpoint, which now requires a signed request.
High-value use cases
- Build a seller outreach list — collect shops with ratings, review volume and followers, then filter to your ideal partners.
- Vet a supplier before you buy — check rating and review volume in seconds instead of clicking through pages.
- Track competitor sellers — snapshot ratings, review counts and followers on a schedule to watch who's growing.
- Brand protection — monitor the shops that carry your brand and their reputation.
- Market research — quantify seller quality across a Shopee region for reports and dashboards.
Input parameters
| Parameter | Type | Default | Description |
|---|---|---|---|
shops | array of strings | — (required) | Shop identifiers: product URL, shop URL, /shop/<id> URL, bare shop ID, or username |
region | enum | co.id | Region for bare IDs/usernames (full URLs carry their own host) |
dataSource | enum | auto | auto (shop API, else public shop page), shopPage, or shopApi (fails while Shopee gates the API) |
maxItems | integer | 1000 | Stop after this many profiles |
maxRetries | integer | 4 | Total attempts per request; 0 = single attempt, no retries, no backoff |
stopOnBlock | boolean | false | Abort the whole run on the first CAPTCHA / 401 / 403 / 418 / 429 of the selected source, with no fallback IP or proxy (in auto, the one-time API check does not count) |
proxyConfiguration | proxy | disabled | Optional Apify proxy (neither source needs one) |
Each shops entry accepts any of:
https://shopee.co.id/<slug>-i.88053496.8152544433(product URL → shop)https://shopee.co.id/shop/88053496https://shopee.co.id/windowfashionsurabaya(storefront URL)88053496(bare shop ID) orwindowfashionsurabaya(username)
Example input
{"shops": ["windowfashionsurabaya","https://shopee.co.id/shop/125118269","88053496"],"region": "co.id","maxItems": 100}
Example output row (public shop page)
{"shopId": 125118269,"username": "tittanium1","name": "Titanium","region": "co.id","shopUrl": "https://shopee.co.id/tittanium1","followerCountText": "6,9RB","followerCountApprox": 6900,"ratingStar": 4.49,"ratingCount": 62620,"avatarUrl": "https://mms.img.susercontent.com/id-11134233-7r98z-lqjb1mxeg2e684","profileSource": "shop_page","scrapedAt": "2026-11-08T07:19:31+00:00"}
When the shop API answers, rows have profileSource: "shop_api" and add the API
fields from the table above (exact followerCount, itemCount, rating breakdown,
badges, account signals, createdAt, lastActiveAt).
Scheduling & integrations
- Schedule runs (hourly/daily/weekly) from the Apify Console to keep seller metrics fresh.
- Webhooks can trigger on run completion to push new data downstream.
- Export to JSON, CSV, Excel or feed Google Sheets, Make, Zapier, Airbyte or Amazon S3 via the Apify API and integrations.
- Pull results directly from the dataset API into your own app or warehouse.
Use it from an AI agent (MCP)
This actor works with the Apify MCP server, so AI assistants (Claude, ChatGPT,
Cursor, VS Code) can call it as a tool — "get the Shopee profile for shop
windowfashionsurabaya" — and receive structured seller data back. Point your MCP
client at Apify and enable this actor.
FAQ
Which data is included? Shop/seller profile data only (see the field table: on the public-shop-page path that is name, username, shop ID, rating, rating count, followers as displayed and logo). Individual product listings and reviews are not part of this actor.
What requests does it make? Do I need a login, cookies, or a proxy? No login,
cookies or proxy. Per run, in auto mode:
- one
GET https://mall.shopee.<tld>/api/v4/shop/get_shop_basewith the Shopee Android app's headers (no cookies, no signature). If Shopee answers it, every shop is read this way. - while Shopee refuses that call, one
GET https://shopee.<tld>/<username>(or/shop/<id>) per shop with a link-preview User-Agent (WhatsApp/2.23.20.0), the request a chat app makes to show a link preview. Shopee answers it with a server-rendered shop header, which the actor parses.
dataSource: shopApi uses only request 1; dataSource: shopPage only request 2.
A proxy is optional if you want a specific egress region.
Which regions are supported? All Shopee storefronts — Indonesia, Singapore,
Malaysia, Thailand, Vietnam, Philippines, Brazil, Mexico and Taiwan. A full URL
selects its own region; bare IDs/usernames use the region input. The public shop
page path was verified on 8 Nov 2026 in Indonesia, Thailand, Singapore, the
Philippines, Vietnam, Taiwan, Malaysia and Brazil.
How fresh is the data? Every run fetches live data at request time, so results reflect the shop's current state.
How do I get shop IDs? From any Shopee product or shop URL — the actor extracts the shop automatically. You can also paste usernames or numeric shop IDs directly.
Is it reliable at scale? Each shop is one request with optional retries
(maxRetries) and per-shop error handling, so one bad ID never fails the whole run.
Unknown shops are skipped and listed in the run's SUMMARY record. If Shopee
blocks every lookup the run ends as failed with a clear status message (no rows,
nothing charged); set stopOnBlock: true to end the run on the first block instead.
Shopee can restrict its pages and endpoints at any time; the October and November
2026 changes above are examples.
Is scraping this data legal? The actor collects publicly available shop information. You are responsible for using the data in compliance with Shopee's terms and applicable laws (including data-protection rules for any personal data).