Depop Listing Scraper API for Resale Pricing
Depop pages are rendered with JavaScript and protected by bot detection, so a plain HTTP client often returns an incomplete page.
A managed scraping API moves the proxy rotation, browser rendering and anti-bot handling into a single request, leaving your application with one call to make. This page explains what the Depop scraper API returns, which request options matter for resale research, and how to choose a plan without over-buying credits.
What the Depop scraper API returns
The API is built around a Depop URL. You send the URL, the service renders the page in a real browser environment, and you receive either the rendered HTML or structured JSON. The structured path is the more useful one for pricing work. A listing record can be grouped into three buckets: pricing fields (current price and original price), identity fields (title, condition, brand, sizes, and the image gallery), and trust-and-engagement fields (seller name, seller rating, and like count). That grouping covers the three patterns resale teams usually care about: product listings for market and inventory analysis, seller ratings for reputation and competitor assessment, and engagement signals such as likes and offer activity for trend research.
If you only need the page as it appears, rendered HTML is enough. If you need fields you can load into a spreadsheet or database, use extraction rules or the AI extraction option described below. The difference matters: HTML gives you the page, JSON gives you a record.
Request controls that matter for Depop
Four advanced parameters do most of the work on Depop. render_js turns on JavaScript rendering so product pages finish loading. stealth_proxy adds the proxy layer used when a target responds with CAPTCHAs or aggressive blocking. country_code routes the request through a residential IP in a chosen country, which is useful when content differs by geography; the geotargeting option covers 200+ countries and territories, with 40+ available on classic proxies. ai_extract_rules accepts a natural-language specification and returns structured JSON, so you can describe the fields you want instead of writing selectors.
A practical field map:
- render_js — enable when the listing content is injected after page load.
- stealth_proxy — enable when requests are being challenged rather than simply failing.
- country_code — set when the same listing or search result varies by region.
- ai_extract_rules — use when you want named fields back as JSON without maintaining selectors.
- extract_rules — use when you already know your selectors and want deterministic mapping to field names; the extraction rules accept CSS or XPath, and the same feature also captures full-page screenshots.
A useful diagnostic: if a request returns a page but the fields are empty, the problem is usually rendering or selector scope, not blocking. If the request is refused or challenged, the problem is more likely proxy or bot detection. Treating those two failures as the same thing leads teams to spend credits on the wrong control.
Worked example: from one listing to a pricing record
Suppose you are tracking a secondhand jacket. You send the listing URL with JavaScript rendering enabled and an extraction specification that asks for title, price, original price, condition, brand, sizes, seller name and rating, like count, and image URLs. The response is a JSON object you can store as one row.
That row supports several comparisons at once. Price against original price shows the discount depth. Condition and brand let you group comparable items. Seller rating lets you separate established sellers from new ones. Like count is an engagement signal rather than a price signal, so keep it in a separate column instead of folding it into a price score. Image URLs are useful for deduplication and for spotting relisted items.
For a batch, repeat the same request shape across a list of URLs. Because the API handles rendering and proxies, the batch code stays small; the main design decision is how many concurrent requests your plan allows and how aggressively the target tolerates them.
Plans, credits and concurrency
The free starting allowance is {{OWNER_FREE_CREDIT_ALLOWANCE}}, and paid plans begin at {{OWNER_PLAN_PRICES}}. Credit consumption depends on the options you enable. Requests start at 1 credit each. JavaScript rendering adds 5 credits per successful request. Premium proxies cost 10 credits without JavaScript rendering and 25 credits with it. stealth_proxy costs {{OWNER_CREDIT_COSTS}}. API credits are valid for {{OWNER_CREDIT_VALIDITY}}. Concurrency is the number of requests that can be sent at the same time, and it is set per plan rather than per target.
The plan table below lists monthly prices and is subject to {{OWNER_VAT_STATEMENT}}. Plan names, credit allowances and concurrency levels can change, so confirm current pricing before committing.
A simple budgeting rule: estimate your monthly request count, multiply by the credit cost of the options you actually need, and compare that to the credit allowance of each plan. If most of your requests need stealth_proxy, the effective request count is far lower than the headline credit number suggests.
Choosing a plan without over-buying
Start with the free credits and a small sample of real Depop URLs. Measure two things: how often rendering alone is enough, and how often you need stealth_proxy. Those two numbers determine your real credit cost per useful record. Then check the concurrency level against your batch size. A plan with a large credit allowance but low concurrency can still bottleneck a time-sensitive price monitor.
If you are unsure, the free tier is the cheapest way to find out. Teams that need more credits or concurrency than the listed plans provide can use the sales contact route at {{OWNER_SALES_CONTACT_ROUTE}}.
Languages and setup
The API is language-agnostic: any HTTP client can send a request. Published SDKs cover Python, Node.js, Go, PHP, Ruby and Java, and plain cURL works as well. Setup is a short sequence: create an account to get an API key and the free credits, install the SDK for your stack if you want one, then send a Depop URL with the options your task needs. The request builder and documentation examples are the fastest way to confirm the exact parameter names for your client.
Compliance and limits
Compliance position: {{OWNER_COMPLIANCE_STATEMENT}}. The service describes proxy rotation and headless browser rendering as the mechanisms used to reduce blocking risk. Those are the publisher's stated positions; your own obligations under GDPR, CCPA or the target site's terms remain yours to assess.
On limits, the API applies concurrency limits per plan rather than a per-target rate limit. If Depop throttles aggressive request patterns, spacing out requests or using multiple sessions is the practical response. That is a different failure mode from a plan-level concurrency cap, and it should be handled differently in your retry logic.
Depop scraper API questions
| Plan | Price per month | API credits | Concurrent requests | JavaScript rendering | Rotating & premium proxies | Geotargeting | Screenshots & extraction rules | Priority email support | Dedicated account manager | Team management |
|---|---|---|---|---|---|---|---|---|---|---|
| Hobby | $19 | 75,000 | 25 | Included | Included | Included | Included | Not included | Not included | Not included |
| Freelance | $49 | 250,000 | 50 | Included | Included | Included | Included | Not included | Not included | Not included |
| Startup (Recommended) | $99 | 1,000,000 | 100 | Included | Included | Included | Included | Not included | Not included | Not included |
| Business | $249 | 3,000,000 | 200 | Included | Included | Included | Included | Included | Included | Included |
| Business + | $599 | 8,000,000 | 400 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 14 | $999 | 14,000,000 | 500 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 24 | $1,599 | 24,000,000 | 600 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 41 (Recommended) | $2,399 | 41,000,000 | 700 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 69 | $3,599 | 69,000,000 | 800 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 120 | $5,799 | 120,000,000 | 900 | Included | Included | Included | Included | Included | Included | Included |
Captured pricing reference; prices exclude VAT; credits are valid for one month and do not roll over. Team management lets you invite multiple users to your organization and assign them a custom quota of credits and concurrency. Check current pricing before purchase.
Frequently asked questions
Do I need a Depop account to use the scraper API?
No external Depop account is required. You create an account with the API provider to get a key and the free starting credits, then send the Depop URL and the service handles the rest.
Can I request Depop pages from a specific country?
Yes. Set country_code on the request to route through a residential IP in that country. This is useful when listing availability or content differs by geography.
Is there a rate limit for scraping Depop?
Limits are applied by concurrency per plan, not as a per-target rate limit. If Depop itself throttles aggressive request patterns, space requests out or use multiple sessions. That is a target-side response, not a plan-level cap.
How do I get structured JSON from a Depop listing?
Use extract_rules with CSS or XPath selectors mapped to field names, or use ai_extract_rules with a natural-language specification. The response is returned as parsed JSON.
Which programming languages can I use?
Any language that can send an HTTP request. Published SDKs cover Python, Node.js, Go, PHP, Ruby and Java, and plain cURL works too.
How much does it cost to scrape Depop?
The free starting allowance is {{OWNER_FREE_CREDIT_ALLOWANCE}}, and paid plans begin at {{OWNER_PLAN_PRICES}}. Requests start at 1 credit each. JavaScript rendering adds 5 credits per successful request. Premium proxies cost 10 credits without JavaScript rendering and 25 credits with it. stealth_proxy costs {{OWNER_CREDIT_COSTS}}. Credits are valid for {{OWNER_CREDIT_VALIDITY}}.