Wallapop Vendidos — Sold & Reserved Price Comps

wallapop vendidos and wallapop sold comps from es.wallapop.com: listings that sold or were reserved, with itemId, title, last ask and status (sold | reserved | removed). Built for resellers who need wallapop comps, not another live search dump.

Wallapop has no public sold archive. This Actor watches a keyword (or search URL), emits reserved ads when the search flag is on, pulls matching vendidos from seller sell-reviews, and on later scheduled runs adds IDs that left the universe (removed). Price is always last ask — never an invented hammer.

Table of contents

• What you get
• How it works
• Input
• Output
• Example input
• Use cases
• Proxy
• API quick start
• FAQ
• Limitations
• Racimo
• Keywords

What you get

Sold / reserved / removed comp

• itemId, url (es.wallapop.com)
• title, city, sellerId
• status: sold | reserved | removed | (optional) active
• lastPrice, soldPrice, priceKind (last_ask), currency (EUR)
• reserved boolean when the listing is reserved
• lastSeenAt, scrapedAt

This is wallapop vendidos, wallapop sold and reserved ads. It is not a third Wallapop live-listings scraper.

How it works

Step	Action
1	Call Wallapop search JSON for your keyword / city (or searchUrl).
2	If reserved.flag is true, emit a reserved row with last ask.
3	Read seller sell reviews and keep items whose title matches the keyword → sold.
4	Save the live universe in Actor storage for the next run.
5	Probe itemIds / watchItems and IDs that vanished. HTTP 404 = removed. Detail sold / reserved flags win.
6	Push only sold / reserved / removed unless you turn includeActive on.

HTTP only (curl_cffi). No Playwright. Last ask from search or item detail — not a made-up close price.

Input

Field	Required	Default	Notes
keyword	One of keyword / URL / IDs	iphone 12	Query as on Wallapop
searchUrl	One of keyword / URL / IDs	—	es.wallapop.com or api.wallapop.com search
city	No	madrid	Spain city for coordinates
itemIds	One of keyword / URL / IDs	—	IDs or item URLs to check now
watchItems	No	—	Last-known cards (itemId, title, lastPrice, …)
maxItems	No	20	1–80
lookbackHours	No	168	Keep IDs between scheduled runs
includeActive	No	false	Off = vendidos / reserved / removed only
proxyConfiguration	No	RESIDENTIAL + ES	Keep country ES

Output

One row per sold, reserved or removed listing. A hard block pushes one row with error: true and a message that names RESIDENTIAL + ES. A first run with no comps yet pushes one honest empty row (error: false) and stores the universe.

{
  "itemId": "mzn3k8vq72jn",
  "url": "https://es.wallapop.com/item/iphone-12-pro-max-256gb",
  "title": "iPhone 12 Pro Max 256GB",
  "status": "sold",
  "lastPrice": 280.0,
  "soldPrice": 280.0,
  "priceKind": "last_ask",
  "currency": "EUR",
  "reserved": false,
  "sellerId": "436ee72e3k6d",
  "keyword": "iphone 12",
  "scrapedAt": "2026-09-25T11:00:00Z"
}

Example input

{
  "keyword": "iphone 12",
  "city": "madrid",
  "maxItems": 20,
  "lookbackHours": 168,
  "includeActive": false,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"],
    "apifyProxyCountry": "ES"
  }
}

Schedule that input every 6–12 hours. The first run often already returns wallapop vendidos (seller reviews) and reserved ads; later runs add listings that dropped out of search.

To check IDs you already have:

{
  "keyword": "iphone 12",
  "city": "madrid",
  "itemIds": ["mzn3k8vq72jn", "https://es.wallapop.com/item/zzzznotanitem00"],
  "maxItems": 20
}

Use cases

• Price an iPhone / PS5 / bike lot from wallapop vendidos and reserved last asks, not live ads.
• Feed the Forocoches-style “análisis reservados o vendidos” (min / max / mean) from real comps.
• Watch a keyword and alert when a listing is reserved, sold, or removed.
• Keep a private sold history — Wallapop search Actors only dump live inventory.

Proxy

Wallapop JSON can 403 without a Spain residential exit. Default proxy is Apify RESIDENTIAL with country ES.

API quick start

from apify_client import ApifyClient

client = ApifyClient("YOUR_TOKEN")
run = client.actor("noahadler/wallapop-sold-comps").call(run_input={
    "keyword": "iphone 12",
    "city": "madrid",
    "maxItems": 20,
})
items = client.dataset(run["defaultDatasetId"]).list_items().items

curl "https://api.apify.com/v2/acts/noahadler~wallapop-sold-comps/run-sync-get-dataset-items?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"keyword":"iphone 12","city":"madrid","maxItems":20}'

FAQ

Why might the first run be empty? Search does not list a sold archive. If no seller nearby has a matching sell-review and nothing is reserved, the run seeds the universe. The next scheduled run emits removed comps. Pass itemIds to check known listings now.

Is this another Wallapop search scraper? No. Live listing Actors already exist. This Actor is wallapop sold / vendidos / reserved comps.

Do you invent sold prices? No. priceKind is last_ask (search or item detail). There is no public hammer.

Will I get every sale on Wallapop? No. You get reserved flags, matching seller sell-reviews, and disappearances inside the universe you watch.

Limitations

• Spain (es.wallapop.com / api.wallapop.com) only in v0.1. IT/PT are out of scope.
• Cap 80 items per run. Seller reviews are sampled from the search universe.
• Sold price equals last asking price when Wallapop hides the close price.
• Ranking changes are not sold: an item must be reserved, have a sell-review, show a sold flag, or 404.
• includeActive off by default so Try it does not dump live ads.

Racimo

Hijo de tu Wallapop listings. Ampliar IT/PT solo si este hero tiene runs a 7–14 días.

Keywords

wallapop vendidos · wallapop sold · wallapop comps · wallapop reservado · wallapop scraper