# Vinted Scraper & Price Change Monitor (`luminar/vinted-listing-price-monitor`) Actor

Collect public Vinted listing observations and compare saved searches for new listings, price and condition changes, with explicit coverage and per-observation pricing.

- **URL**: https://apify.com/luminar/vinted-listing-price-monitor.md
- **Developed by:** [Luka](https://apify.com/luminar) (community)
- **Categories:** E-commerce
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.85 / 1,000 verified listing observations

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

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.

```json
{"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

![Vinted listing output](https://api.apify.com/v2/key-value-stores/DJgPR6wwS2tIaLDQW/records/vinted_listing_price_monitor--dc4c86b6abfe5198-output.png)

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.

# Actor input Schema

## `workflow` (type: `string`):

Both workflows deliver and charge verified listing observations. Monitor also calculates changes against your saved baseline without additional charge, including new listings and price or condition changes.

## `catalogUrls` (type: `array`):

Paste public Vinted catalog search or filter URLs. Regional availability can differ; an unavailable region returns coverage instead of invented listings.

## `maxListings` (type: `integer`):

Hard ceiling across every URL. The run stops cleanly at this number and reports the coverage as capped.

## `maxListingsPerTarget` (type: `integer`):

Per-URL ceiling. Useful when one search is far larger than the others and you do not want it to consume the whole run.

## `maxPagesPerTarget` (type: `integer`):

How deep to page through each search. Each page is one request of up to the listings-per-request size.

## `stateNamespace` (type: `string`):

Runs that share this name compare against each other. Use one name per watch list so separate searches never mix.

## `firstRunBehavior` (type: `string`):

Both options return paid listing observations. Seed only records the baseline with no change rows; emit current as new also includes free NEW change rows.

## `maxRuntimeSecs` (type: `integer`):

Time budget for collecting listings. The Actor also reserves time for delivery before the platform timeout.

## `maxBuyerChargeUsd` (type: `integer`):

The run refuses to start if the maximum possible charge for your settings would exceed this.

## Actor input object example

```json
{
  "workflow": "collect",
  "catalogUrls": [
    "https://www.vinted.co.uk/catalog?search_text=nike"
  ],
  "maxListings": 100,
  "maxListingsPerTarget": 250,
  "maxPagesPerTarget": 10,
  "stateNamespace": "default",
  "firstRunBehavior": "seed_only",
  "maxRuntimeSecs": 240,
  "maxBuyerChargeUsd": 10
}
```

# Actor output Schema

## `dataset` (type: `string`):

Observations, changes and coverage. Distinguish records by recordType.

## `summary` (type: `string`):

Coverage and accepted observation counts.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "catalogUrls": [
        "https://www.vinted.co.uk/catalog?search_text=nike"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("luminar/vinted-listing-price-monitor").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "catalogUrls": ["https://www.vinted.co.uk/catalog?search_text=nike"] }

# Run the Actor and wait for it to finish
run = client.actor("luminar/vinted-listing-price-monitor").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "catalogUrls": [
    "https://www.vinted.co.uk/catalog?search_text=nike"
  ]
}' |
apify call luminar/vinted-listing-price-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,luminar/vinted-listing-price-monitor"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/QFXAKxCU3MotriOO0/builds/VIv36DmfmtDftpTEz/openapi.json