TikTok Shop Trending Products — Sold Count, SKU | $1.99/1K

Extract structured e-commerce data from TikTok Shop at scale. This TikTok Shop Scraper pulls clean product records from product pages, seller storefronts, and keyword search — title, current and original price, sold count, rating, reviews, shop, SKU variants, images, and stock status. It is built for sellers, affiliates, and market-research teams who need reliable TikTok Shop product data without a browser farm or a third-party proxy account. You pay per product — $1.99 per 1,000 results — and compute runs on your own Apify account.

Unlike a generic TikTok video scraper, this actor is dedicated to the shopping surface: every row is a product or a shop, with prices and sales metrics, ready for spreadsheets, BI tools, or a price-monitoring pipeline.

TikTok Shop product data — what you get

Each product record includes:

Field	Description
product_id, title, description	Product identity and copy
price, original_price, currency, discount_pct	Current vs. list price and the discount
price_min, price_max	Variant price range — spot multi-tier listings at a glance
sold_count, rating, review_count	Demand and social-proof signals (sales velocity)
shop_id, shop_name, seller_region	Which storefront and which market (US/UK/SEA)
category, brand	Classification
sku_variants	Per-variant name, price, and stock
image_urls, video_urls	Product gallery images and demo/review videos
shipping	Shipping fee, origin region, and delivery estimate
stock_count, is_in_stock, product_url	Numeric stock, availability flag, and canonical link
parse_confidence, warnings	Per-row quality score so you catch silent drift

Shop mode adds a shop record with shop_name, follower_count, product_count, rating, and region, followed by each product listed on that storefront.

Why this TikTok Shop Scraper beats the alternatives

Most TikTok Shop actors on the market run a full browser farm (slow and expensive), pass ~$8/GB residential traffic to you, and break silently when TikTok re-skins its pages. This one is different on four concrete points:

• Per-row quality scoring. Every record carries parse_confidence and warnings. No other TikTok Shop scraper tells you, per product, whether the parse was clean — so you catch silent structure drift the day it happens instead of weeks later when your dashboard is already full of nulls.
• Richer schema. Variant price range (price_min/price_max), numeric stock_count, product video_urls, and shipping (fee/origin/delivery) — fields the cheaper incumbents drop.
• Self-healing transport. Each request rotates to a fresh residential exit IP, and a soft block (login-wall page with no product JSON) triggers an automatic retry on a new IP rather than a failed row.
• Graceful degradation. A probe-first stop-gate verifies connectivity before you are charged a cent, and keyword search degrades cleanly if TikTok rotates its request signing while product and shop modes keep running.

How to scrape TikTok Shop

Pick any combination of three input modes — the actor auto-detects which to run:

1. Keyword search — give a list of keywords (e.g. phone case, skincare) and the actor returns matching products, paginated up to maxResults.
2. Product URLs / IDs — paste TikTok Shop product (PDP) URLs like https://www.tiktok.com/shop/pdp/<id> or bare IDs. This is the most reliable mode: it reads the product JSON embedded directly in the page, with no request signing.
3. Shop / storefront URLs / IDs — paste https://www.tiktok.com/shop/store/<shop_id> links to get the shop profile plus its product catalog.

Resilient, low-maintenance e-commerce scraper

TikTok blocks datacenter IPs and region-gates TikTok Shop, so this actor uses Apify Residential Proxy (configured through the standard proxy input — no external proxy key, ever) and follows the storefront region of your chosen countryCode. The parser targets stable business keys (productId, salePrice, soldCount), not fragile CSS classes, so it survives TikTok's frequent re-skins. A probe-first stop-gate verifies connectivity before charging you, and keyword search degrades gracefully if TikTok rotates its request signing, while product and shop modes keep running.

Pricing

$1.99 per 1,000 products (Pay Per Result). Shop profile rows are free; you are billed only for products. Residential proxy usage is billed to your own Apify account at standard rates. Start with a low maxResults for a cheap test run.

Related actors

Pair this with our other marketplace scrapers for cross-platform e-commerce intelligence. For TikTok video, profile, and comment data, use a dedicated TikTok video scraper instead — this actor is shopping-only.

Integrations

Built for e-commerce sellers and market-research teams benchmarking TikTok Shop products, pricing, and sales-velocity signals — the JSON/dataset output drops into the tools you already run, no glue code:

• n8n / Make / Zapier — trigger a run or pipe every new dataset item into 500+ apps (Google Sheets, Airtable, Slack, HubSpot, your database) with no code: n8n, Make, Zapier.
• Webhooks — fire your own endpoint the moment a run finishes, to push results straight into your pipeline (docs).
• MCP server — expose this actor as a tool to Claude, Cursor, or any MCP client so an AI agent can pull this data mid-conversation (guide).
• API & SDKs — fetch the dataset as JSON, CSV, or Excel through the Apify REST API or the Python / JS SDKs.

See all Apify integrations.

Frequently asked questions

Do I need a TikTok account or an external proxy key?

No. The actor runs on Apify Residential Proxy through the standard proxy input — no login, no third-party proxy account. Proxy usage is billed to your own Apify account.

Which countries and storefronts are supported?

It follows the storefront region of your countryCode — US, UK and Southeast-Asia TikTok Shop markets are supported.

Can I get real sales numbers?

Yes. Every product row carries sold_count, rating and review_count, so you can rank by real sales velocity, not just listing order.

What input modes are there?

Three, auto-detected: keyword search, product URLs/IDs (the most reliable — reads the embedded product JSON), and shop/storefront URLs/IDs (shop profile plus its full catalog).

Does it scrape TikTok videos, profiles or comments?

No — this actor is shopping-only (products and shops). For video, profile or comment data use a dedicated TikTok video scraper.

What output formats can I export?

JSON, JSONL, CSV and Excel via the Apify dataset, plus the Apify API and Python/JS SDKs.

More scrapers from our toolkit

Building a data pipeline? These actors pair well with this one — each runs on your own Apify account with the same pay-per-result pricing, no subscription:

• Amazon Products Scraper
• Ebay Scraper
• Etsy Listings
• Shopify Products Scraper
• Competitor Price Monitor
• Mercadolibre Scraper

Chain any of them together from the Integrations tab (the Run succeeded trigger) to build a multi-step workflow — one actor's output feeds the next.

Output example

Each dataset item has this shape (values are illustrative placeholders, not real data):

{
  "title": "string",
  "price": "string",
  "original_price": "string",
  "currency": "string",
  "discount_pct": "string",
  "sold_count": "string",
  "rating": "string",
  "review_count": "string",
  "shop_name": "string",
  "seller_region": "string",
  "product_url": "https://example.com/item/123",
  "parse_confidence": "string"
}

Rate this Actor

If TikTok Shop Trending Products saved you time, please rate it on the Apify Store. A rating takes a few seconds and helps other people find a working scraper. If something did not work, open an issue on the Actor page and we will fix it.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.