Vestiaire Collective Scraper avatar

Vestiaire Collective Scraper

Pricing

from $1.00 / 1,000 results

Go to Apify Store
Vestiaire Collective Scraper

Vestiaire Collective Scraper

Scrape Vestiaire Collective luxury fashion data effortlessly. Extract product listings, prices, conditions & seller info for price monitoring, market research & business intelligence. Fast, reliable automation.

Pricing

from $1.00 / 1,000 results

Rating

5.0

(4)

Developer

Shahid Irfan

Shahid Irfan

Maintained by Community

Actor stats

2

Bookmarked

19

Total users

5

Monthly active users

5 days ago

Last modified

Share

What does Vestiaire Collective Scraper do?

Vestiaire Collective Scraper is a Vestiaire Collective product listing scraper for collecting structured luxury resale data from public search, category, brand, and tag URLs. You can provide a Vestiaire URL or a keyword, choose a result limit, and export listing records with product details, prices, images, seller information, stock signals, and engagement data.

The dataset is useful for resale market research, price monitoring, competitive analysis, sourcing, and historical catalog tracking. Each run produces clean records that can be downloaded as JSON, CSV, Excel, or XML and connected to downstream workflows.

Why use Vestiaire Collective Scraper?

  • Resale market monitoring - Track brands, categories, prices, colors, sizes, availability, and demand signals across repeated runs.
  • Pricing analysis - Compare numeric prices, formatted prices, currencies, likes, stock values, and seller details across listings.
  • Inventory sourcing - Find products and brands that match a keyword or a curated Vestiaire Collective category URL.
  • Competitive research - Build structured datasets for luxury fashion assortment, brand coverage, and marketplace analysis.
  • Automation-ready output - Export results to files, spreadsheets, databases, dashboards, and workflow tools through Apify integrations.
  • Repeatable collection - Run the Actor on demand or schedule recurring runs to compare listing changes over time.

What data can you extract from Vestiaire Collective?

FieldTypeDescription
idNumber or StringUnique Vestiaire Collective listing identifier.
nameStringListing title.
descriptionStringListing description when provided.
brandIdNumber or StringBrand identifier when provided.
brandNameStringBrand name associated with the listing.
countryStringCountry or marketplace context for the listing.
linkStringAbsolute product or listing URL.
likesNumberNumber of likes shown for the listing.
soldBooleanWhether the listing is marked as sold.
stockNumber, Boolean, or StringStock value or availability status returned for the listing.
universeIdNumber or StringVestiaire Collective market or audience identifier.
createdAtNumberListing creation timestamp when provided.
colorNamesArrayFlattened list of color names.
primaryColorStringFirst available color name.
sizeStringListing size label.
pictureUrlsArrayAbsolute image URLs associated with the listing.
imageCountNumberNumber of unique image URLs in pictureUrls.
priceAmountNumberNumeric listing price.
priceCurrencyStringCurrency code for the listing price.
priceFormattedStringLocalized display version of the price.
sellerIdNumber or StringSeller identifier when provided.
sellerNameStringSeller name or username when provided.
localEligibleBooleanWhether local shipping is available for the listing.
directShippingEligibleBooleanWhether direct shipping is available for the listing.
editorPicksObjectEditor selection flags when provided.
sourceUrlStringVestiaire URL used as the source context for the record.
searchKeywordStringKeyword applied to the search, when one was used.
appliedSortStringSort order applied to the search.
appliedCatalogPathStringCategory path applied to the search, when available.
appliedUniverseIdStringMarket or audience filter applied to the search, when available.

Empty values are omitted from individual dataset items, so optional fields may not appear on every record.

How to use Vestiaire Collective Scraper

  1. Open the Actor in Apify Console.
  2. Paste a public Vestiaire Collective search, category, brand, or tag URL into url, or enter a product keyword in keyword.
  3. Set results_wanted and max_pages for the size of the run.
  4. Enable proxyConfiguration for larger or repeated runs when needed.
  5. Run the Actor.
  6. Review the dataset and download it or connect it to your workflow.

When url is provided, its search query, category path, and URL filters determine the collection context. Use keyword by itself for a keyword search. If both are empty, the Actor uses its default women's catalog context.

Input Parameters

ParameterTypeRequiredDefault or prefillDescription
urlStringNoPrefilled with https://www.vestiairecollective.com/search/?q=gucciPublic Vestiaire Collective search, category, brand, or tag URL. URL query and category filters are used as the collection context.
keywordStringNoPrefilled with gucciKeyword for a product search when url is not supplied.
results_wantedIntegerNo20Maximum number of product listings to save. Minimum value is 1.
max_pagesIntegerNo10Maximum number of result pages to process. Minimum value is 1.
proxyConfigurationObjectNo{ "useApifyProxy": false }Optional Apify Proxy settings for larger or repeated runs.

Output Data

The Actor writes one dataset item per unique listing. Product URLs and image URLs are returned as absolute URLs when available.

Usage Examples

Basic URL Collection

Collect listings from a Vestiaire Collective search URL:

{
"url": "https://www.vestiairecollective.com/search/?q=gucci",
"results_wanted": 20
}

Search for a specific product phrase without supplying a URL:

{
"keyword": "chanel handbag",
"results_wanted": 50,
"max_pages": 10
}

Category and Brand Monitoring

Collect a larger batch from a public category or brand URL for repeat monitoring:

{
"url": "https://www.vestiairecollective.com/women-bags/handbags/gucci/",
"results_wanted": 100,
"max_pages": 8,
"proxyConfiguration": {
"useApifyProxy": true
}
}

Sample Output

{
"id": "65518631",
"name": "Leather handbag",
"description": "Pre-owned leather handbag in good condition.",
"brandId": "37",
"brandName": "Gucci",
"country": "US",
"link": "https://us.vestiairecollective.com/women-bags/handbags/gucci/",
"likes": 18,
"sold": false,
"stock": "1",
"universeId": "1",
"createdAt": 1776303138,
"colorNames": ["White", "Cream"],
"primaryColor": "White",
"size": "One size",
"pictureUrls": [
"https://images.vestiairecollective.com/produit/66074344-1.jpg",
"https://images.vestiairecollective.com/produit/66074344-2.jpg"
],
"imageCount": 2,
"priceAmount": 749,
"priceCurrency": "USD",
"priceFormatted": "$749",
"sellerId": 3201983,
"sellerName": "fashioncloset",
"localEligible": true,
"directShippingEligible": true,
"sourceUrl": "https://www.vestiairecollective.com/search/?q=gucci",
"searchKeyword": "gucci",
"appliedSort": "relevance",
"appliedCatalogPath": "/women/",
"appliedUniverseId": "1"
}

Optional fields such as editorPicks are included when Vestiaire Collective provides them for a listing.

Tips for Best Results

  • Start with a small limit - Use results_wanted: 20 to validate the URL, keyword, and output before collecting a larger dataset.
  • Use public listing URLs - Search, category, brand, and tag pages provide the context needed for collection. Individual product pages are not the primary input format.
  • Keep URL filters focused - A specific brand or category URL usually produces a more useful dataset than a broad marketplace page.
  • Use consistent inputs for monitoring - Repeat the same URL or keyword so price, stock, and engagement changes can be compared over time.
  • Increase limits gradually - Raise results_wanted and max_pages after checking the first dataset preview.
  • Expect optional fields - Sellers and listings may not publish every description, color, size, image, shipping, or seller field.
  • Use proxy settings for larger runs - Enable Apify Proxy when a repeated or larger collection needs additional request stability.

Integrations

  • Google Sheets - Review listing prices, brands, and availability in a shared spreadsheet.
  • Airtable - Build a searchable luxury resale catalog with seller and product metadata.
  • Webhooks - Trigger downstream processing after an Actor run finishes.
  • Make or Zapier - Send fresh listing data to notifications, databases, and business workflows.
  • Apify API - Start runs and retrieve dataset records from your own application.
  • CSV, Excel, JSON, and XML - Export results for analysis, reporting, catalog work, and data pipelines.

Frequently Asked Questions

Can I search Vestiaire Collective by keyword?

Yes. Enter a phrase in keyword, such as gucci belt or chanel handbag, and leave url empty.

Can I use a Vestiaire Collective category or brand URL?

Yes. Provide a public search, category, brand, or tag URL in url. The Actor uses the URL path and its available query or filter context.

What happens when both url and keyword are provided?

The url takes priority. Its search query and category context are used for the run, so use keyword by itself when you want a keyword-only search.

Can I export Vestiaire Collective data to CSV or Excel?

Yes. Apify datasets can be downloaded as CSV, Excel, JSON, XML, and other supported formats.

Can I schedule recurring price monitoring?

Yes. Create an Apify schedule to run the same URL or keyword hourly, daily, weekly, or at another interval, then compare the resulting datasets.

Why is a field missing from a listing?

A field is missing when the source listing does not publish that value. The Actor removes empty values from each dataset item to keep records compact.

Is this an official Vestiaire Collective API?

No. This is an independent data collection Actor and is not affiliated with, endorsed by, or operated by Vestiaire Collective.

Public data collection may be permitted in some situations, but you are responsible for complying with Vestiaire Collective terms, applicable laws, privacy requirements, and the rules that apply to your use case.

  • Nike Product Scraper - Collect Nike product prices, colors, images, inventory, and links for fashion and retail research.
  • Namshi Product Scraper - Extract fashion and beauty product listings, prices, discounts, ratings, and stock data from Namshi.
  • Asos Product Scraper - Collect structured fashion product data from ASOS for pricing, assortment, and competitor analysis.

Support

For issues, feature requests, or missing fields, use the Issues tab on the Actor page. Include the input used, the affected URL or keyword, and a representative dataset item when reporting a problem.

This Actor is intended for legitimate collection of publicly available Vestiaire Collective listing data. Users are responsible for responsible data use, compliance with website terms, privacy rules, intellectual property requirements, and applicable laws. This Actor is not affiliated with Vestiaire Collective.