Vinted Scraper — Fashion Listings EU+US | from $1.50/1K | No Proxy

Built for second-hand fashion resellers monitoring Vinted across France, Germany, Poland, and the US — and for market researchers tracking brand pricing in the sustainable fashion segment.

Pricing: Pay per listing — $1.50/1K. First 10 results free.

No proxy required. No login.

Scrape Vinted fashion listings by keyword search. Returns title, price, brand, size, condition, views, favourites, seller info, and photo URL.

Supports vinted.com (US/global), vinted.fr (France), vinted.de (Germany), vinted.pl (Poland).

How it works

Uses Vinted's catalog API with a session pre-warm technique: the actor establishes a valid session first, then calls the API endpoint directly. This works reliably without a proxy.

No proxy required from Apify cloud IPs. A proxy input is available as a fallback if your IP gets flagged.

Input

Field	Type	Default	Description
searchText	string	—	Search keyword(s), e.g. "nike jacket", "levis 501"
domain	select	www.vinted.com	Vinted regional domain
maxItems	integer	96	Max results (0 = all pages)
proxyConfiguration	object	—	Optional Apify proxy (fallback only)

Output fields

Field	Description
item_id	Vinted numeric item ID
title	Listing title
price	Price (float)
currency	ISO currency code (USD, EUR, GBP, PLN…)
brand	Brand name
size	Size label
status	Condition (e.g. "Very good", "New with tags")
view_count	Number of views
favourite_count	Number of favourites
seller_login	Seller username
seller_id	Seller numeric ID
seller_profile_url	Seller profile URL
url	Direct listing URL
photo_url	Full-size photo URL
domain	Vinted domain used
scraped_at	Scrape timestamp (ISO 8601 UTC)
parse_confidence	Data quality score 0–1
warnings	List of quality warnings

vs. competitors

Feature	This actor	Web.Harvester Vinted / generic HTML scrapers
Access handling	Session pre-warm (no proxy)	Usually fails or needs residential proxy
Multi-domain EU+US	4 domains (fr/de/pl/com)	Usually 1
view_count + favourite_count	Yes	Rarely
parse_confidence signal	Yes	No
Price	$1.50/1K	$2–4/1K

Use with AI agents (MCP)

This actor is tagged MCP_SERVERS — compatible with Claude, GPT-4o, and other MCP-aware agents:

https://mcp.apify.com/?tools=bovi/vinted-marketplace

Pricing example

Volume	Cost
100 listings	$0.15
1,000 listings	$1.50
10,000 listings	$15.00

First 10 results are free. You pay only for listings actually returned.

FAQ

Do I need a proxy? No. The actor uses a session pre-warm technique — no proxy required from Apify cloud IPs. A proxy input is available as a fallback if your IP gets flagged.

Which Vinted domains are supported? vinted.com (US/global), vinted.fr (France), vinted.de (Germany), vinted.pl (Poland). Select via the domain input.

What output formats are available? JSON (default), CSV, and Excel — via the Apify dataset export or API.

What if results come back empty? Check the domain — listings are region-specific. A search on vinted.fr may return results where vinted.com returns none for the same keyword. Also try broader terms.

Pricing

Pay-per-result (PPE). You are charged per listing returned to your dataset.

Caveats

• Session pre-warm dependency: The actor must establish a session before calling the API. This adds ~1–2s per run.
• IP flagging: Apify cloud IPs are generally clean. If you see 403 errors, add a proxyConfiguration (residential recommended).
• Rate limiting: The API has no documented rate limits but avoid very high maxItems in rapid succession.

Integrations

Built for second-hand fashion resellers and market researchers monitoring listings, pricing, and brand presence across Vinted markets — the JSON/dataset output drops into the tools you already run, no glue code:

• n8n / Make / Zapier — trigger a run or pipe every new dataset item into 500+ apps (Google Sheets, Airtable, Slack, HubSpot, your database) with no code: n8n, Make, Zapier.
• Webhooks — fire your own endpoint the moment a run finishes, to push results straight into your pipeline (docs).
• MCP server — expose this actor as a tool to Claude, Cursor, or any MCP client so an AI agent can pull this data mid-conversation (guide).
• API & SDKs — fetch the dataset as JSON, CSV, or Excel through the Apify REST API or the Python / JS SDKs.

See all Apify integrations.

More scrapers from our toolkit

Building a data pipeline? These actors pair well with this one — each runs on your own Apify account with the same pay-per-result pricing, no subscription:

• Allegro Offers
• Amazon Products Scraper
• Autoscout24 Cars Scraper
• Competitor Price Monitor
• Craigslist Scraper
• Doordash Scraper

Chain any of them together from the Integrations tab (the Run succeeded trigger) to build a multi-step workflow — one actor's output feeds the next.

Use it from your existing tools

Use with Claude Desktop / Cursor / Cline (MCP)

Load this actor as a tool in your AI assistant. Call it directly from your AI assistant via the Apify MCP server — no Store browsing needed. Paste this into your MCP client config (e.g. claude_desktop_config.json) and restart the client:

{
  "mcpServers": {
    "apify-vinted-marketplace": {
      "command": "npx",
      "args": [
        "-y",
        "@apify/actors-mcp-server",
        "--tools",
        "bovi/vinted-marketplace"
      ],
      "env": {
        "APIFY_TOKEN": "YOUR_APIFY_TOKEN"
      }
    }
  }
}

Replace YOUR_APIFY_TOKEN with your own Apify API token (free at apify.com → Settings → Integrations). Curated to a handful of tools so the agent selects reliably.

Works with Clay

Run this actor as an HTTP enrichment step inside a Clay table:

• Method: POST
• URL: https://api.apify.com/v2/acts/bovi~vinted-marketplace/run-sync-get-dataset-items?token={{apify_token}}
• Body (JSON): map your Clay columns to the actor input (see the Input section above), e.g. {"searchText": "{{clay_column}}"}

The run finishes synchronously and returns the dataset rows straight into your Clay table. It runs on Apify's cloud under your own token and usage. Synchronous runs must complete within 300 seconds.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.