Depop Marketplace Monitor
Pricing
Pay per event
Depop Marketplace Monitor
Returns Depop listings for keyword searches or listing URLs (price, sold status), with a monitor mode alerting on new listings for a search, price drops or sales for an item. Inputs: search queries, listing URLs, monitorMode. Agent-ready: pay per event (x402 and MCP), no charge for blocked checks.
Pricing
Pay per event
Rating
0.0
(0)
Developer
Adam Pearce
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
6 days ago
Last modified
Categories
Share
What does Depop Marketplace Monitor do?
Depop Marketplace Monitor watches Depop, the secondhand-fashion resale marketplace, two ways: give it a search (e.g. "vintage carhartt jacket") and it alerts you the moment a new matching listing appears, or give it specific listing URLs and it alerts you on a price drop or the item selling out. Every existing Depop scraper on the Apify Store hands you a flat, one-time list of results; this is the only one that keeps watching so you don't have to refresh the search yourself.
Runs on Apify's infrastructure, so it's schedulable (hourly, daily, whatever fits), API-accessible, and works as a tool inside AI agents via Apify's MCP server. No account, no login, no browser extension to install.
Why use Depop Marketplace Monitor?
Depop moves fast: the best-priced vintage pieces and rare drops get bought within minutes of listing. Checking a saved search by hand, over and over, is exactly the kind of thing worth automating.
- Resale buyers and thrifters: get notified the second something matching your search goes up, before anyone else sees it.
- Resellers and sourcing teams: watch a whole category or brand for new stock across many sellers, not just one shop.
- Sellers: watch your competitors' listings for price changes or track when their stock sells through.
- Anyone with a wishlist: watch a specific listing and get told the moment it drops in price or sells to someone else.
How to use Depop Marketplace Monitor
- Click Try for free and open the Input tab.
- Add one or more search queries (e.g. "vintage carhartt jacket"), specific listing URLs, or both.
- Leave Monitor mode off for a one-time snapshot, or turn it on and give your watchlist a stable Watchlist ID to only get charged the full rate when something actually changed.
- Run it. Results land in the dataset, downloadable as JSON, CSV, or Excel, or pulled via the API.
- Schedule it (Apify's built-in Scheduler) to run every hour or every day and get a running record of what's new or what changed.
Input
| Field | Description |
|---|---|
searchQueries | Depop search terms to watch, e.g. vintage carhartt jacket. In Monitor mode, alerts on new listings matching the search. |
productUrls | Direct Depop listing URLs to watch, e.g. https://www.depop.com/products/example-item/. In Monitor mode, alerts on price drops or the item selling/going unavailable. |
maxItemsPerSearch | How many listings to check per search (default 24, one results page). |
monitorMode | Off: a one-time snapshot. On: remembers your last check per search/item and only flags real changes. |
watchlistId | A name for this watchlist, so it doesn't get mixed up with any other list you run. |
proxyCountryCode | Which country the request should look like it's coming from. US is the default. |
Output
{"itemUrl": "https://www.depop.com/products/s0c18-brown-leather-jacket-with-a-5555/","itemSlug": "s0c18-brown-leather-jacket-with-a-5555","watchType": "search","sourceQuery": "vintage carhartt jacket","title": "Men's Burgundy and Brown Jacket","brand": "Carhartt","size": "L","price": 9.0,"currency": "USD","sellerUsername": null,"likesCount": null,"description": null,"imageUrl": "https://media-photos.depop.com/r1/.../P0.jpg","soldOrUnavailable": false,"monitorMode": true,"isFirstCheck": false,"changeDetected": true,"changeSummary": "New listing matching this search since the last check.","changes": ["New listing matching this search."],"fetchIssue": null,"checkedAt": "2026-08-13T20:53:29.314Z"}
You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.
Data table
| Field | Meaning |
|---|---|
watchType | search (from a watched search query) or item (from a watched listing URL). |
price / currency | The listing's current price, when recognized. |
sellerUsername / likesCount / description | Only populated for item-type results (a search results page doesn't show these per-listing). |
soldOrUnavailable | Best-effort. true/false when confidently detected, null when the page loaded but this couldn't be confirmed, never guessed. |
changeDetected | Monitor mode only: a new listing (search watch) or a real price/availability change (item watch) since your last check. |
changeSummary | Plain-English description of what changed, if anything. |
fetchIssue | Set (and nothing charged) if a check genuinely couldn't get a real answer this run. |
Pricing
Pay-per-event, you only pay for real answers:
- $0.015 per one-time listing check (from a search or a direct URL).
- $0.06 per Monitor mode check where something actually changed, a new listing or a real price/availability change.
- $0.004 per Monitor mode check that confirms nothing changed (cheap, so daily monitoring stays affordable).
Watching 5 searches and 10 specific listings daily in Monitor mode for a month runs somewhere around $3-8/month, depending on how much actually changes. A one-time check of a 24-listing search page runs about $0.36.
Tips
- Give a watchlist a stable
watchlistIdand keep reusing it, that's what makes Monitor mode compare against your actual last check instead of starting fresh every time. - Broad searches ("jacket") return more noise than narrow ones ("carhartt detroit jacket large"), a narrower search means fewer, more relevant new-listing alerts.
- Hourly scheduling suits genuinely fast-moving categories (rare drops, hyped brands); daily is enough for most searches.
FAQ
Is this legal? Reading a public listing or search page is not illegal. This tool doesn't log in, doesn't bypass any paywall, and only reads what's already publicly visible on the page. Automated access sits outside Depop's own Selling API terms, the same real, known tradeoff as most large marketplaces (the Apify Store already hosts several Depop scrapers), worth knowing rather than hidden, use accordingly.
Why did a check come back with no data and no charge? Depop sits behind a Cloudflare bot check. This actor solves it with a real browser automatically; if a check still comes back blocked after every retry, it reports that honestly instead of guessing, and you're not charged for it.
Why is soldOrUnavailable sometimes null? Depop's markup isn't documented and can change without notice. When the page loads but a sold/available state can't be confidently read off it, this actor reports null rather than guessing true or false, so you never get told a live listing is dead or vice versa on a hunch.
Found a bug or have a request? Use the Issues tab, it's read personally, not a support bot.