Temu API — FetchLayer Docs

Temu API v1

Three endpoints, on purpose: one product in full, current prices for up to 50 variants per call, and URL parsing — each priced for the country storefront you choose, from https://api.fetchlayer.dev/temu. No Temu account, no seller credentials.

OpenAPI JSON

Temu API at a glance

This is the reference: every endpoint, its parameters and the fields it returns. The essentials first.

Returns
Product details and price checks, as typed JSON.
Endpoints
3 endpoints, grouped as Products and Utility. See them all
Request
POST https://api.fetchlayer.dev/temu/<endpoint> with a JSON body.
Auth
Your FetchLayer API key as a Bearer token. One key works for every platform we support. Authentication
Cost
1 credit per page of results a call returns; the exact figure is on every response. Credits are $1.99 per 1,000 pay-as-you-go, plans start at $25 a month, and new accounts get 30 free requests.
MCP
Also on our MCP server for AI agents, with the same key and the same billing. Connect an agent

What teams use it for, with worked examples: Temu API

Send the skuId to price checks

This decides what a price-monitoring job costs. A /price-check item that names its variant with skuId is a ~1.6KB check that answers in a fraction of a second. An item without one first loads the whole product page — about 1.5MB — to find the default variant. Every /product response lists the skuIds, and every price check returns the skuId it priced: store it once, send it every time after.

What this API does not return

Keyword search and reviews are not available: Temu doesn't make them reliably public, so they are left out rather than served unreliably. Star ratings, sold counts, shipping costs, delivery estimates and stock quantities are not available either — availability is a status, not a count. If you need to discover products, start from Temu URLs you already have; /resolve-url turns any of them into ids.

Prices, storefronts and the notes array

Temu prices, currency and availability differ by country. Every request is priced for exactly one storefront, named by market (default US), and a response rendered for the wrong country fails rather than returning another currency. Every result also carries a notes array — a variant list that may be incomplete, availability that could not be checked. Read it before treating a result as complete.

Rate limits and retries

Temu rate-limits tightly. When it refuses, you get a 503 (or, inside a price check, an item with status: "failed") — retry those after a short wait, as you would a 502. A 400 or 404 will not change on retry. Space scheduled checks out and batch variants into one call rather than firing many single-item requests.

Available endpoints

Product overview Temu API: what it returns, pricing and use cases