Temu APItemu.com ↗
Access Temu product search, homepage featured listings, and product details including price, ratings, review counts, and sales volume via a structured JSON API.
What is the Temu API?
The Temu API provides 3 endpoints covering product search, homepage featured listings, and individual product details from temu.com. The search_products endpoint accepts keyword queries and returns paginated arrays of products with fields including sale price, market price, discount percentage, rating, review count, sold count, and thumbnail URL — enough to build price trackers, comparison tools, or catalog mirrors against Temu's inventory.
curl -X GET 'https://api.parse.bot/scraper/19417d13-c955-4a31-bfb8-d40635cf048d/search_products?limit=10&query=wireless+earbuds&offset=0' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace temu-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: Temu Catalog API — search products, browse featured, get details."""
from parse_apis.Temu_Catalog_API import Temu, ProductNotFound
client = Temu()
# Search for products by keyword, capped at 5 total items.
for product in client.products.search(query="wireless earbuds", limit=5):
print(product.title, product.price, product.rating, product.category)
# Browse featured/trending homepage products, take the first one.
featured = client.products.featured(limit=3).first()
if featured:
print(featured.title, featured.sold_count, featured.shipping_days, featured.ranking_label)
# Drill into a specific product by ID for full details.
top = client.products.search(query="kitchen gadgets", limit=1).first()
if top:
try:
detail = client.products.get(product_id=str(top.product_id))
print(detail.title, detail.price, detail.market_price, detail.product_url, detail.mall_id)
except ProductNotFound as exc:
print(f"Product not found: {exc}")
print("exercised: products.search / products.featured / products.get")
Full-text search over Temu's product catalog by keyword. Returns a paginated list of products with pricing, ratings, sales data, shipping info, and category rankings. Pagination is offset-based: advance `offset` by `limit` to fetch subsequent pages. Each product carries a `product_id` usable with get_product_details.
| Param | Type | Description |
|---|---|---|
| limit | integer | Number of results to return per page. |
| queryrequired | string | Search keyword (e.g. 'wireless earbuds', 'kitchen gadgets'). |
| offset | integer | Offset for pagination. Advance by `limit` for the next page. |
{
"type": "object",
"fields": {
"has_more": "boolean indicating if more results are available beyond this page",
"products": "array of product objects with product_id, title, price, market_price, discount_percent, rating, review_count, sold_count, thumbnail, product_url, category, ranking_label, shipping_days, video_url, mall_id",
"total_count": "integer count of products returned in this response"
},
"sample": {
"data": {
"has_more": true,
"products": [
{
"price": "$4.73",
"title": "Wireless Earbuds, 2026 Wireless Headphones HiFi Stereo Earphones",
"rating": 4.8,
"mall_id": 634418216644132,
"category": "in Headphones, Earbuds & Accessories",
"thumbnail": "https://img.kwcdn.com/product/fancy/0fcaa1ae.jpg",
"video_url": null,
"product_id": 601102740526088,
"sold_count": "10K+ sold",
"product_url": "https://www.temu.com/wireless-earbuds-g-601102740526088.html",
"market_price": "$20.20",
"review_count": "1,677",
"ranking_label": "TOP RATED",
"shipping_days": 5,
"discount_percent": "76"
}
],
"total_count": 40
},
"status": "success"
}
}About the Temu API
Endpoints and What They Return
The API exposes three GET endpoints. search_products takes a required query string plus optional limit and offset integers for pagination, and returns a products array alongside total_count and a has_more boolean. Each product object carries product_id, title, price, market_price, discount_percent, rating, review_count, sold_count, and thumbnail. The get_homepage_featured endpoint uses the same pagination parameters and the same product object shape, but pulls from Temu's trending/recommended homepage surface rather than a keyword search.
Product Detail Lookup
get_product_details accepts a single product_id string — the numeric ID surfaced in products[*].product_id from either of the other endpoints — and returns a focused record with title, price, market_price, discount_percent, rating, review_count, sold_count, thumbnail, and the product_id itself as an integer. Prices are returned as formatted strings (e.g. '$5.61'), making them directly displayable without additional formatting.
Pagination and Data Shape
Both list endpoints (search_products and get_homepage_featured) use offset-based pagination via offset and limit. The has_more boolean in each response tells you whether additional pages exist, allowing straightforward sequential iteration. total_count on search_products reflects the count of products returned in the current response page, not the total catalog size for that query.
The Temu API is a managed, monitored endpoint for temu.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when temu.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official temu.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Track price changes and discount percentages on specific Temu products over time using
priceandmarket_pricefields. - Build a product comparison tool that surfaces Temu listings alongside other marketplaces using
title,price, andrating. - Monitor trending products by polling
get_homepage_featuredand tracking shifts insold_countandreview_count. - Seed an affiliate product feed by querying
search_productswith category keywords and exportingthumbnail,title, andprice. - Analyze discount depth across a product category by collecting
discount_percentvalues from keyword search results. - Power a consumer deals alert that fires when
discount_percentfor a trackedproduct_idcrosses a defined threshold.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Temu have an official public developer API?+
What does `search_products` return beyond the title and price?+
search_products returns a products array where each object includes product_id, title, price (sale price), market_price (original price), discount_percent, rating (numeric average), review_count, sold_count, and thumbnail (image URL). The has_more boolean and total_count support pagination.Does the API return product descriptions, seller information, or variant data?+
How does pagination work across the list endpoints?+
search_products and get_homepage_featured accept integer offset and limit parameters. Each response includes a has_more boolean indicating whether another page of results exists. Increment offset by limit on each request to walk through result pages sequentially.Are category-based or filter-based searches supported?+
search_products accepts only a free-text query string. Filtering by category, price range, rating threshold, or shipping options is not currently supported. You can fork this API on Parse and revise it to add a category-browse or filtered-search endpoint.