Getting Started

Read a product once to learn its variants, then check their prices on a schedule with the skuIds it gave you. That is the whole workflow — and the second step is where getting it right saves a thousandfold in bytes.

1. Get your API key

Create an account and generate a FetchLayer API key from your dashboard. There is no Temu account or seller credential to register.

Create free account →

2. Read a product and its variants

bash

curl -X POST https://api.fetchlayer.dev/temu/product \
  -H "Authorization: Bearer ss-your-key" \
  -H "Content-Type: application/json" \
  -d '{"product":"607033881415363","market":"US"}'

product takes the product id or any Temu product URL. The response carries the default variant's price, list price, discount and running promotion, the gallery and specifications, and a variants array — each with its own skuId, price and availability. Keep those skuIds.

Tip

Temu publishes each variant's own price only while a promotion runs. For other products the default variant is listed and the rest fall within product.priceRange — the notes array says which case you are looking at.

3. Check prices with skuIds

bash

curl -X POST https://api.fetchlayer.dev/temu/price-check \
  -H "Authorization: Bearer ss-your-key" \
  -H "Content-Type: application/json" \
  -d '{"market":"US","items":[{"goodsId":"607033881415363","skuId":"117585735607558"},{"goodsId":"607033881415363","skuId":"117585735640326"}]}'

Up to 50 items per call, each reported as ok, not_found or failed. One failed item never fails the others.

Always send skuId

An item with a skuId is a ~1.6KB check. An item without one first loads the whole product page (~1.5MB) to find the default variant, and is several times slower. If you only have a goodsId, the first check returns the variant it priced as skuId with variantLookedUp: true — store it and send it from then on.

4. Handle refusals

Temu rate-limits tightly. A 503, a 502, or a price-check item with status: "failed" is worth retrying after a short wait. A 400 (bad input, including an unrecognised field) or 404 (the product does not exist or is not sold in that storefront) will not change on retry.

Tip

Have a link someone pasted? /resolve-url turns any Temu URL into its goodsId, skuId and storefront without touching Temu, and does not consume a credit.

Error responses

Every error, on every route, is JSON in one shape: error (what went wrong, in words), status, code, retryable and requestId, which also comes as the X-Request-Id header. Branch on code and retryable rather than on the text; on a 5xx the text is generic. Quote requestId when reporting a problem.

json

{
  "error": "Missing required parameter: url",
  "status": 400,
  "missing": ["url"],
  "code": "invalid_input",
  "retryable": false,
  "requestId": "922874e3-c0d0-40d8-8866-d198af132420"
}

code	Status	Retryable	Meaning
invalid_input	400	no	The request needs fixing; error names the field. A missing required parameter also lists it in missing.
unauthorized	401	no	The API key is missing or not valid.
insufficient_credits	402	no	Nothing left to spend: no credits, a used-up free trial, or a monthly allowance and credit balance both spent. error says which. Waiting does not help; topping up does.
forbidden	403	no	This key or account is not allowed this request.
not_found	404	no	What the request names does not exist or is not public.
expired	410	no	What the request refers to is no longer available; ask for it afresh.
quota_exceeded	429	no	A request-rate limit was reached; error says which. Slow down before sending more.
cancelled	499	no	The caller closed or cancelled the request before it finished. The work was stopped and nothing was charged.
time_limit	503	yes	Your timeoutMs ran out before there was anything to return; ask again, or allow more time.
temporarily_unavailable	503	yes	Not available right now; ask again shortly.
posts_unavailable	403	no	TikTok user videos: TikTok is not showing this account’s posts publicly right now. Asking again at once returns the same answer; nothing is charged.
store_unreachable	503	yes	Store routes (Shopify, WooCommerce): the store itself can’t be reached right now — it may be offline. Ask again later. Where a store route doesn’t say so yet, an offline store is temporarily_unavailable.
upstream_error	502	yes	The source answered in a way that could not be used; ask again later.
internal_error	500	yes	Something failed on our side; ask again later, and quote requestId if it persists.
tool_error	—	no	MCP only: a tool call failed in a way no other code describes; error says what.

More codes may be added; treat one you do not recognise by its retryable flag. Over MCP, a tool error carries the same fields in structuredContent, and as a JSON text block beside the message.

Next steps

Product overviewTemu API: what it returns, pricing and use cases

On this page