One API, 2 marketplaces

Shein and Temu data from one API

These two set the floor for cross-border consumer pricing and are usually researched together. Both are here under one key, and this page is direct about where each one's data is awkward, because both are.

Why not the official API

Neither publishes a public product API. Both run seller and affiliate programmes that return partner-scoped data rather than the catalogue.

Coverage

What the two engines give you

Shein
search, product/detail, price, category/browse
Temu
search, product/detail
Shein markets
US and the Gulf storefronts, each with its own currency
Variants
Shein detail carries per-size price and availability
Worked example

Compare an item across both

Search each, then read the detail. Take the price from the record you asked for.

  1. 1
    POST /shein/v1/search

    listings with the card price

  2. 2
    POST /shein/v1/product/detail

    per-size price and availability

  3. 3
    POST /temu/v1/search

    the comparable item on Temu

  4. 4
    POST /temu/v1/product/detail

    the full record

Two cross-border prices for a comparable item, at variant level on the Shein side.

Before you join them

Where the two sources genuinely differ, including where it is awkward

 sheintemu
Depth4 actions including a dedicated price endpoint2 actions
Pagingcategory browse pages normallysearch returns one page, 40 rows — that ceiling is the source's, not ours
Price agreementa product page price can disagree with the card price on the same item; the card figure is the one we returnsingle price per record
Discountsstruck-through price presentclaimed discounts are published as-is