What Aliexpress DataHub does and who it is for
Aliexpress DataHub delivers structured, real-time data from AliExpress without requiring you to write or maintain any scraping logic yourself. The API is aimed at developers building dropshipping automation, price-monitoring dashboards, product research tools, or comparison engines that depend on up-to-date AliExpress catalog data.
The provider sits at ecommdatahub.com and explicitly markets the service as an alternative to building and babysitting custom web scrapers. It is still under active development — the changelog shows regular updates to endpoint stability, response schema, and feature additions — so teams adopting it should plan for occasional breaking changes and watch the changelog.
Endpoint coverage
The API exposes 36 endpoints in total, organized into several logical groups:
Item detail
There are eight item-detail variants (/item_detail through /item_detail_7, plus /item_detail_simple). Each returns product-level data such as pricing, availability, SKU options, sales counts, reviews, and breadcrumbs. The variants differ in data completeness, regional focus, and performance characteristics. /item_detail_4 is explicitly oriented toward aliexpress.ru. /item_detail_2 requires a follow-up call to an item-description endpoint to fill in properties and description fields — a tradeoff worth knowing before you design your data pipeline.
Recent updates have standardized the available boolean (whether a product is still purchasable), fixed VAT visibility, and added skuImages to most detail endpoints, so the response schema across variants is converging.
Item search
Five keyword search endpoints (/item_search through /item_search_5) let you paginate through listings, sort results, and filter by category ID (catId) or keyword (q). A dedicated Super Deals / PLUS endpoint (/item_search_promotion_deals) targets discounted listings.
Three image-search endpoints (/item_search_image, /item_search_image_2, /item_search_image_3) accept an image URL and return visually similar products. Endpoint #1 and #2 support images from most external sites; endpoint #3 is restricted to AliExpress product images only.
Shipping detail
Five shipping-detail endpoints (/shipping_detail through /shipping_detail_5) return delivery options, estimated delivery dates, and carrier information. They accept an ext parameter that pairs with item-detail responses to provide accurate, item-specific shipping quotes. Endpoints 2–5 expose estimateDelivery and estimateDeliveryDate fields.
Store data
Three store-item search endpoints (/store_item_search, /store_item_search_2, /store_item_search_3) let you query a seller's catalog by storeId, sellerId, or keyword. /store_info and /store_categories round out store-level metadata retrieval.
Supporting endpoints
/item_desc and /item_desc_2 return full product descriptions and property tables. /item_sku provides SKU-level pricing and variant data. Two review endpoints (/item_review, /item_review_2) expose buyer feedback. /base_params returns supported regions, currencies, and locales — a useful starting point for building locale-aware requests. /category_list_1 delivers the AliExpress category tree. Finally, /custom (GET and POST) is a placeholder for bespoke endpoints negotiated directly with the provider.
Pricing
| Plan | Price | Request quota | Rate limit | Overage |
|---|---|---|---|---|
| BASIC | $0 / month | 100 requests / month | — | — |
| PRO | $7.99 / month | 300 requests / day | 100 / hour | $0.0100 / request |
| ULTRA | $24.99 / month | 1,750 requests / day | 500 / hour | $0.0010 / request |
| MEGA | $74.99 / month | 15,000 requests / day | 15 / second | $0.0008 / request |
All paid plans also include a monthly allotment of "Exclusive Requests" (PRO: 30, ULTRA: 100, MEGA: 1,500) which appear to cover access to specific high-cost endpoints; MEGA subscribers can purchase additional exclusive requests at $0.0010 each.
The BASIC tier's 100 requests per month is realistically only enough for initial integration testing. A minimal production use case — say, refreshing 50 product prices twice daily — exhausts that in a single day and lands squarely in PRO territory. At 300 requests per day, PRO is a reasonable starting point for small dropshipping catalogs. ULTRA at 1,750 per day suits medium-volume monitoring, while MEGA at 15,000 per day covers large-scale pipelines.
Note for MEGA subscribers: the provider has communicated that new subscribers currently receive 15,000 requests per day, with a temporary increase to 25,000 available until August 1st, after which the permanent limit will settle at 20,000 per day. Existing uninterrupted MEGA subscribers are not affected by these changes. Custom plans with private endpoints are available by contacting the provider directly.
Performance characteristics
The reported average latency of 1,777 ms is on the high side for a synchronous API call. This is worth factoring into your architecture: if you need sub-second responses for end-user-facing features, adding a caching layer (Redis, DynamoDB, or similar) between your application and Aliexpress DataHub is almost certainly necessary. The flip side is a reported 100% average success rate, which suggests the provider's infrastructure is highly reliable even if individual calls are slow.
Geo-location-based server updates were noted in the changelog, indicating the provider is actively working to reduce latency across regions.
Practical use cases
- Dropshipping automation: Pull item details and SKU-level pricing on demand whenever a customer places an order, then cross-reference shipping estimates using the shipping-detail endpoints.
- Price monitoring: Schedule daily or hourly fetches on a tracked product list. At ULTRA rates (1,750 per day), you can monitor roughly 875 products twice daily within quota.
- Product research tools: Use keyword search and image search to build discovery features, then enrich results with reviews and shipping data.
- Competitor analysis: Combine store-item search with item detail to profile a specific seller's catalog and pricing strategy.
- Locale-aware storefronts: Use
/base_paramsto build dynamic currency and region selectors, then pass the appropriate parameters to detail and shipping endpoints.
Limitations and things to check before integrating
Latency: Nearly 1.8 seconds average means you should not call this API in the critical path of a synchronous user request without caching.
Schema variability across endpoints: Having seven-plus item-detail variants with slightly different fields means you may need to normalize responses on your end. Test the specific variant you plan to use and pin your integration to its documented fields, watching the changelog for schema additions.
Active development: The "Work in Progress" note in the provider's description is genuine — endpoints have been added, renamed, and removed between versions. Build with that in mind: abstract the API calls behind a service layer so schema migrations stay contained.
Overage costs at PRO: At $0.01 per extra request on the PRO plan, overages add up quickly if your traffic spikes. Upgrading to ULTRA drops that rate to $0.001.
No refund policy on upgrades: The provider explicitly states that no refunds will be issued if you subscribe to one plan and later upgrade. Choose your starting plan deliberately.
Getting started
Subscribe to the BASIC plan at no cost to receive API credentials and explore the endpoint catalog. Use /base_params first to understand which locale, currency, and region strings the API accepts. Then hit /item_detail with a known AliExpress item ID to verify your integration and inspect the response schema. Once you have a realistic picture of your daily request volume and latency requirements, evaluate the PRO or ULTRA tier before going live. For high-volume pipelines exceeding MEGA quotas, the provider offers custom plans via direct contact.
