# Depop Sold Comps — Sold Items & Last Ask (`noahadler/depop-sold-comps`) Actor

Scrape depop sold items and depop sold comps: itemId, title, last ask, status sold or removed. For resellers who want depop shop sold in a spreadsheet — not a live listings dump. Last ask is not an invented hammer. RESIDENTIAL GB.

- **URL**: https://apify.com/noahadler/depop-sold-comps.md
- **Developed by:** [Noah Adler](https://apify.com/noahadler) (community)
- **Categories:** E-commerce, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $6.00 / 1,000 sold comps

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?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Depop Sold — Sold Items & Price Comps

**depop sold** comps from **depop.com**: items that sold or left a shop, with `itemId`, title, `lastPrice` (last ask) and `status`. Built for resellers who need **depop sold items** and **depop comps** in a spreadsheet, not another live listings dump.

> Depop does not publish a sold search. The public search API is **410 (deprecated)**. Search HTML is live ads only. This Actor reads **depop shop sold** (`sold=true` / `PURCHASED` on the shop products API) and watches a keyword universe so scheduled runs emit **sold / removed** when a listing disappears. First search-only run seeds the universe. Last ask is **not** an invented hammer price (`priceKind=last_ask`).

### Table of contents

- [What you get](#what-you-get)
- [How it works](#how-it-works)
- [Input](#input)
- [Output](#output)
- [Example input](#example-input)
- [Use cases](#use-cases)
- [Proxy](#proxy)
- [API quick start](#api-quick-start)
- [FAQ](#faq)
- [Limitations](#limitations)
- [Keywords](#keywords)

### What you get

**Sold / removed comp**

- `itemId`, `slug`, `url` (depop.com/products/…)
- `title`, `brand`, `size`
- `status`: `sold` | `removed` | (optional) `active`
- `lastPrice`, `soldPrice`, `priceKind` (`last_ask`), `currency`
- `firstSeenAt`, `lastSeenAt`, `sellerId`, `sellerUsername`, `scrapedAt`

This is **depop sold**, **depop sold items**, **depop sold comps**, and **depop shop sold**. It is not a third Depop live-search scraper.

### How it works

| Step | Action |
|------|--------|
| 1 | Optional: open a **shop URL**. Shop JSON includes PURCHASED items with last ask. Those rows are **sold comps on the first run**. |
| 2 | Optional: open Depop search HTML for your keyword (e.g. Nike). Live cards seed the watched universe in Actor storage. They are **not** pushed as sold. |
| 3 | Check `listingUrls` / `itemIds` / `watchItems` and IDs that vanished since the last snapshot. |
| 4 | Product page: InStock = still active. SoldOut / PURCHASED = `sold`. HTTP 404 = `removed`. |
| 5 | Push only sold / removed rows unless you turn `includeActive` on. |

There is no working `?sold=true` search filter (query params are ignored). Search API v2 is gone (410).

### Input

| Field | Required | Default | Notes |
|-------|----------|---------|-------|
| `keyword` | One of keyword / URL / shop / IDs | Nike | Brand as buyers type it |
| `searchUrl` | One of keyword / URL / shop / IDs | — | Full search URL |
| `shopUrl` | One of keyword / URL / shop / IDs | — | `https://www.depop.com/{username}/` for shop sold |
| `listingUrls` | One of keyword / URL / shop / IDs | — | Product URLs a reseller would paste |
| `itemIds` | One of keyword / URL / shop / IDs | — | Numeric IDs |
| `watchItems` | No | — | Last-known cards |
| `maxItems` | No | 20 | 1–80 |
| `lookbackHours` | No | 168 | Keep IDs between scheduled runs |
| `includeActive` | No | false | Off = sold/removed only |
| `proxyConfiguration` | No | RESIDENTIAL + GB | Keep GB (or your market) aligned |

### Output

One row per sold or removed item. A hard block pushes one row with `error: true` and a message that names RESIDENTIAL + GB. A first keyword-only run with no disappearances yet pushes one honest empty row (`error: false`) and stores the universe.

```json
{
  "itemId": "925467575",
  "url": "https://www.depop.com/products/kewin7500-women-nay-blue-gap-long-c467/",
  "title": "Women Nay blue Gap long sleeve 100% cotton shirt",
  "status": "sold",
  "lastPrice": 12.0,
  "soldPrice": 12.0,
  "priceKind": "last_ask",
  "currency": "USD",
  "scrapedAt": "2026-09-25T00:00:00Z"
}
```

`priceKind=last_ask` means the number is the last public asking price, not a Depop hammer.

### Example input

```json
{
  "keyword": "Nike",
  "shopUrl": "https://www.depop.com/kewin_500/",
  "maxItems": 15,
  "includeActive": false,
  "listingUrls": ["https://www.depop.com/products/kewin7500-women-nay-blue-gap-long-c467/"],
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"],
    "apifyProxyCountry": "GB"
  }
}
```

### Use cases

- Resellers dumping **depop sold** listings into a sourcing spreadsheet (brand, style, last ask)
- **depop shop sold** counts / comps on a watched seller
- Closed-sale checks on product URLs you already track (schedule 6–12h)

### Proxy

Depop can challenge datacenter IPs. Default is **Apify RESIDENTIAL**, country **GB**. Use a market-aligned country if you need local currency.

### API quick start

```bash
apify call noahadler/depop-sold-comps --input '{
  "keyword": "Nike",
  "shopUrl": "https://www.depop.com/kewin_500/",
  "maxItems": 15,
  "includeActive": false
}'
```

### FAQ

**Why didn’t the first keyword-only run return sold rows?**\
Public search has no sold tab (API 410). The first run saves live IDs; the next scheduled run emits comps when those IDs leave. Pass `shopUrl` / `listingUrls` to get **depop shop sold** now.

**Is soldPrice the hammer?**\
No. Public HTML and shop JSON expose last ask. `priceKind=last_ask`. This Actor does not invent hammer prices.

**Can I dump live listings?**\
Not with the default input. Use a listings Actor for that. `includeActive` is off on purpose.

### Limitations

- Search API deprecated (410)
- Search `sold` query params ignored
- Disappeared listing = `removed` (sold or withdrawn) unless the shop/page marks PURCHASED / SoldOut
- Do not invent hammer prices

### Keywords

`depop sold` · `depop sold items` · `depop comps` · `depop shop sold` · `depop scraper` · `depop sold comps`

# Actor input Schema

## `keyword` (type: `string`):

What a reseller types on Depop (e.g. Nike). Builds the watched search universe. Required unless you pass searchUrl, shopUrl, listingUrls, itemIds or watchItems.

## `searchUrl` (type: `string`):

Optional depop.com search URL. Overrides the keyword URL when set. Live results are not dumped as sold.

## `shopUrl` (type: `string`):

Depop shop URL (https://www.depop.com/{username}/). Shop products API returns PURCHASED / sold=true items — this is depop shop sold, not live search.

## `listingUrls` (type: `array`):

Depop product URLs a reseller would paste (/products/{slug}/). Checked now for sold, last ask, or removed.

## `itemIds` (type: `array`):

Numeric Depop product IDs (or URLs). Same as listingUrls when the ID is known.

## `watchItems` (type: `array`):

Last-known cards from a previous run: itemId, slug, title, lastPrice, url. Used when you paste last run output instead of Actor storage.

## `maxItems` (type: `integer`):

Maximum sold/removed rows to save, and size of the watched search universe (1–80).

## `lookbackHours` (type: `integer`):

How long to keep IDs in the watched universe between scheduled runs (1–720). Typical: 168 (7 days).

## `includeActive` (type: `boolean`):

Off by default. This Actor is depop sold comps, not a live listings scraper. Turn on only if you also want current ONSALE matches.

## `proxyConfiguration` (type: `object`):

Default: Apify RESIDENTIAL, country GB (Depop). Keep RESIDENTIAL on if you see a challenge.

## Actor input object example

```json
{
  "keyword": "Nike",
  "shopUrl": "https://www.depop.com/kewin_500/",
  "maxItems": 20,
  "lookbackHours": 168,
  "includeActive": false,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "GB"
  }
}
```

# Actor output Schema

## `comps` (type: `string`):

No description

# 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 = {
    "keyword": "Nike",
    "shopUrl": "https://www.depop.com/kewin_500/"
};

// Run the Actor and wait for it to finish
const run = await client.actor("noahadler/depop-sold-comps").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 = {
    "keyword": "Nike",
    "shopUrl": "https://www.depop.com/kewin_500/",
}

# Run the Actor and wait for it to finish
run = client.actor("noahadler/depop-sold-comps").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 '{
  "keyword": "Nike",
  "shopUrl": "https://www.depop.com/kewin_500/"
}' |
apify call noahadler/depop-sold-comps --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,noahadler/depop-sold-comps"
        }
    }
}
```

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/ovcaDCxMoKGb4AxY9/builds/MuF89G4Lr5eWXIYTC/openapi.json