Get AliExpress data with one API

They are the same item written two ways, and the gap between them is a constant: 2,251,799,813,685,248, which is 2^51. Measured on four products on 2026-08-27, for example 3256806194871771 minus 2^51 gives 1005006381186523. Both forms are accepted as product_id and the API echoes back whichever form you sent, so pick one and stay consistent if you are joining against your own table.

Every variant carries image and thumbnail, and on a 50-variant running shoe all 50 were populated. Only 5 were distinct because AliExpress attaches the photo to the color, not to the color and size pair, so all ten sizes of the blue shoe point at the same blue photo. If you want the color swatch set on its own, sku_properties[].value_details[] carries one image, thumbnail and color_hex per color value.

No, and that is the usual reason a scraped price looks wrong. On one measured listing price_min was 14.99 EUR and price_max 18.79 EUR, with EU 43 at 16.19 and EU 44 at 16.69. price_current (14.99) is the pre-selected SKU, not an average and not the minimum in every case. Read sku_variants[].price.sale if you need the price for a specific size.

AliExpress publishes the figure as a rounded label rather than an exact number, so product_detail returns sold_count null and puts the label in sold_text, for example "50,000+ sold". The search action does parse that label into sold_count, where "1,000+ sold" became 1000 and "24 sold" became 24. Treat search's sold_count as a floor, not an exact count.

Quite a lot. The same product returned 2.64 USD shipping to the US with an 8 to 14 day estimate, and 14.99 EUR to Germany with 5 to 11 days. The store_url host switched from aliexpress.com to de.aliexpress.com, and sold_text came back in German. meta also reports province_sent, which is defaulted from the country (US gave California, DE gave Berlin), so set province yourself if you need a state-accurate delivery estimate.

Because the language parameter localizes them. The same shoe returned props keyed "Color" and "Shoe Size" under language=en and "Farbe" and "Schuhgroesse" under language=de. sku_id is stable across languages, so match on sku_id and use props only for display.

They are two different counters read at two different moments. On 2026-08-27 the same product returned review_count 1354 from product_detail and total_reviews 1352 from reviews. The reviews action also gives you summary.distribution with a count per star (5: 1103, 4: 132, 3: 55, 2: 15, 1: 49) plus positive_num, neutral_num and negative_num, which is the block to use when the numbers have to add up.

It marks a sponsored placement. Search rows come back with product_type either "natural" or "ad", and the ad rows are interleaved with organic ones in the same results array. If you are measuring rank or building a price index, filter on product_type equal to "natural" first, otherwise paid placements will move your numbers around.

AliExpress API is a ReefAPI endpoint group for product search, prices, variants, reviews and shipping. It returns live JSON through POST requests under /aliexpress/v1.

Yes. ReefAPI starts with 1,000 free credits, no card required. AliExpress calls use the same shared credit balance as every other ReefAPI engine.

No login to AliExpress is needed for the API response. You call ReefAPI with your x-api-key header, and the playground can run live examples before you create a production key.

The page example is captured from a live search call, and production requests fetch live data through ReefAPI rather than a static sample.

AliExpress actions currently cost 1-2 credits per successful call. Failed or blocked calls are free, and all APIs draw from one credit pool.

Yes. Connect ReefAPI once through MCP and your assistant can call aliexpress actions with the same key, credit pool and JSON envelope used by normal REST requests.