/vinted/products/search

POST /api/vinted/products/search

Price: 20 credits

Search Vinted items by keyword with optional category, brand, size, condition, color, material and price filters

How to use it

Use to find second-hand listings on Vinted by keyword in one country marketplace, picked with domain. Narrow with catalog, brand, size, condition, color and material IDs plus a price range, and choose the ordering; condition and size text comes back in the domain's own language. Vinted returns at most 960 listings per query, so split a broad search by filter or price band.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• domain string — Vinted country domain to search (default: "vinted.de"; one of: "vinted.de", "vinted.fr", "vinted.es", "vinted.it", "vinted.nl", "vinted.pl", "vinted.co.uk")
• keyword string required — Search keyword (examples: "nike", "levis jeans"; minLength: 1)
• count integer required — Max number of results to return; one query reaches at most 960 listings (examples: 20; min: 1)
• order string — Result ordering (default: "relevance"; one of: "relevance", "newest_first", "price_high_to_low", "price_low_to_high")
• catalog_ids array nullable — Filter by Vinted category (catalog) IDs (examples: [1904])
• brand_ids array nullable — Filter by brand IDs (examples: [53])
• size_ids array nullable — Filter by size IDs (examples: [57])
• status_ids array nullable — Filter by condition (status) IDs (examples: [6])
• color_ids array nullable — Filter by color IDs (examples: [9])
• material_ids array nullable — Filter by material IDs (examples: [44])
• price_from number nullable — Minimum price (min: 0)
• price_to number nullable — Maximum price (min: 0)
• currency string nullable — Currency code for price filters (examples: "EUR")

Response

• @type string (default: "VintedSearchItem")
• id integer required
• title string required
• url string nullable
• path string nullable
• price object nullable
  • @type string (default: "VintedPrice")
  • amount number nullable
  • currency string nullable
• total_price object nullable
  • @type string (default: "VintedPrice")
  • amount number nullable
  • currency string nullable
• service_fee object nullable
  • @type string (default: "VintedPrice")
  • amount number nullable
  • currency string nullable
• brand string nullable
• size string nullable
• status string nullable
• image string nullable
• images array (default: [])
• favourite_count integer (default: 0)
• view_count integer (default: 0)
• is_promoted boolean (default: false)
• user object nullable
  • @type string (default: "VintedSearchUser")
  • id integer required
  • alias string nullable
  • profile_url string nullable
  • is_business boolean (default: false)

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.