Scrape Wallapop Listings, Shipping Details, and Seller Feedback
Wallapop is a Spanish secondhand marketplace where listings carry price, condition, category, location, seller handle, shipping options, and an image gallery.
Collecting that data at scale usually means running headless browsers, rotating proxies, and handling bot detection. A hosted scraping API moves that infrastructure off your plate so your team can focus on the data product. This page explains the common Wallapop workflows, the request options that matter, the fields you can expect back, and how credit costs stack up.
Common Wallapop data workflows
Three data families tend to drive Wallapop collection projects. The first is listing data: title, asking price, condition, category, location, and seller handle. The second is shipping data: delivery options, costs, and courier details attached to each listing. The third is seller feedback: reviews, star ratings, and feedback counts. Each family can be requested from public-facing pages and returned as parsed HTML or structured JSON.
A practical way to choose a starting point is to ask what decision the data will support. Pricing intelligence needs listing price and condition. Delivery-cost analysis needs shipping fields. Seller-quality or competitor research needs review and rating fields. If you need all three, plan a single request per listing URL and map the fields you care about rather than issuing separate requests for each data family.
Field and control map
The table below pairs the request controls with the output fields they help produce. It is a planning aid, not a guarantee that every page exposes every field.
| Request control | What it does | Output fields it supports |
|---|---|---|
render_js | Executes page JavaScript before extraction | Listing title, price, condition, category, location, seller handle, shipping options, image gallery |
extract_rules | Maps CSS selectors to field names | Any field you target with selectors |
ai_extract_rules | Natural-language extraction spec | Structured JSON of listings without selectors |
stealth_proxy | Routes through stealth proxies for CAPTCHA-heavy pages | The same fields, with a higher credit cost |
country_code | Geo-targets the request | Region-specific listing and shipping content |
screenshot | Captures a full-page image | Visual verification of rendered pages |
Use extract_rules when you know the page structure and want predictable field names. Use ai_extract_rules when the page structure changes often or you want to describe the fields in plain language. Both return parsed JSON.
Worked example: one listing request
Suppose you want to track a single Wallapop listing for a used bicycle. You pass the listing URL to the endpoint with render_js enabled and an extract_rules map that names the fields you want. The response can include the listing title, asking price, condition, category, location, seller handle, shipping options, and the image gallery. If the page structure is unstable, replace extract_rules with an ai_extract_rules spec such as a request for title, price, condition, and seller handle. The response still comes back as parsed JSON, so your downstream pipeline does not need to change.
This example uses the field set captured for Wallapop listings. It does not assert that every listing page exposes every field on every request; treat missing fields as a signal to inspect the rendered page or adjust your extraction rules.
Concurrency limits versus target rate limits
The API applies concurrency limits per plan, not per-target rate limits. That means the ceiling is on how many requests you can have in flight at once, not on how many requests you can send to Wallapop in a given minute. If Wallapop throttles aggressive patterns, space out requests or use multiple sessions. The concurrency figure for each plan is listed in the plan table.
How request options affect credit cost
Credit cost depends on the options you enable. A request that enables JavaScript rendering costs 5 API credits. Premium proxies cost 10 credits without JS rendering or 25 credits with it. Stealth proxies cost 75 credits. The plan table lists the monthly credit allowance and concurrency for each tier. Credits are valid for one month and do not roll over, and requests start at 1 credit each.
Setup path
Create an account to get an API key and free starting credits. Install an SDK for Python, Node.js, Go, PHP, Ruby, or Java, or call the endpoint with plain cURL. Pass a Wallapop URL and your API key; the service handles rendering and bot bypass and returns parsed HTML or structured JSON. Test in the dashboard request builder first, then move the generated snippet into your codebase. The same workflow works for listing collection, shipping analysis, and seller-feedback research.
| Plan | Price | API credits | Concurrent requests | Priority support | Account manager | Team management |
|---|---|---|---|---|---|---|
| Hobby | $19 /mo | 75,000 | 25 | Not included | Not included | Not included |
| Freelance | $49 /mo | 250,000 | 50 | Not included | Not included | Not included |
| Startup | $99 /mo | 1,000,000 | 100 | Not included | Not included | Not included |
| Business | $249 /mo | 3,000,000 | 200 | Included | Included | Included |
| Business + | $599 /mo | 8,000,000 | 400 | Included | Included | Included |
| Enterprise 14 | $999 /mo | 14,000,000 | 500 | Included | Included | Included |
| Enterprise 24 | $1,599 /mo | 24,000,000 | 600 | Included | Included | Included |
| Enterprise 41 | $2,399 /mo | 41,000,000 | 700 | Included | Included | Included |
| Enterprise 69 | $3,599 /mo | 69,000,000 | 800 | Included | Included | Included |
| Enterprise 120 | $5,799 /mo | 120,000,000 | 900 | Included | Included | Included |
Prices are exclusive of VAT. Credits are valid for one month and do not roll over. Requests start at 1 credit each. JavaScript rendering costs 5 credits; premium proxies cost 10 or 25 credits depending on JS rendering; stealth proxies cost 75 credits. All figures are captured from the source page and should be checked against current pricing before purchase.
Frequently asked questions
Do I need a Wallapop account to collect data?
No external Wallapop account is required. You sign up for an API key, send the public URL, and the service handles rendering and bot bypass. The free starting allowance is 1,000 credits with no card required.
Is scraping Wallapop legal?
Public-facing pages can usually be collected, but review Wallapop's terms of service before deploying and avoid post-login content. Legal rules vary by jurisdiction and by how the data is used.
What rate limits apply?
The API applies concurrency limits per plan, not per-target rate limits. If Wallapop throttles aggressive patterns, space out requests or use multiple sessions. The plan table lists concurrency per tier.
How do I get structured JSON from Wallapop?
Pass extract_rules with CSS selectors mapped to field names, or use ai_extract_rules with a natural-language specification. The response comes back as parsed JSON.
Which programming languages can I use?
Any language that can make HTTP requests. SDKs are published for Python, Node.js, Go, PHP, Ruby, and Java, and plain cURL works too.
How much does it cost to collect Wallapop data?
There are 1,000 free credits on signup with no card required. Paid plans start at $19/month. Credit cost per request depends on options: 5 credits for JavaScript rendering, 10 credits for premium proxies without JS rendering, 25 for premium proxies with JS rendering, and 75 for stealth proxies. Credits are valid for one month and do not roll over, and requests start at 1 credit each. The plan table lists monthly credit allowances and concurrency.