AliExpress Search Scraper
Pricing
from $0.70 / 1,000 unique products
Scrape AliExpress search results: price, discount, exact units sold, rating, Choice and free shipping. Many countries per run, price-change mode. No login.
Search terms, 1 to 100, as you would type them on AliExpress. Each keyword runs once per ship-to country. Either keywords or start URLs are needed.
Optional. AliExpress search URLs (/w/wholesale-*.html) or category list URLs (/category//.html). Product URLs (/item/...) are rejected: this Actor reads result lists only.
[]ISO-2 markets, e.g. US, DE, GB. Prices, currency and the product set differ per market.
[ "US"]Leave empty for each market's own currency (USD for US, EUR for DE, GBP for GB...).
Title language (AliExpress machine-translates titles).
Order of AliExpress results.
In the run's currency. Sent to AliExpress and re-checked on output.
In the run's currency. Sent to AliExpress and re-checked on output.
Output filter, e.g. 4.5. Products without a rating are dropped when set. Filtered rows are free.
Ads are always flagged with isPromoted. Turn off to drop them (free).
Unique products, 1 to 3,600 (AliExpress shows at most 60 pages of 60).
Hard cap for the whole run. Your max charge per run is respected too.
Output only products that are new in the scanned results (changeType newInResults, absent from the last N runs) and price changes on products already seen (priceChanged). Unchanged products are not output and not charged. AliExpress personalises rankings, so newInResults does not mean newly listed.
Named key-value store that keeps a compact per-product history (last price, first and last seen, runs seen in). Use one name per watchlist.
Change-only mode: a product is output as newInResults only if it was absent from all of the last N runs with this state store. Higher means fewer false 'new' alerts from AliExpress's personalised ranking.
Parallel cookie sessions, 1 to 6. Higher is not always faster: AliExpress throttles per IP.
Default: Apify datacenter proxy as a fallback. The Actor starts direct and switches to this proxy at the first captcha cluster (measured on Apify: direct runs from Apify IPs hit captchas at about 27%, datacenter proxy about 10% with 0 failed pages). Turn off to stay direct.
{ "useApifyProxy": true}