AliExpress API v1

Pin the market

AliExpress answers differently depending on who is shopping. The same keyword ranks different products first for a US and a German shopper, the same product is priced in a different currency, and titles are translated. So every scraping endpoint takes the market explicitly — shipTo (a two-letter country), currency and language — and every result echoes the market it was read in as market. Unset fields default to US, USD and en_US.

Only values verified to work are accepted: currencies USD, EUR, GBP, CAD, AUD, NZD, BRL, MXN, CLP, COP, PEN, ARS, JPY and KRW; languages en_US, de_DE and pt_BR. Anything else is a 400 — AliExpress itself answers an unsupported currency with an empty page that looks exactly like "no matches", so it is refused up front. When you compare prices over time, keep the market fixed: a price read in a different market is a different price, not a price change.

Retry 503s on product lookups

/product-details and /product-prices depend on product lookups that AliExpress refuses in bursts, so an occasional 503 on those two is temporary — wait a little and retry. Search, category listings and reviews are served another way and are not affected. The rest of the contract is the same across the API: 400 means fix the request and 404 means the product or category does not exist, and neither is worth retrying; 502 and 503 are.

Read the notes array

Every JSON result carries a notes array. It is where a partial answer announces itself: a multi-page walk AliExpress refused part-way (with a nextCursor that resumes at the refused page), a search AliExpress padded with loosely related products, or a review page repeated by the cursor. An empty notes means the result is as complete as AliExpress publishes.

Available endpoints