Product Search Scraper for Temu - Prices, Sellers & Deals

Disclaimer: This Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by PDD Holdings Inc. or any of its subsidiaries. All trademarks mentioned are the property of their respective owners. "Temu" is referenced only to describe the publicly available website this Actor collects data from.

Scrape Temu search results into a clean, structured dataset. Give it a search term - or a list of Temu search URLs - and get back every product Temu shows for it: product ID, title, price, "was" price and discount, units sold, seller ID and type, category ID, image and the canonical product URL, ready for Excel, CSV, JSON or your own pipeline.

Built for e-commerce price monitoring, competitor research, dropshipping product research, catalog matching and market analysis on one of the fastest-growing marketplaces in the world.

• Reads Temu's own search results page by page, to the depth you ask for, in Temu's own ranking order.
• Need thousands of products? Use more search terms. Temu itself returns at most ~300 results per search - that is Temu's limit, not this Actor's. Ten terms at 100 each asks for 1,000 products in a single run; the run tells you when a term ran out early.
• No Temu account, no cookies, no login. Nothing to configure but your search terms.
• Pay per product you keep - price and adult-content filters run during the scrape, so filtered-out products are never charged.
• Bulk input: paste search terms, paste a block of Temu search URLs, upload a .txt/.csv file, or link a remote file / Google Sheet.

---

What you get

One row per product:

Field	Description
productId	Temu's numeric product (goods) ID
title	Full product title
url	Canonical Temu product URL
price	Numeric price, e.g. 12.68
priceText	Price exactly as shown, e.g. $12.68
currency	Currency code, e.g. USD
originalPrice	Temu's own "was" price, when the product is discounted
discountPercent	Discount percentage, when the product is discounted
soldCount	Units sold, when Temu discloses it
soldText	The "N sold" badge verbatim, when shown
imageUrl / imageWidth / imageHeight	Main product image and its dimensions
hasVideo	Whether the listing has a product video
categoryId	Temu's category ID for the product - group listings, or match them to a category
sellerId	Temu seller (mall) ID - group or match listings by seller
sellerType	first-party, third-party-marketplace or local-warehouse
skuId	Currently selected SKU ID
tags	Merchandising badges, e.g. Only 3 left, Big & Tall
isAdultProduct	Whether Temu flags the listing as adult content
onFlashDeal / dealEndsAt	Whether the product is in a timed deal, and when it ends
rank	Position in Temu's result list for the search
searchTerm	The search term the row came from (what you asked for)
temuSearchTerm	The search Temu actually ran - usually the same; see the note below
sourceUrl / scrapedAt	Provenance of the row

Honest note on field coverage

Temu itself only publishes some of these for some listings, so a few fields are deliberately null rather than guessed. How many rows carry them depends on the search; measured on live searches (wireless earbuds, kitchen gadgets, dog bed, yoga mat, LED strip lights, desk lamp, water bottle):

• originalPrice / discountPercent - 0-13%: present only while a product is actually discounted.
• soldCount / soldText - 0-22%: Temu discloses sales volume for a minority of listings. This Actor emits null when nothing is disclosed rather than a misleading 0.
• tags - 3-31%: only listings Temu badges.
• dealEndsAt - 2-46%: only listings on a countdown.

Everything else - productId, title, url, price, priceText, currency, imageUrl, hasVideo, categoryId, sellerId, sellerType, skuId, rank, searchTerm, temuSearchTerm - is 100% populated. Ratings and review counts are not offered: Temu leaves them out of its search pages.

Temu rewrites a few searches. For some phrases Temu runs a different, broader search - for example it answers "water bottle" with its results for "-bottle", which include soap dispensers and bottle openers. When that happens the run card says so, and every row carries both your term (searchTerm) and the search Temu ran (temuSearchTerm), so you can filter those rows or rephrase the term.

---

Input

Field	What it does
Search terms	One term per line, exactly what you would type into Temu's search box.
Start URLs	Temu search-result URLs, or Temu's own search pages such as temu.com/yoga-mat-...-s.html. Supports Link remote text file and file upload.
Search URLs from a file or pasted list	Paste a block of URLs, or one link to a .txt/.csv/Google Sheet. Ideal from the API or an AI agent.
Max products per search term	Stop once this many products have been collected per term (up to Temu's ~300). Only products that pass your filters count.
Minimum / Maximum price	Keep only products in a price band. Applied while scraping - filtered rows are not charged, and the Actor keeps reading Temu's results until it has your number of matches or Temu runs out.
Exclude adult products	Drop listings Temu flags as adult content.
Proxy configuration	Residential proxies are the default and what this Actor is tested with. Temu refuses datacenter addresses far more often.

{
  "searchTerms": ["wireless earbuds", "yoga mat"],
  "maxResultsPerTerm": 240,
  "minPrice": 5,
  "maxPrice": 50,
  "excludeAdultProducts": true
}

Product-detail URLs are not supported. Temu serves individual product pages as an empty JavaScript shell with no data in it, so this Actor scrapes search-result pages only and tells you on the run card if you gave it something else. Every row still carries the canonical product URL.

---

Use with AI assistants (MCP)

This actor works as a tool for AI assistants and agents through the Apify MCP server - ask for Temu products in natural language and the agent runs this scraper and reads the dataset back.

Agent-ready: autonomous payments (x402 & Skyfire)

This actor is agent-ready: AI agents can discover it, run it, and pay for it autonomously, with no Apify account and no human in the loop. It uses pay-per-event pricing and limited permissions, so it qualifies for Apify's agentic-payment standards:

• x402: an open, HTTP-native payment protocol. Agents pay per run in USDC on the Base network directly through the Apify MCP server, with no account and no API key.
• Skyfire: agent-to-service payments for fully autonomous AI-agent workflows.

Building an AI agent, MCP tool, or autonomous data pipeline? This scraper is ready to plug in and pay as it goes.

---

Pricing

Pay-per-event: you are charged per product returned, plus any run-start fee shown on the Pricing tab. Products removed by your price or adult-content filters are never charged.

Reliability - read this before you buy

Temu rate-limits its own search pages, and it does so in waves. That is the single thing that decides how much data a run returns, and this Actor is built around it rather than pretending otherwise:

• it rotates a pool of search-engine crawler identities, because Temu's limit applies per identity, and it reads both page layouts Temu serves them;
• a refused request is detected (Temu answers with an empty page, not an error) and retried with another identity on a fresh IP, never mistaken for "no results";
• a short or half-rendered page is read again instead of being taken as the end of the results;
• searches run several at a time, so one slow search does not hold up the others.

What this means in practice. When Temu is serving, a few hundred products come back in a minute or two. When Temu is refusing, the run stops within about two minutes, says so plainly on the run card, and charges no products. When it refuses part-way, the run card names the searches that came back short (and counts the rest when there are many), for example:

⚠ INCOMPLETE: 1 of 3 searches came back in full. Temu stopped serving "dog bed" after 40 of 120 and refused "yoga mat": it is rate-limiting its search pages right now (not a problem with your input). No missing product was charged - re-run those searches later.

You are only ever charged for products that are in your dataset (plus any run-start fee shown on the Pricing tab).

Automate & schedule

Run this Actor on autopilot and pull results into your own stack:

• Apify API - start runs, fetch datasets and manage schedules over REST.
• apify-client for JavaScript and apify-client for Python - official SDKs.
• Schedules - run it hourly, daily or weekly and keep your dataset current.
• Webhooks - trigger downstream actions (CRM import, Slack alert, email sequence) the moment a run finishes.

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: 'MY_APIFY_TOKEN' });

const run = await client.actor('scrapesage/temu-scraper').call({
    "searchTerms": [
        "wireless earbuds"
    ],
    "maxResultsPerTerm": 120
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(`Got ${items.length} records`);

Integrate with any app

Connect the dataset to thousands of apps - no code required:

• Make - multi-step automation scenarios.
• Zapier - push new records straight into your CRM or spreadsheet.
• Slack - get notified when a scheduled run finds something new.
• Google Drive / Sheets - auto-export every run to a spreadsheet.
• Airbyte - pipe results into your data warehouse.
• GitHub - trigger runs from commits or releases.

More scrapers from scrapesage

Related Actors in the same category:

• Taobao & Tmall Scraper - Products, Prices, Sellers & Reviews
• Kompass Scraper - Global B2B Company & Supplier Leads
• Faire Scraper - Wholesale Brands, Supplier Leads & Products
• AliExpress Scraper - Products, Prices, Orders & Supplier Leads
• GetYourGuide Scraper - Tours, Activities, Prices & Reviews

FAQ

How is this Actor billed? Pay-per-event: you pay for the products it delivers, with no monthly rental. Any run-start fee and the per-product price are shown on the Pricing tab.

Can I schedule it and get results automatically? Yes - create a Schedule and add a webhook or an integration (Google Sheets, Slack, Make, Zapier) to push each run's dataset wherever you need it.

Which export formats are available? Every run's dataset can be downloaded as JSON, CSV, Excel (XLSX), XML, HTML or RSS from the Apify Console or the API.

Can I run it from code or an AI agent? Yes - through the Apify API and client libraries, or from Claude, ChatGPT and other assistants via the Apify MCP server.

Is it legal to scrape Temu? This Actor collects publicly available data only. You are responsible for using the output in compliance with applicable laws (including data-protection law where personal data is involved) and the source's terms. See Data & lawful use and the Disclaimer below.

Is this an official Temu tool? No. It is an independent, third-party Actor with no affiliation to, endorsement by or sponsorship from PDD Holdings Inc. See the Disclaimer below.

Data & lawful use

How it accesses the site. This Actor reads only publicly available pages that Temu serves without a login. Temu serves its search-result pages fully server-rendered only to search-engine crawlers, so this Actor identifies itself with standard search-engine crawler User-Agents (Googlebot, Bingbot and msnbot) and requests only Temu search-result pages, which Temu's robots.txt does not disallow for any of those crawlers. It does not log in, create accounts or use cookies.

The output is the public data the site publishes; where a record identifies an individual you are responsible for using it lawfully, including data-protection law where it applies.

Under Apify's Standard Actor Contract, which governs your use of this Actor, you are the controller of any personal data in your input and output and scrapesage acts only as your processor: that data is processed solely to run your job, written only to your own Apify storage, never used for any other purpose and never shared onward. If you need help with a data-subject request that involves this Actor's output, open an issue on the Issues tab.

Disclaimer

This Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by PDD Holdings Inc. or any of its subsidiaries. All trademarks mentioned are the property of their respective owners.

"Temu" and any related marks are the property of their respective owners and are used here only in a descriptive, nominative sense - to identify the publicly accessible website from which this Actor collects data. This Actor is not an official Temu product, is not authorised or certified by PDD Holdings Inc., and does not distribute Temu software. It collects only publicly available information; you are responsible for ensuring your use of that data complies with applicable laws, regulations and the terms of the source website.

Need help?

Open an issue on the Actor's Issues tab, or visit the Apify help center. Feature requests are welcome - this Actor is actively maintained.