Vinted Search Scraper

Export Vinted marketplace search listings by keyword, price range, brand IDs, catalog IDs, country domain, and sort order.

Use this actor when you need a repeatable CSV, JSON, Excel, or API export of Vinted listings for resale research, price monitoring, inventory discovery, marketplace analytics, or AI-agent workflows.

At a glance

• Input: Search text, marketplace domain, price filters, brand IDs, catalog IDs, sort order, page, and result limit.
• Output: Listing IDs, titles, prices, currency, brand, size, status, listing URL, photos, seller fields, favorite/view counts, and scrape time.
• Marketplace domains: Use domains such as www.vinted.com, www.vinted.fr, or other supported Vinted domains.
• Best for: Vinted listing exports, resale pricing research, saved-search monitoring, and marketplace automation.
• No login required: Uses public listing search data.

What can it do?

• Export Vinted search listings: Save listing titles, URLs, prices, currency, brands, sizes, status, and photos.
• Track marketplace prices: Combine search text, price filters, and sort order for repeatable price snapshots.
• Collect seller fields: Add seller IDs, logins, and profile URLs when available.
• Filter by catalog or brand: Use Vinted IDs to narrow the search beyond text.
• Use as a Vinted search API alternative: Run from the Apify UI, API, schedules, webhooks, or the official Apify MCP server.

Common workflows

• Resale research: Compare listing prices for a brand, size, or item type.
• Inventory discovery: Export public listings that match a niche or search term.
• Price monitoring: Schedule daily runs and compare prices, favorites, and listing counts.
• Seller research: Capture seller profile URLs for public seller context.
• AI-agent analysis: Let an agent collect listing rows before summarizing demand and price bands.

Input example

{
  "searchText": "nike sneakers",
  "maxItems": 50,
  "domain": "www.vinted.com",
  "priceMin": 10,
  "priceMax": 80,
  "brandIds": [],
  "catalogIds": [],
  "order": "newest_first",
  "page": 1,
  "perPage": 96,
  "includeSeller": true
}

Output example

{
  "id": "123456789",
  "title": "Nike Air sneakers",
  "priceAmount": 42,
  "currency": "EUR",
  "brandTitle": "Nike",
  "sizeTitle": "42",
  "status": "Very good",
  "url": "https://www.vinted.com/items/123456789",
  "photoUrls": ["https://images1.vinted.net/..."],
  "sellerId": "987654",
  "sellerLogin": "example_seller",
  "sellerProfileUrl": "https://www.vinted.com/member/987654-example-seller",
  "favoriteCount": 12,
  "viewCount": 88,
  "scrapedAt": "2026-07-03T10:00:00.000Z",
  "searchText": "nike sneakers"
}

Tips for best results

• Use the Vinted domain for the country or marketplace you want.
• Keep the first run small when testing brand IDs or catalog IDs.
• Use price filters to reduce broad searches.
• Turn on includeSeller only when seller fields matter.
• Use the same query and filters for scheduled price monitoring.

Limits and caveats

• The actor extracts public search listing data. It does not log in, message sellers, or purchase items.
• Vinted domains, filters, and field availability vary by country.
• Brand and catalog IDs must be Vinted IDs, not plain names.
• Some counters or seller fields may be missing for individual listings.

API usage

curl "https://api.apify.com/v2/acts/fetch_cat~vinted-search-scraper/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "searchText": "nike sneakers",
    "domain": "www.vinted.com",
    "maxItems": 50,
    "includeSeller": true
  }'

MCP and AI agents

You can run this actor through the official Apify MCP server at https://mcp.apify.com.

For a focused single-actor tool, use:

https://mcp.apify.com?tools=fetch_cat/vinted-search-scraper

Agent-friendly inputs are searchText, maxItems, domain, priceMin, priceMax, brandIds, catalogIds, order, page, perPage, and includeSeller.

Support

If a run fails, returns no data, or a field looks wrong, open an issue from the Actor page.

Please include the Apify run ID or run URL, input JSON, one example public URL, query, or input item, what you expected, and what the dataset returned. Small reproducible inputs make parsing or site-layout issues much faster to fix.