Get an AliExpress product by id or URL
Returns one AliExpress product: title, sale price, original price, currency, shop name, images, sold count, and category. Pass the numeric product id or the full aliexpress.com/item/{id} URL. Optional country, currency, and language localise the price. A product that does not exist, or is not sold to that country, comes back 404 and is not billed. There is no product description on this surface. For reviews call GET /v1/aliexpress/reviews. For similar items call GET /v1/aliexpress/product/similar.
Request
- Base URL: https://www.socialcrawl.dev/v1
- URL: https://www.socialcrawl.dev/v1/aliexpress/product
- Auth: API key in header x-api-key
Query parameters
AliExpress product id, the numeric id in a product URL: aliexpress.com/item/3256812847028710.html is product id 3256812847028710. Product ids also come back on every row of GET /v1/aliexpress/search and GET /v1/aliexpress/search/hot. (one of: product_id, url; at least one required)
Full AliExpress product URL, for example https://www.aliexpress.com/item/3256812847028710.html. The product id is extracted from the path. (one of: product_id, url; at least one required)
Ship-to country as a two-letter code. Default US. Changes displayed price and availability. A product that exists for US can return empty for another country.
ISO 4217 currency for displayed prices. Default USD. Live-validated: USD GBP CAD EUR UAH MXN TRY RUB BRL AUD INR JPY IDR SEK KRW ILS THB CLP VND.
Copy language as an ISO code. Default EN. Live-validated: EN RU PT ES FR ID IT TH JA AR VI TR DE HE KO NL PL MX CL IN.
Headers
Send no-cache to bypass the response cache and force a live fetch. Billed at the normal endpoint cost; the fresh result is written back to cache for the next caller. Only the no-cache directive triggers this. See the Response Schema guide for details.
Optional UUID that makes the request safely retriable. The key is reserved atomically per account before billing. A concurrent retry receives 409 IDEMPOTENCY_IN_PROGRESS with a Retry-After of 1 second while the original is young, growing to a quarter of the time it has been running (at most 30); a crashed reservation expires after 5 minutes. A replay keeps the cached payload immutable except for billing metadata: credits_used becomes 0, idempotent_replay becomes true, and credits_remaining is refreshed to the current balance. A known current balance appears in both the body and X-Credits-Remaining header; no balance row resolves to 0. On a transient lookup failure, body credits_remaining is null and X-Credits-Remaining is omitted. Completed outcomes expire after 24 hours. If the claim store is unavailable, the request fails closed before billing. GET endpoints do not combine idempotent replay with Server-Sent Events: use Accept: application/json when sending this header. The unsupported key-plus-SSE combination is rejected before billing.
Response
Successful response
Example response
{
"success": true,
"platform": "aliexpress",
"endpoint": "/v1/aliexpress/product",
"credits_used": 1,
"credits_remaining": 4999,
"request_id": "req-abc123",
"idempotent_replay": true,
"meta": {
"hint": {
"code": "search_multi",
"message": "You searched \"matcha\" on 3 platforms one call at a time; /v1/search/multi returns each platform's own search rows in one call at the same price per platform, and a platform with no rows is not charged.",
"method": "GET",
"path": "/v1/search/multi?query=matcha&platforms=instagram,tiktok,youtube"
}
}
}Changes
No recorded changes to this operation across all 1 revision of this API.