AliExpress Products Scraper

What this Actor scrapes

AliExpress runs no public product-data API for shoppers, and its product-detail page is a client-side-rendered app shell with zero product data in the raw HTML — we execute it in a real, fingerprint-resistant browser so the numbers are actually there. This Actor resolves products three ways — search keyword, direct product URL, or product ID — and returns one clean schema across all three: price, currency, rating, review count, and an explicit order_count (the "500+ sold" badge) most AliExpress scrapers skip past.

What we handle for you

• 🛡️ Browser fingerprint rotation — curl-cffi impersonates real Chrome / Firefox / Safari TLS handshakes so the target sees a browser, not Python.
• 🌐 Residential proxy rotation via Apify Proxy — fresh session and exit IP on every block.
• 🔁 Retries with exponential backoff on 408 / 429 / 5xx — up to 5 attempts per page, Retry-After honoured.
• 🧱 Rate-limit-aware pacing — when the target pushes back, we slow down instead of getting banned.
• 🧊 Clean, typed dataset rows — Pydantic-validated, ISO-8601 timestamps, stable product IDs, JSON / CSV / Excel export straight from the Apify Console.
• 💰 Pay-Per-Event pricing — you only pay for results that hit your dataset. No data, no charge.

Use cases

• Dropshipping product validation — check price, rating, and order count before you list a product.
• Amazon private-label sourcing research — cross-reference candidate SKUs by order volume instead of eyeballing the storefront.
• Competitor price monitoring — track price movement across a candidate catalog by search keyword or product ID.
• Catalog enrichment — resolve a list of product URLs or IDs into title, price, rating, and images in one call.
• Market-price snapshots — run the same keyword across a run schedule to build your own price-history series (AliExpress doesn't publish one).

Input

Paste this into the Apify Console, or send it as the run input over the API. Proxy settings are on by default; you rarely need to touch them.

{
  "searchKeywords": [
    "wireless earbuds"
  ],
  "maxResultsPerKeyword": 3,
  "shippingDestinationCountry": "US",
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}

Output

One row per result, schema-validated before it is written. Export JSON, CSV, Excel or XML from the run, or read it over the API.

product_idtitlepricecurrencyratingreview_countorder_countvariantsshipping_cost_estimateshipping_destinationproduct_urlimage_urlsseller_namecategorysearch_keywordscraped_at

{
  "product_id": "3256811548194791",
  "title": "Air Pro ANC Wireless Earphone Bluetooth Headsets Pro 2 Active Noise Cancellation",
  "price": 3.67,
  "currency": "USD",
  "rating": 4.8,
  "review_count": 334,
  "order_count": null,
  "variants": [],
  "shipping_cost_estimate": null,
  "shipping_destination": "US",
  "product_url": "https://www.aliexpress.com/item/3256811548194791.html",
  "image_urls": [
    "https://ae-pic-a1.aliexpress-media.com/kf/S883875aebfd44d7ab6eed07c5fe2fae09.jpg"
  ],
  "seller_name": null,
  "category": null,
  "search_keyword": null,
  "scraped_at": "2026-08-31T06:45:00.368Z"
}

Pricing

You pay only for results that land. Cap any run with maxTotalChargeUsd. See pricing & billing for worked examples.

Limitations

• searchKeywords rows: title, price, currency, rating, and order_count all come from the search results page directly.
• productUrls/productIds rows: AliExpress's product-detail page ships zero product data in its raw HTML — every field comes from a structured-data block a real browser render exposes. That block carries title, price, currency, rating, review count, and images, but not order_count.
• variants, seller_name, category, shipping_cost_estimate are currently always null/[] on every row, both modes. AliExpress doesn't expose per-variant stock, seller name, or category on any page surface we've found a reliable source for yet, and its shipping-cost endpoint isn't publicly reachable. We'd rather ship an honest null than a guessed value — these are on our roadmap as the storefront's endpoints get mapped further.
• productUrls/productIds lookups render the live page in a real browser, and an individual render can occasionally fail to resolve — we retry once with a fresh session automatically, and a still-unresolved entry is skipped (not billed) and named in the run's status message rather than silently dropped. searchKeywords never touches a browser and doesn't carry this risk.
• English/USD aliexpress.com storefront only — no other locales in v1.
• Review text isn't included, only rating/review_count (see the companion AliExpress Reviews Scraper for review text).
• No historical price time-series or coupon/cart-level pricing.