Vinted Scraper & Price Change Monitor

Turn a public Vinted search into clean rows, or compare it with your saved watch list.

Paste a catalog search URL from your browser. Supported URL filters carry over; regional availability requires validation.

🚀 Start in 60 seconds

Paste https://www.vinted.co.uk/catalog?search_text=nike, keep Collect listings and start with the default 100-row limit. Inspect listing rows and coverage together.

{"catalogUrls":["https://www.vinted.co.uk/catalog?search_text=nike"],"maxListings":100}

🎯 Choose the right workflow

Collect listings returns every matching listing as a typed row.

Monitor changes returns the current listing observations plus new listings, price drops, price rises, condition changes and listings absent from a complete comparison. Every verified listing observation is charged, including unchanged ones. Calculated changes are included without additional charge.

Monitoring remembers observations within your configured search limits.

On the next run, the same search and namespace compare current observations with the saved baseline. Unchanged observations are still delivered and charged; only actual differences produce free change rows.

📦 What you get

Actual UK catalog observations from the private QA run, 6 September 2026.

Field	Meaning
listingId	Stable public ID, safe to use as a key across runs
title	Listing title
priceAmount, currency	Asking price as shown publicly
brand, size, status	Brand, size label and condition
favouriteCount	Public favourite count
sellerId, sellerLogin	Public seller identity
photoUrl, url	Primary image and the canonical listing link
collectedAt	When this row was read

A change row adds changeKind (NEW, PRICE_DROP, PRICE_RISE, STATUS_CHANGED, GONE), plus previousPriceAmount, priceDeltaAmount, previousStatus, firstSeenAt and previousSeenAt.

🎛️ Input guide

1. Set What do you want back? to Monitor changes.
2. Paste one or more Vinted URLs.
3. Give the run a state namespace — one name per watch list, so separate searches never mix.
4. Test manually, then schedule sequential runs if useful.

The first run has nothing to compare against. By default it records the baseline quietly and returns no changes; set First monitor run to Return everything as new if you would rather see the current set immediately.

💰 Pricing

Both workflows use the same price. A successful empty search or baseline-only monitor still incurs the search fee. Blocked, failed and unvisited targets are free.

Event	Price	Charged when
Verified search	$0.02	A URL returns validated observations or a confirmed empty result
Verified listing observation	$0.00085	Per unique observation delivered, including unchanged observations in monitoring
Calculated change or coverage	Free	Additional explanation and comparison rows

One search with 100 observations costs $0.105; with 250 observations it costs $0.2325. Changes do not add to this price. A one-row run costs $0.02085, so tiny searches have a higher effective cost per row.

Set Maximum you can be charged and the run refuses to start if your settings could ever exceed it.

✅ Coverage you can trust

Every run writes a coverage row: COMPLETE, CAPPED, PARTIAL, BLOCKED, FAILED or EMPTY_CONFIRMED. A capped or blocked run cannot establish that an unseen listing is gone. Capped scans update validated observations and retain older unseen entries. GONE means absent from an exhaustively checked search, not proof that an item was sold or deleted. Prices and other source fields can be null; missing prices never mean zero-cost items.

🔌 API and automation

Use your Apify API credentials to run the Actor and export its Dataset to CSV or JSON. Monitoring returns listing observations, changes and coverage in one Dataset; use recordType to distinguish them. Run the same watch list sequentially; overlapping runs are not supported. Collect mode does not overwrite the monitor baseline.

⚠️ Not yet supported

• The recorded live evidence covers the UK catalog. Other regional domains still require validation.
• Default caps: 100 listings per run, 250 per URL, 10 pages per URL, 240 seconds. Raise them in Advanced.
• Only public catalog data is read. There is no account access of any kind.
• Run the same watch list sequentially; overlapping runs are not supported. The baseline is bounded at 5,000 identities. Reaching that limit requires a narrower search or a new namespace before further paid delivery.

Account-only data, full item-page enrichment, verified sold status and checkout pricing are not supported. A search changes during pagination, so results are not an atomic snapshot of the entire marketplace.

❓ FAQ and support

Found a URL that does not work, or a field you need? Open an issue on the Actor page with the exact URL and the run ID.