Vestiaire Collective seller listings

GET https://api.api.sh/vestiairecollective/v1/seller-items
1 credit / call e-commerce try it in the playground →

A Vestiaire Collective seller's listings, 48 per page, with sort and a sold filter: id, name, brand, model, price, currency, discount, sold flag, likes, size, colours, country, listing date, description, shipping flag, link and photos, with the total. Pass next_page back as page; null on the last page.

Every response includes credits_used: the credits this call cost.

Parameters

nametypedescription
id string The seller's numeric id, e.g. 4085582. Example: 4085582
url string A vestiairecollective.com profile link, instead of id.
sort relevance | price-asc | price-desc relevance (default), price-asc or price-desc.
sold true | false true: only sold items; false: only items still for sale; omit for both.
page integer Page number. Pass next_page from the previous response; next_page is null on the last page.

Every endpoint also takes fresh, raw, fields (see lean responses and caching).

Example

curl "https://api.api.sh/vestiairecollective/v1/seller-items?id=4085582" \
  -H "x-api-key: $APISH_KEY"

Response

A JSON object with the fields described above, plus raw (the source's own data), cached, fetched_at and credits_used. Errors return {"success": false, "error": "…"} with the HTTP status (see errors). A lookup that ran but found nothing (404) costs the price above; refused calls and errors on our side are free (what's charged).

The fastest way to see the full response is the playground: it runs this endpoint with your account and shows the exact JSON.