Vinted Scraper - Secondhand Fashion Listings

Scrape Vinted secondhand & vintage fashion listings into clean, structured data - no Vinted account or API key required. Works across Vinted's regional sites (vinted.com, vinted.co.uk, vinted.de, vinted.fr, and more).

What you get (per listing)

• Item id and canonical listing URL
• Title
• Price (amount + currency), plus totalItemPrice (price incl. Vinted Buyer Protection) and the serviceFee
• Brand, size, and condition (New with tags / New without tags / Very good / Good / Satisfactory)
• Favourite count, view count and promoted flag
• Seller login, id, profile URL and business-seller flag
• Photos - primary photoUrl plus the full photoUrls list

Full field list

id, title, url, price, currency, totalItemPrice, serviceFee, brand, size, condition, status, favouriteCount, isFavourite, viewCount, isPromoted, sellerLogin, sellerId, sellerProfileUrl, isBusinessSeller, photoUrl, photoUrls, path, scrapedFrom.

Input

• Search keyword - a term such as nike, carhartt jacket, or y2k jeans. The simplest way to pull a full, paginated result set.
• Vinted catalog / search URLs - build a filtered search on any Vinted site (category, brand, size, price, condition, sort order...) and paste the result URL(s). Every filter in the URL is forwarded to Vinted's catalog API and paginated in full. Each URL keeps its own regional host.
• Domain / region - which Vinted site to search when using the keyword (default vinted.com).
• Max listings caps the run. (Vinted itself caps deep pagination at roughly 960 results per individual search.)
• Proxy - Vinted rate-limits datacenter IPs, so the actor uses Apify Residential proxy by default.

Example input

{
  "searchText": "carhartt jacket",
  "domain": "vinted.co.uk",
  "maxItems": 200,
  "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"] }
}

Or drive it from a filtered catalog URL:

{
  "startUrls": [{ "url": "https://www.vinted.com/catalog?search_text=nike&price_to=50&order=newest_first" }],
  "maxItems": 500
}

Example output (one record)

{
  "id": 9200043363,
  "title": "Nike Court Vision Low Men's Leather Lace-Up Sneakers Black/White",
  "url": "https://www.vinted.com/items/9200043363-nike-court-vision-low-mens-sneakers",
  "price": { "amount": 19.99, "currency": "USD" },
  "currency": "USD",
  "totalItemPrice": { "amount": 21.69, "currency": "USD" },
  "serviceFee": { "amount": 1.7, "currency": "USD" },
  "brand": "Nike",
  "size": "7",
  "condition": "Very good",
  "favouriteCount": 5,
  "sellerLogin": "sierrac71",
  "photoUrl": "https://images1.vinted.net/t/.../f800/....jpeg",
  "scrapedFrom": "www.vinted.com"
}

How it works

Vinted's web app is backed by an internal JSON API. This actor reads the catalog search endpoint (/api/v2/catalog/items) directly, so every field comes from one clean response - there are no per-listing detail requests (fast + cheap), and pagination follows Vinted's real page parameter.

A cold call to that endpoint returns HTTP 401 (invalid_authentication_token) because it needs the anonymous access_token_web cookie a normal page view sets. The actor handles this by first GETting the region homepage on a persistent browser-impersonating session (which seeds that cookie plus Cloudflare's __cf_bm), then calling the API on the same session so the cookies ride along. If the token is ever rejected mid-crawl, the actor automatically re-primes it on a fresh proxy IP and retries.

• Durable: parses structured JSON, not brittle CSS selectors.
• Multi-region: one actor covers every Vinted marketplace.
• Export as JSON, CSV, Excel, or pull via the Apify API.

Great for resellers and analysts doing pricing intelligence, brand & trend monitoring, and secondhand-market research. This is public marketplace data for research; it is not a consumer report and must not be used for FCRA-covered purposes.