Vestiaire Collective Scraper
Pricing
Pay per usage
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
Pay per usage
Rating
0.0
(0)
Developer
Shahid Irfan
Actor stats
0
Bookmarked
2
Total users
1
Monthly active users
9 hours ago
Last modified
Categories
Share
Extract product listings from Vestiaire Collective with a simple keyword-based setup. Collect rich listing data including brand, pricing, likes, sizing, flattened colors, complete image URLs, seller metadata, and product links at scale.
Features
- Simple input setup - Run with either a listing URL or a keyword, plus result/page limits.
- Internal smart defaults - Listing source, sort, locale, and core filters are configured internally.
- Pagination handling - Continues collecting until
results_wantedormax_pagesis reached. - Structured product output - Returns normalized listing fields ready for analytics pipelines.
- Clean dataset records - Omits empty values so output is compact and easier to process.
Use Cases
Resale Market Monitoring
Track second-hand luxury product trends by brand, category, and demand signals. Build historical datasets to monitor shifts in pricing and stock availability.
Competitive Intelligence
Compare category depth and listing quality across different URL patterns. Identify where specific brands or segments are most active.
Pricing Analysis
Collect listing price snapshots and combine them with engagement signals such as likes. Use this data to estimate sell-through potential and market positioning.
Inventory Sourcing Research
Discover high-volume categories and product types suitable for sourcing decisions. Filter by tags, keyword, or curated listing URLs.
Input Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
url | String | No | https://www.vestiairecollective.com/search/?q=gucci | Vestiaire search/category/brand/tag URL |
keyword | String | No | gucci | Keyword override for listing search |
results_wanted | Integer | No | 20 | Maximum number of products to return |
max_pages | Integer | No | 10 | Maximum pages to process per URL |
proxyConfiguration | Object | No | Apify Proxy | Proxy settings |
When both are empty, the actor uses an internal default listing context.
Output Data
Each dataset item can contain the following fields:
| Field | Type | Description |
|---|---|---|
id | Number | Listing identifier |
name | String | Listing title |
description | String | Listing description |
brandId | Number | Brand identifier |
brandName | String | Brand name |
country | String | Country context |
link | String | Product URL |
likes | Number | Number of likes |
sold | Boolean | Sold flag |
stock | Boolean | Stock value/status |
universeId | Number | Universe id |
createdAt | Number | Creation timestamp |
colorNames | Array | Flattened color names |
primaryColor | String | Primary color name |
size | String | Size label |
pictureUrls | Array | Listing image URLs |
imageCount | Number | Total number of unique image URLs |
priceAmount | Number | Numeric price amount |
priceCurrency | String | Currency code |
priceFormatted | String | Localized display price |
sellerId | Number | Seller identifier |
sellerName | String | Seller name |
localEligible | Boolean | Local shipping eligibility |
directShippingEligible | Boolean | Direct shipping eligibility |
editorPicks | Object | Editor selection flags |
sourceUrl | String | Input URL used for this record |
searchKeyword | String | Effective keyword applied |
appliedSort | String | Applied sort value |
appliedCatalogPath | String | Applied category path |
appliedUniverseId | String | Applied universe id |
Usage Examples
Basic Listing Extraction
{"url": "https://us.vestiairecollective.com/women-accessories/watches/#categoryParent=Accessories%236_category=6%20%3E%20Watches%2344_gender=Women%231","results_wanted": 20}
Keyword Search
{"keyword": "gucci","results_wanted": 50,"max_pages": 10}
Sample Output
{"id": "65518631","name": "Leather handbag","brandId": "37","brandName": "Gucci","country": "US","link": "https://us.vestiairecollective.com/women-bags/handbags/gucci/","likes": 18,"stock": "1","universeId": "1","createdAt": 1776303138,"colorNames": ["White", "Cream"],"primaryColor": "White","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","directShippingEligible": true,"sourceUrl": "https://us.vestiairecollective.com/women/#gender=Women%231","searchKeyword": "gucci","appliedSort": "relevance","appliedCatalogPath": "/women/","appliedUniverseId": "1"}
Tips For Best Results
Start With Small Runs
- Use
results_wanted: 20to validate your input setup. - Increase result limits only after verifying output quality.
Prefer Stable Listing URLs
- Use listing pages instead of individual product detail pages.
- Keep category paths consistent for easier trend comparisons.
Tune Filters Incrementally
- Adjust
keywordand run smaller batches first. - Compare output volume after each filter change.
Use Proxy For Larger Runs
- Residential proxy is recommended for production-scale runs.
- Keep request volume aligned with your desired data freshness.
Integrations
- Google Sheets - Export product records for quick analysis.
- Airtable - Build searchable luxury resale datasets.
- Make - Trigger automated enrichment and notifications.
- Zapier - Connect output to CRM, docs, or alerting tools.
- Webhooks - Forward new data to your own services.
Export Formats
- JSON - Programmatic workflows and APIs.
- CSV - Spreadsheet and BI analysis.
- Excel - Business reporting.
- XML - Legacy system integration.
Frequently Asked Questions
Does this actor support keyword search?
Yes. Use the keyword input.
Why are some fields missing in certain records?
Some listings do not expose every optional field, and empty values are intentionally omitted from output.
How can I limit run time?
Use lower values for results_wanted and max_pages.
Is proxy required?
Proxy is optional for small runs, but recommended for production stability.
Support
For support requests and feature suggestions, open an issue through the Apify actor page.
Resources
Legal Notice
This actor is designed for legitimate data collection use cases. You are responsible for complying with website terms, applicable laws, and responsible usage practices in your jurisdiction.