AliExpress Scraper API for Search, Products, and Stores
AliExpress spreads the same commercial question across many page types: what a search returns, what a product page states, what buyers wrote, and how a seller presents itself.
This page explains how a single hosted scraping request can cover those surfaces, which request controls matter for each job, and where the practical limits sit. It is a guide to the API's capabilities and inputs, not a promise of any particular success rate on a given day.
What one request can reach
The API is designed to return AliExpress pages as rendered HTML or as structured JSON. The page types named for coverage are search results, product detail pages, review feeds, seller stores, category listings and deal pages. You hand over a target URL and the request itself carries the browser work: JavaScript execution, residential proxy rotation and countermeasures against AliExpress bot detection all happen server-side, so no browser fleet or proxy pool of your own is needed.
That framing matters for planning. A price-monitoring job and a seller-rating job may both start from a product or store URL, but they differ in how often you need to revisit the page and how much of the page you need to parse. The API does not decide that for you; it returns the page or the extracted fields you asked for.
Mapping common jobs to request controls
Three workflows recur in practice: pulling product details, watching price changes, and collecting seller ratings. The table below pairs each with the controls that do the work. Treat it as a planning aid, not a guarantee that every field will be present on every page.
Request control reference
The controls below are the ones named for AliExpress work. Each answers a different question, so combine them deliberately rather than switching everything on at once.
A worked example
Suppose you want the price and availability shown on a specific product page, and you also want the page rendered so that client-side content is present. A sensible request sequence is: send the product URL with render_js=true so the page executes in a real headless browser; add country_code if the price you need is the one shown to shoppers in a particular market; and add extract_rules mapping CSS selectors to field names such as price and availability, or ai_extract_rules with a natural-language description if the markup is unstable. If the target starts returning challenge pages, enable stealth_proxy. The response then arrives as parsed JSON rather than raw HTML.
If you only need the raw rendered page for your own parser, skip the extraction rules and keep the HTML. The two paths are alternatives, not steps that must both be run.
Two different kinds of limit
It helps to separate two failure modes that look similar from the outside.
- Plan concurrency. The API enforces concurrency limits per plan, not per-target rate limits. If you exceed your plan's concurrent request allowance, the constraint comes from your account tier.
- Target throttling. AliExpress may respond aggressively to rapid or repetitive patterns regardless of your plan. In that case, spacing requests out or using multiple sessions is the suggested response, and stealth_proxy is the control to enable when a target becomes aggressive.
Diagnosing which one you hit determines the fix: upgrade or queue for the first, slow down or vary the request for the second.
From account to first request
The documented path has four steps. Create an account to receive an API key and starting credits. Install a client library for your stack — Python, Node, Go, PHP or Ruby are named — so that a scrape becomes a single function call. Then make a request: the AliExpress URL travels with your API key, the page is executed in a real browser, the outbound IP is rotated, and the response comes back ready for your scraper to act on. Advanced parameters are optional add-ons rather than requirements — render_js for JavaScript execution, stealth_proxy for CAPTCHAs, country_code for geo-targeting, and ai_extract_rules for natural-language data extraction.
If you prefer not to write code at all, the dashboard request builder accepts a pasted URL and parameters, and generates a snippet in Python, Node, Go, PHP, Ruby or cURL that you can copy. Code samples in Java, Python, Go, PHP, cURL and JavaScript are also documented.
Choosing an output format
The API can return rendered HTML, parsed JSON via extraction rules, or clean Markdown suitable for feeding into a language model. The choice follows from what happens next:
- Rendered HTML — you have your own parser and want full fidelity.
- Structured JSON — you want named fields and are willing to maintain selectors or a natural-language spec.
- Markdown — you want readable text for summarization or analysis rather than field-level extraction.
Screenshots are a separate capability, useful for visual verification rather than data extraction.
Plans and credit consumption
Plan tiers differ in monthly price, included API credits, concurrent request allowance, and whether priority support, a dedicated account manager and team management are included. Support arrangements, account-management availability and team features should be confirmed against the current plan documentation before relying on them. JavaScript rendering, rotating and premium proxies, geotargeting, and screenshots and extraction rules are listed as included across the standard tiers shown. Enterprise tiers extend credits and concurrency further. Credit consumption is not one credit per request in every case. The published rules are: requests start at 1 credit each; each successful request that enables JS rendering costs 5 API credits; and each successful request that enables premium proxies costs 10 or 25 API credits depending on whether JS rendering is disabled or enabled. Credit validity periods and rollover behaviour should be checked against the current plan terms. Prices are exclusive of VAT. The plan table below reproduces the original provider's published figures as a dated external reference, not as this site's own offer. Treat those figures as a historical snapshot and confirm current pricing and terms with the provider before committing.
Compliance and reliability notes
Data-handling and regulatory statements should be evaluated against the current provider documentation and your own legal review; this page does not assert a particular compliance certification. Proxy rotation and headless browser rendering are presented as the mechanisms that reduce IP-based blocking and mimic real browsing behaviour. Claims about throughput, scaling and response times should be treated as the original provider's own descriptions rather than independent benchmarks, and actual performance will vary by target and load.
| Workflow | What you collect | Controls that matter |
|---|---|---|
| Product details | Competitor pricing, product features, stock levels | Target product URL; render_js=true; extract_rules or ai_extract_rules |
| Price monitoring | Historical price trends over repeated visits | Scheduled repeat requests; country_code for market-specific pricing; extract_rules for price fields |
| Seller ratings | Seller rating and performance signals | Store profile URL; extract_rules for rating fields; stealth_proxy if challenged |
Control pairings are editorial guidance derived from the named request parameters; they do not guarantee that every field exists on every page.
| Control | What it does | When to use it |
|---|---|---|
| render_js=true | Runs the page in a real headless browser and returns post-render HTML | Pages whose content depends on client-side JavaScript |
| stealth_proxy | Enables stealth proxy handling | When a target responds aggressively to requests |
| country_code | Routes through a residential IP in the specified country | When content or pricing varies by geography |
| extract_rules | Maps CSS selectors to field names and returns parsed JSON | Stable markup where you know the selectors |
| ai_extract_rules | Natural-language specification for extraction | When AliExpress markup shifts and selectors break |
Parameter names and behaviours are as documented by the provider; availability may depend on plan.
| Plan | Price / month | API credits | Concurrent requests | Priority support | Account manager | Team management |
|---|---|---|---|---|---|---|
| Hobby | $19 | 75,000 | 25 | Not included | Not included | Not included |
| Freelance | $49 | 250,000 | 50 | Not included | Not included | Not included |
| Startup | $99 | 1,000,000 | 100 | Not included | Not included | Not included |
| Business | $249 | 3,000,000 | 200 | Included | Included | Included |
| Business + | $599 | 8,000,000 | 400 | Included | Included | Included |
| Enterprise 14 | $999 | 14,000,000 | 500 | Included | Included | Included |
| Enterprise 24 | $1,599 | 24,000,000 | 600 | Included | Included | Included |
| Enterprise 41 | $2,399 | 41,000,000 | 700 | Included | Included | Included |
| Enterprise 69 | $3,599 | 69,000,000 | 800 | Included | Included | Included |
| Enterprise 120 | $5,799 | 120,000,000 | 900 | Included | Included | Included |
Figures are the original provider's published list as a dated external reference, not this site's own pricing. Prices exclude VAT; credit validity periods and rollover behaviour should be confirmed against current plan terms. JavaScript rendering, rotating and premium proxies, geotargeting, and screenshots and extraction rules are listed as included on every tier shown. Confirm current pricing before purchase.
Frequently asked questions
Will I get blocked when scraping AliExpress?
The service rotates residential proxies and uses a real headless browser so requests resemble normal traffic. If a target becomes aggressive, enable stealth_proxy on the request. No service can guarantee zero blocks on every target.
Can I scrape AliExpress without writing code?
Yes. The dashboard request builder lets you paste a URL, set parameters, and copy a generated snippet in Python, Node, Go, PHP, Ruby or cURL. You still need somewhere to run that snippet, but you do not have to author the request logic yourself.
How do I handle JavaScript when scraping AliExpress?
Pass render_js=true. The page runs in a real headless browser, JavaScript executes server-side, and you receive the post-render HTML.
Can I scrape AliExpress from a specific country?
Yes. Pass country_code to route the request through a residential IP in that country. This is useful when content or pricing varies by geography.
What's the rate limit for scraping AliExpress?
Limits are expressed as concurrency per plan, not as per-target rate limits. If AliExpress throttles aggressive patterns, space out requests or use multiple sessions.
How do I get structured JSON from AliExpress?
Pass extract_rules with CSS selectors mapped to field names, or use ai_extract_rules with a natural-language specification. The response comes back as parsed JSON.
Which output format should I choose for an AliExpress job?
Choose rendered HTML if you already have a parser and want full page fidelity. Choose structured JSON via extract_rules or ai_extract_rules if you want named fields and can maintain selectors or a natural-language spec. Choose Markdown if the next step is summarization or analysis rather than field-level extraction. Screenshots are a separate capability for visual verification.
How many credits does a single AliExpress request consume?
Requests start at 1 credit each. Enabling JS rendering on a successful request costs 5 credits. Enabling premium proxies costs 10 credits with JS rendering disabled, or 25 credits with it enabled. Credit validity periods, rollover behaviour, any free starting credits and cancellation terms should be confirmed against the current plan documentation before you commit.