# Vinted Multi-Country Scraper - Listings, Sellers & Reviews (`abotapi/vinted-marketplace-scraper`) Actor

Scrape Vinted across 27 country marketplaces: keyword search with brand, price and condition filters, item and seller URLs, or a seller's full feedback history. Returns price, currency, condition, size, view and favourite counts, seller rating and profile depth per listing.

- **URL**: https://apify.com/abotapi/vinted-marketplace-scraper.md
- **Developed by:** [Abot API](https://apify.com/abotapi) (community)
- **Stats:** 2 total users, 1 monthly users, 50.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Vinted Multi-Country Scraper

Scrapes Vinted, Europe's largest C2C second-hand fashion marketplace, across its 27 country marketplaces: keyword search with brand, price and condition filters, item and seller pages, and a seller's full member feedback history.

### What you get

- **Search mode**: keyword search on any country's catalogue with source-side brand, category, price and condition filters. Every listing carries price + local currency, brand, size, condition, view count, favourite count, photos, and the seller reference.
- **Item detail** (toggle, on by default): full description, colour, upload date and the schema.org condition.
- **Seller profiles** (toggle): the seller's city, country, feedback reputation with positive/neutral/negative counts, item and follower counts, bundle discount, response time and online status.
- **Reviews mode**: every feedback entry for a seller as its own row (rating, comment text, date, reviewer, linked item), plus the seller's summary rating on each row.
- **URL mode**: paste item pages, seller/member pages, or catalogue/search pages (a `page=` parameter starts the walk at that page). Each URL's own hostname picks its market, so links from different countries can be mixed in one run.

### Quick start

1. Pick a **Mode**.
2. Search mode: type **Search keywords** (e.g. `nike air max`), optionally narrow with Category, Brand, Condition or price. URL mode: paste item or member links. Reviews mode: paste member ids or links.
3. Pick the **Country marketplace** (defaults to Germany). Prices come back in that market's own currency (EUR, PLN, GBP, SEK, ...).
4. Set **Max items** if you want a bounded run. `0` (the default) keeps going until the source runs out of results.

### Output

| Field | Sample value |
|---|---|
| `itemId` | `"0000000000"` |
| `title` | `"Sample knitted winter sweater"` |
| `brandTitle` | `"Sample Brand"` |
| `priceAmount` | `12.5` |
| `currency` | `"EUR"` |
| `condition` | `"Very good"` |
| `size` | `"M"` |
| `color` | `"Green"` |
| `viewCount` | `142` |
| `favouriteCount` | `18` |
| `seller.username` | `"sample_seller"` |
| `seller.feedbackReputation` | `4.9` |
| `url` | `"https://www.vinted.de/items/0000000000"` |

Samples above are illustrative placeholders, not real listings. A review row (Reviews mode) carries `reviewId`, `rating`, `body`, `createdAt`, `reviewerUsername` and the seller's summary rating.

The second, larger price the site displays next to the listing price is the buyer-protection fee added at checkout, not a former price - this actor therefore does not emit a "was price" field.

### Modes and scope (what applies where)

| Input | Search | URL | Reviews |
|---|:---:|:---:|:---:|
| Country marketplace | yes | fallback only | fallback only |
| Keywords, category, brand, condition, price, sort | yes | no | no |
| URLs (item / member / catalogue pages) | no | yes | no |
| Sellers | no | no | yes |
| Fetch item detail / Fetch seller profiles | yes | yes | n/a (reviews are the product) |

In URL and Reviews modes each pasted URL always uses its own market (the marketplace keeps one catalogue per country, and a seller's full item list only shows on the seller's home market). The Country marketplace setting is the fallback for bare numeric ids and unknown links.

### Notes and limits

- Anonymous search honours two sort orders: the default relevance ranking and "newest first". Price sorting is only offered to signed-in members on the site, so it is not offered here.
- Condition labels come back in the market's language (e.g. "Sehr gut" on the German market); the schema.org condition enum (`conditionSchema`, e.g. `UsedConditions`) is language-stable.
- Sold and removed items 404 on read. The run reports them as unavailable and continues; in incremental mode a tracked listing that disappears after a complete scan is reported as `EXPIRED`.
- The actor fails loudly when the marketplace refuses to serve pages (a connection problem is never reported as "no results"); when some pages are refused but real rows were delivered, the run reports `Partial results:`.

### Resume & recurring updates

Two different tools, both optional:

- **`resumeFromRunId`**: continue ONE interrupted run. Paste a previous run id or dataset id and the run skips (and does not re-charge) records that run already collected.
- **`incrementalMode`**: recurring monitoring of the same search/URLs/sellers (e.g. daily). The first run returns everything as `NEW`; later runs return only `NEW`, `UPDATED` and `REAPPEARED` records, and listings that sold or were removed come back as `EXPIRED` after a complete scan. State is kept separately per mode, country and setup; name a campaign with **`stateKey`** to keep it stable or deliberately share it. **`emitUnchanged`** and **`emitExpired`** return extra rows you already have (and bill for them), so both default to off.

### Billing

Pay per event: a start event, a per-result event for every listing or review returned, and a `detail-enrichment` surcharge charged once per listing whose detail page and/or seller profile was actually fetched and returned. Suppressed (unchanged) incremental rows are never charged the surcharge.

### Send results into your apps (MCP connectors)

Select one or more MCP connectors under **`mcpConnectors`** to mirror results into the app you already use, alongside the dataset. Supported: Notion, Linear, Airtable, and Apify. Authorize a connector once under Apify -> Settings -> Integrations.

- **`mcpConnectors`**: the connectors to export into. The connector receives a condensed, human-readable summary per item (title + key fields), not the full JSON; the complete record always stays in the dataset. Leave empty to skip.
- **`notionParentPageUrl`**: for the Notion connector, the URL (or id) of the page under which item pages are created. Required for Notion; ignored by other connectors.
- **`maxNotifyListings`**: cap on items written to each connector per run (default 50). Does not affect the dataset.

### Computing usage

A search of 48 listings per page costs one page read per result page. A bounded run (`Max items: 24`, detail + seller profiles on) reads one result page, then 24 listing pages and 24 seller profiles. Local development runs honour `APIFY_PURGE_ON_START=0` and the platform injects the proxy settings itself.

# Actor input Schema

## `mode` (type: `string`):

'search' finds listings by keyword with the marketplace's own filters. 'url' scrapes any item page or seller/member page you paste. 'reviews' pulls a seller's full feedback history (rating + every comment).

## `country` (type: `string`):

Which country's catalogue to search, and which market session to use when a pasted URL does not name one. Each country has its own catalogue, language and currency; item and seller ids work across all of them. Pasted URLs always pin their own market from the URL itself.

## `queries` (type: `array`):

One or more free-text keywords, e.g. 'nike air force' or 'robe vintage'. The item budget (Max items below) is split evenly across keywords.

## `categoryId` (type: `string`):

A catalogue id, e.g. '1242' (sneakers). Find it in a category page URL: vinted.<tld>/catalog/<id>-<name>. Narrows a keyword search, or browses the whole category when Search keywords is left empty. Search mode only.

## `brandId` (type: `string`):

A brand id, e.g. '53' (Nike). Find it in a brand page URL: vinted.<tld>/brand/<id>-<name>. Search mode only.

## `conditions` (type: `array`):

Only return items in these conditions. Leave empty for any condition. Search mode only.

## `minPrice` (type: `integer`):

Only return items priced at or above this amount, in the selected market's currency. Search mode only.

## `maxPrice` (type: `integer`):

Only return items priced at or below this amount, in the selected market's currency. Search mode only.

## `sortBy` (type: `string`):

Order of the returned results. The marketplace honours 'newest first' and its default relevance ranking for anonymous readers; price sorting is available on the site itself once signed in, so it is not offered here. Search mode only.

## `urls` (type: `array`):

Paste one or more item pages (/items/<id>-<slug>), seller/member pages (/member/<id>), or catalogue/search pages (/catalog?search\_text=...). A member URL enumerates every item that seller has listed; a catalogue URL walks that search from the page parameter it carries. Each URL's own hostname picks its market, so links from different countries can be mixed; filter fields above are ignored in this mode.

## `sellers` (type: `array`):

Seller numeric member ids or full /member/<id> URLs (any country) to fetch feedback for. A pasted URL's own hostname picks the market; a bare numeric id uses the Country marketplace above.

## `fetchDetails` (type: `boolean`):

Adds the full description, colour, upload date and schema condition to each listing. Identity, price, brand, size, condition label, view/favourite counts and photos are already included without this toggle. Billed as the per-listing detail-enrichment surcharge when a row is returned.

## `fetchSellerProfiles` (type: `boolean`):

Adds seller depth to each listing: city, country, feedback reputation with positive/neutral/negative counts, item and follower counts, bundle discount, response time and online status. Also billed as the detail-enrichment surcharge (once per listing, together with Fetch item detail).

## `maxPages` (type: `integer`):

Stop after this many result pages per keyword/category/URL entry. Leave empty for as many pages as needed (bounded by Max items below).

## `maxItems` (type: `integer`):

Hard cap on total records (listings or reviews) returned across the whole run. 0 = unlimited: the run keeps going until the source runs out of results.

## `proxy` (type: `object`):

Runs use the platform's residential proxy pool by default: the marketplace refuses ordinary datacenter exits, so residential connections are required for reliable runs. You can pin the pool to the market's country or paste your own proxy URLs here instead.

## `mcpConnectors` (type: `array`):

Optionally send the scraped results into the apps you already use, via Model Context Protocol (MCP) connectors. Authorize a connector once under Apify -> Settings -> Integrations, then select it here. The connector receives a condensed, human-readable summary per item (title + key fields), not the full JSON; the complete record stays in the dataset. Leave empty to skip. Supported: Notion (https://mcp.notion.com/mcp), Linear (https://mcp.linear.app/sse), Airtable (https://mcp.airtable.com/mcp), Apify (https://mcp.apify.com).

## `notionParentPageUrl` (type: `string`):

URL (or id) of the Notion page under which item pages are created. Required to enable the Notion export; ignored by other connectors.

## `maxNotifyListings` (type: `integer`):

Cap on items written to each connector per run. Does not affect the dataset.

## `resumeFromRunId` (type: `string`):

Paste a previous run ID or dataset ID to continue an interrupted crawl without returning or charging for records already collected there. For recurring daily monitoring of the same search/URLs/sellers, use Incremental mode below instead.

## `incrementalMode` (type: `boolean`):

Turn this on for daily or recurring monitoring. The first run returns everything as NEW. Later runs normally return only NEW, UPDATED, and REAPPEARED records; a sold/removed listing on this marketplace comes back as EXPIRED. Turn on "Emit unchanged" or "Emit expired" only when you also want those records returned (and billed). State is kept separately per mode, country and search/URL/seller/detail setup; use State key when you want to name or deliberately share a monitoring campaign. To continue one specific interrupted run instead, use Resume from a previous run above.

## `stateKey` (type: `string`):

Optional. Name this monitoring campaign to keep its state stable, or to deliberately share state across differently-configured runs. Leave empty to let the actor derive a key automatically from the mode, country, search/URL/seller and detail settings - different setups then never mix state with each other.

## `emitUnchanged` (type: `boolean`):

Off by default. Turn on to also return records that have not changed since the last run, marked UNCHANGED. This returns - and bills - extra rows you already have, so leave it off unless you specifically want the full snapshot every run.

## `emitExpired` (type: `boolean`):

Off by default. Turn on to also return records that were present in a previous run but are no longer found (sold or removed), marked EXPIRED. Only produced once a run has fully scanned the tracked scope - not when Max items capped it, when Resume was used, or when a run scanned nothing. This returns - and bills - extra synthetic rows, so leave it off unless you need expiry tracking.

## Actor input object example

```json
{
  "mode": "search",
  "country": "de",
  "queries": [
    "nike"
  ],
  "sortBy": "relevance",
  "urls": [
    "https://www.vinted.de/member/3162455054"
  ],
  "sellers": [
    "https://www.vinted.de/member/3162455054"
  ],
  "fetchDetails": false,
  "fetchSellerProfiles": false,
  "maxItems": 20,
  "proxy": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  },
  "maxNotifyListings": 50,
  "incrementalMode": false,
  "emitUnchanged": false,
  "emitExpired": false
}
```

# Actor output Schema

## `overview` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "mode": "search",
    "country": "de",
    "queries": [
        "nike"
    ],
    "urls": [
        "https://www.vinted.de/member/3162455054"
    ],
    "sellers": [
        "https://www.vinted.de/member/3162455054"
    ],
    "proxy": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ]
    },
    "incrementalMode": false,
    "emitUnchanged": false,
    "emitExpired": false
};

// Run the Actor and wait for it to finish
const run = await client.actor("abotapi/vinted-marketplace-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "mode": "search",
    "country": "de",
    "queries": ["nike"],
    "urls": ["https://www.vinted.de/member/3162455054"],
    "sellers": ["https://www.vinted.de/member/3162455054"],
    "proxy": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
    },
    "incrementalMode": False,
    "emitUnchanged": False,
    "emitExpired": False,
}

# Run the Actor and wait for it to finish
run = client.actor("abotapi/vinted-marketplace-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "mode": "search",
  "country": "de",
  "queries": [
    "nike"
  ],
  "urls": [
    "https://www.vinted.de/member/3162455054"
  ],
  "sellers": [
    "https://www.vinted.de/member/3162455054"
  ],
  "proxy": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  },
  "incrementalMode": false,
  "emitUnchanged": false,
  "emitExpired": false
}' |
apify call abotapi/vinted-marketplace-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,abotapi/vinted-marketplace-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/1THqtZOjUi1xwmeZ2/builds/OnYeOdwdiUav1KoZ7/openapi.json