Vestiaire Collective Real-Time Data Scraper avatar

Vestiaire Collective Real-Time Data Scraper

Pricing

from $25.00 / 1,000 results

Go to Apify Store
Vestiaire Collective Real-Time Data Scraper

Vestiaire Collective Real-Time Data Scraper

Live Vestiaire Collective resale market data: keyword search, full listing details, seller closets, profiles, and sell-through stats. Results stream to your dataset in real time with price filters, sort options, and webhook delivery.

Pricing

from $25.00 / 1,000 results

Rating

0.0

(0)

Developer

Emmanuel

Emmanuel

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Categories

Share

Vestiaire Collective Real-Time Data — Live Resale Market Intelligence

Live Vestiaire Collective market data for designer resale: keyword listing search, full product details, seller inventory tracking, seller profiles, sell-through stats, and instant deal alerts. Structured JSON streams to your dataset row-by-row while the run is still working — results start appearing in seconds.

⚠️ Free Apify plan notice (read first): Free-tier accounts are limited to 2 results per run. Upgrade to any paid Apify plan for unlimited exports. This is a policy limit, not an error — it is stated here, in the Actor input form, and in the run log.

Who this is for

  • Vintage & thrift resellers sourcing undervalued designer inventory (Poshmark, eBay, Depop, Mercari, Grailed cross-listers)
  • Consignment owners tracking competitor closets and market prices
  • Resale arbitrageurs hunting margin spreads between platforms
  • Fashion market researchers & pricing teams tracking sell-through and trend data
  • AI agents & automations that need structured resale market data via the Apify MCP server

What you can do with it

  • Find undervalued designer & vintage inventory — search "vintage 90s levis 501", "carhartt detroit jacket", "patagonia fleece", "chanel vintage bag", or "y2k baby tee" and sort by newest first to catch fresh steals before anyone else.
  • Price comps & sell-through analysis — pull seller sell-through statistics (items listed vs. sold) to gauge realistic pricing and demand before you buy.
  • Seller inventory monitoring — watch top sellers' full active stock and spot new listings and repricing moves.
  • Instant Slack / Discord deal alerts — pipe every matched item to a webhook the moment it is saved, so your pricing bot or phone buzzes on newly listed steals.
  • Multi-platform pricing sync — feed structured rows into Sheets, Airtable, Make, Zapier, n8n, or your own repricer.

Features

FeatureWhat it doesOutput (featureType)
🔍 Listing SearchLive keyword search with min/max price filters and sort orderlisting_search
✨ Full Details EnrichmentStreams a second enriched row per search result (description, fabric/material, category path, full image gallery, and more) — filter by detailsFetchedlisting_search (detailsFetched: true)
📦 Listing DetailsFull record for specific listings by URL or listing IDlisting_details
👚 Seller Inventory (Closet Listings)Full active inventory of any seller profilecloset_listings
👤 Seller ProfileReseller stats: items sold, closet size, followers, verification badges, bioseller_profile
🧾 Sold Item Comps / HistoryPer-seller sell-through statistics for pricing decisionssold_history
🔗 Scrape By URLDirect processing of any Vestiaire Collective URL — search, seller, category, or listingscrape_by_url

Sold data note: this marketplace does not expose a public per-item sold feed. The Sold Comps feature returns the closest available equivalent — per-seller sell-through statistics (items listed, items sold, sell-through rate, shipping speed, quality pass rate) — so you can still gauge demand and price fairly. This is described in the input form too.

Stream, then enrich: with Enrich with full listing details on, every search result is saved immediately as a fast row, and a second enriched row (detailsFetched: true) follows as soon as its detail page is read. No buffering behind slow items — rows appear in real time, and a timeout can never erase completed work. Keep the last row per item_id for fully enriched data, or filter detailsFetched: true to work with enriched rows only. Enrichment adds a little extra time per listing.

Quick start (10 results in seconds)

The Actor comes prefilled for an instant demo run:

  1. Click Start — no configuration needed.
  2. Defaults: Listing Search on, keywords carhartt detroit jacket, vintage 90s levis 501, patagonia fleece, 10 results per keyword.
  3. Watch the dataset fill row-by-row in real time.

Example searches that work well

GoalKeywordsFilters
Workwear flipscarhartt detroit jacket, carhartt vestmax price: 150
Vintage denimvintage 90s levis 501, levis 550 orange tabmax price: 90
Gorpcorepatagonia fleece, arc'teryx shell, north face nuptsesort: price low to high
Y2K / streetweary2k baby tee, vintage nba jersey, stussy 90ssort: newest first
Designer for cheapchanel vintage bag, celine macadamsort: price low to high
Sneakersvintage nike air max, jordan 1 1985max price: 200

Full input reference

🔍 Listing Search (enableListingSearch, default on)

FieldTypeDefaultNotes
searchKeywordsstring list3 resale examplesRequired when search is on. Any marketplace search term.
searchMaxResultsinteger10Max results per keyword (1–200).
searchSortselectrelevancerelevance, newest (newest first), price_low_to_high, price_high_to_low.
searchMinPrice / searchMaxPriceinteger—Price window in region currency. Applied as a result filter after collection (the marketplace does not expose price as a search parameter) — items outside the window are skipped before the dataset write.
searchFetchFullDetailsbooleanfalseEnrich with full listing details — streams a second enriched row per search result (description, fabric/material, category path, full gallery, and more; detailsFetched: true).

📦 Listing Details (enableListingDetails, default off)

FieldTypeNotes
listingUrlsstring listFull listing URLs (https://www.vestiairecollective.com/...-12345678.shtml).
listingIdsstring listNumeric listing IDs (the digits at the end of a listing URL).

👚 Seller Inventory (enableClosetListings, default off)

FieldTypeDefaultNotes
sellerUsernamesstring list—Seller usernames or numeric profile IDs. Shared by Seller Inventory, Seller Profile, and Sold Comps.
sellerMaxListingsinteger30Max listings per seller (1–500).

👤 Seller Profile (enableSellerProfile, default off)

Uses the same sellerUsernames list. One row per seller: items sold, closet size, followers, verification badges, bio, country, shipping speed.

🧾 Sold Item Comps / History (enableSoldHistory, default off)

Uses the same sellerUsernames list. One row per seller with sell-through statistics (see the sold-data note above).

🔗 Scrape By URL (enableScrapeByUrl, default off)

FieldTypeNotes
scrapeUrlsstring listAny marketplace search URL, seller profile URL, category page, brand feed, or single listing URL. The page type is auto-detected. Non-marketplace URLs are rejected with a clear error.

Run volume

There is no single global cap — each feature section controls its own volume:

  • Listing Search → searchMaxResults (per keyword)
  • Seller Inventory → sellerMaxListings (per seller)
  • Listing Details & Scrape By URL → the number of URLs/IDs you paste

🌍 Region

FieldTypeDefaultNotes
countryselectUSMarket region: US, UK, FR, DE, IT, ES. Controls currency (USD/GBP/EUR) and the recommended proxy country.

🔔 Delivery

FieldTypeDefaultNotes
webhookUrlstring—Optional. Every record is always saved to the dataset; each new row is ALSO POSTed here in real time (Slack, Discord, Zapier, Make, n8n, custom bot).
webhookFormatselectjsonjson = full record object; slack = Slack-friendly message.

Full output field reference

Every listing row carries the shared core so multi-platform agents can union datasets: featureType, scrapedAt, url, item_id, item_url, title, description, main_image_url, additional_image_urls, status, current_price, original_price, currency, discount_percentage, brand, size, condition, category, department, subcategory, color, style_tags, material, likes_count, is_sold, seller_username, seller_id, detailsFetched.

Feature-specific highlights:

GroupFields
Pricingcurrent_price, original_price, currency, discount_percentage, free_shipping, accepts_offers
Productbrand, size, condition, category, department, subcategory, color, material, style_tags, is_vintage, is_authentic
Engagementlikes_count, comments_count, is_sold, position
Seller (listing rows)seller_username, seller_id, seller_location, seller_verified
Seller profile rowsdisplay_name, bio, followers, following, total_sales, total_listings, total_likes, country, is_trusted, usually_ships_within, badges, avatar_url
Sell-through rowsitems_listed, items_sold, sell_through_rate, usually_ships_within, pass_rate, note
Scrape By URL rowspageType (listing / seller / catalog)

Filter any dataset view by featureType: listing_search, listing_details, closet_listings, seller_profile, sold_history, scrape_by_url.

Webhook guide

  1. Paste a webhookUrl (Slack incoming webhook, Discord webhook, Zapier catch hook, Make scenario, n8n webhook, or your own endpoint).
  2. Pick the format: json (full record — best for bots and Sheets) or slack (formatted message with price, brand, size, seller, and link).
  3. Start the Actor. Every saved row is POSTed immediately after the dataset write — deal alerts arrive while the run is still working.
  4. Webhook delivery is best-effort: a failed delivery never stops the run and never loses the dataset row.

MCP / AI agent usage

Add the Actor to any MCP client (Claude, Cursor, …):

claude mcp add --transport http apify "https://mcp.apify.com?tools=<your-actor-id>"

Then ask questions like:

  • "What is the average listing price for a 90s Carhartt Detroit jacket on Vestiaire Collective?"
  • "Find me Patagonia fleece under $60 and send new matches to my Slack."
  • "Compare sell-through rates between seller X and seller Y."

FAQ

Do I need a proxy? Residential connections are used by default and give the most reliable results at scale. Match the proxy country to the Market region.

Why do free runs stop at 2 results? Free Apify plans get a 2-result preview per run. Upgrade to any paid plan for unlimited exports. The run log states this plainly — it is not an error.

How fresh is the data? Every row is collected live at run time. Pair the "newest first" sort with a webhook for deal-alert workflows.

Are there rate limits? Collection is throttled to polite parallel limits with randomized pauses between chunks, which keeps runs stable and reliable.

Why does enrichment take longer? Full detail collection adds a little extra time per listing — but fast rows stream to the dataset the moment each item is discovered, so results appear in real time. Leave "Enrich with full listing details" off for the fastest runs.

Can I get sold prices per item? The marketplace has no public per-item sold feed. Sold Comps returns per-seller sell-through statistics instead — the closest available equivalent.

Free-tier notice

Free Apify plans receive a 2-result preview per run (configurable by the Actor owner via Console environment variables FREE_TIER_MAX_ITEMS and FREE_TIER_MODE). Paying users get full, uncapped output. The limit applies to total records per run across all features.