# Grailed Scraper: Sold Prices & New Listings (`accountable_eel/grailed-listing-lookup`) Actor

Grailed scraper by keyword: new listings, price-drop alerts, sold comps, sell-through rate and days to sell for a list of designers. Price, size, condition, and Grailed's own price-drop history. No login required. Pay per listing; misses and quiet runs are free.

- **URL**: https://apify.com/accountable\_eel/grailed-listing-lookup.md
- **Developed by:** [Adrian Voss](https://apify.com/accountable_eel) (community)
- **Categories:** E-commerce, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 listing returneds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## Grailed Scraper: Sold Prices & New Listings

Watch a search, get only what's new. This actor runs your search against **Grailed's own
first-party Algolia search** — the largest dedicated resale marketplace for menswear and
streetwear — and returns one clean row per listing: price, designer, size, condition, and
Grailed's own price-drop history. Search sold listings too, for sold-price comps without eBay's
login wall. Turn on monitoring and it becomes a watchlist: new listings and price drops since your
last run, charged per new row, free on quiet days. Schedule it hourly and send the results to
Discord, Slack, Google Sheets, or n8n.

### Who it's for

A reseller checking what a piece is actually worth before buying or flipping it wants real sold
prices, not asking prices — Grailed's sold index gives you that without eBay's login-walled
"completed listings" search. A buyer watching for a specific designer, size, or price band wants a
live feed of new listings the moment they post, without refreshing the search page by hand. A
market-research or pricing team tracking resale value for a product category, or a Sheets/n8n
workflow that reacts the moment something new is posted or a price drops, gets the same shape here:
paste a list of search terms, get back a flat row per listing, and pay only for listings actually
returned — a search that finds nothing costs nothing.

### Why this one

- **Sold-price comps without eBay's login wall.** Grailed exposes its own sold-listings index
  (`sold_at desc`) with real sale prices and dates — set "Listing type" to "Sold listings" for a
  comps feed. eBay's own completed/sold search has needed a login since 2026-07-22, which is why
  this is rare among scrapers right now.
- **Grailed's own price-drop history, no monitoring required.** Every listing carries its own
  `nativePriceDropCount` and `originalPrice` straight from Grailed's data — the seller's own
  markdown history, available even with monitoring off.
- **Monitoring first, not a one-off dump.** Turn on "Only return results that are new, or dropped
  in price" and this actor becomes a watchlist: it remembers every listing ID it has already shown
  you, and only bills you for what's actually new or has dropped in price (against what *this
  watchlist* has seen) since the last run. A quiet run still finishes and costs only the base run
  fee.
- **Reads Grailed's own structured search data.** Every field comes from Grailed's first-party
  Algolia index — the same data that powers grailed.com's own search page — not text scraped from
  rendered HTML, so price, size, condition, and designer are exact, typed values.
- **Never charged for a miss, or a quiet monitoring run.** A search that finds nothing, or a
  scheduled watchlist run where nothing changed, still gets a row explaining what happened — and
  costs nothing.

### What you get

One row per listing by default (turn off "Expand rows" in Advanced to get one row per search
instead, with the listings nested under `listings`).

| Field | Type | Description |
|---|---|---|
| `query` | text | The search you submitted, echoed back |
| `found` | boolean | `true` if Grailed returned real search results for this search |
| `status` | text | `OK` on a match; `NOT_FOUND`, `BLOCKED`, or `BAD_FORMAT` on a miss |
| `message` | text | Plain-English reason for a miss — only present when `found` is `false` |
| `searchQuery` | text | The keywords actually searched |
| `listingType` | text | `active`, `sold`, or `both` — what this search was run against |
| `listingCount` | number | Listings returned and billed for this search |
| `totalAvailable` | number | Total listings Grailed reports matching this search, including ones not returned |
| `truncated` | boolean | `true` if more results existed than were returned |
| `newCount` | number | New listings this run (monitoring only) |
| `priceDropCount` | number | Price drops this run, as tracked by this watchlist (monitoring only) |
| `monitorStatus` | text | `NO_NEW_ROWS` on a quiet monitoring run, `WATCHLIST_SEEDED` on a silent first run, otherwise empty |
| `activeCount` | number | **Sold comps only.** Active listings fetched this run |
| `soldCount` | number | **Sold comps only.** Sold comps fetched this run |
| `sellThroughRate` | number | **Sold comps only.** `soldCount / (soldCount + activeCount)` over the fetched window, 0-1 |
| `compsWindowDays` | number | **Sold comps only.** Span between the oldest and newest sold comp fetched, in days |
| `activeMedianPrice` | number | **Sold comps only.** Median asking price (USD) across active listings fetched |
| `soldMedianPrice` | number | **Sold comps only.** Median sold price (USD) across sold comps fetched |
| `askVsSoldGapPct` | number | **Sold comps only.** `(activeMedianPrice - soldMedianPrice) / soldMedianPrice`, as a % |
| `medianDaysToSell` | number | **Sold comps only.** Median `daysToSell` across sold comps fetched |
| `listingId` | text | Grailed's own numeric listing ID |
| `title` | text | Listing title |
| `price` | number | Asking price in USD |
| `currency` | text | Always `USD` |
| `designers` | text | Designer(s), comma-joined |
| `size` | text | Size, as Grailed labels it for that category |
| `category` | text | Grailed's own category slug |
| `condition` | text | `is_new`, `is_gently_used`, `is_used`, `is_worn`, or `is_not_specified` |
| `color` | text | Primary listed color |
| `location` | text | Seller's coarse location (e.g. a country or region), as Grailed exposes it |
| `postedAt` | date | When the listing was created |
| `bumpedAt` | date | When the seller last bumped the listing |
| `isSold` | boolean | `true` for a listing from the sold index |
| `soldAt` | date | **Sold listings only.** When it sold |
| `soldPrice` | number | **Sold listings only.** What it actually sold for |
| `daysToSell` | number | **Sold listings only.** Days from `postedAt` to `soldAt` |
| `nativePriceDropCount` | number | Grailed's own count of price drops on this listing's history — independent of monitoring |
| `originalPrice` | number | The highest price in Grailed's own price-drop history for this listing, before any of its own markdowns |
| `popularity` | number | Grailed's own "heat" score |
| `imageUrl` | text (link) | Cover photo |
| `sellerHash` | text | Anonymous per-seller hash — always present, lets you group listings by seller without a name |
| `sellerId` | text | **Raw seller info only.** Grailed's own user ID |
| `sellerName` | text | **Raw seller info only.** Seller's username |
| `sellerProfileUrl` | text (link) | **Raw seller info only.** Seller's profile link |
| `changeType` | text | `new`, `price-drop`, or `seen`, as tracked by this watchlist (monitoring only) |
| `isNew` | boolean | `true` on this listing's first appearance to this watchlist (monitoring only) |
| `previousPrice` | number | Price this watchlist last recorded, when it dropped (monitoring only) |
| `priceDropPct` | number | Percentage drop from this watchlist's previous recorded price (monitoring only) |
| `firstSeenAt` | date | When this watchlist first saw this listing (monitoring only) |
| `url` | text (link) | Permanent listing link |
| `scrapedAt` | date | When this row was fetched |

Deselect any field in the Input tab's column picker to drop it from every row — `query`, `found`,
`status`, `message`, and `scrapedAt` always stay.

`priceDropCount` (the search-level monitoring summary) and `nativePriceDropCount`/`originalPrice`
(the per-listing field, from Grailed's own permanent history) are deliberately different things —
see "Monitoring / only new results" below.

### Sold comps and sell-through

Turn on **"Include sold comps and sell-through stats"** and every search also fetches Grailed's own
sold-listings index for the same keywords and filters — up to "Max sold comps to fetch" (50 by
default, 200 max), newest sale first — regardless of what "Listing type" is set to. Each sold comp
comes back as an ordinary row: `isSold: true`, `soldAt`, `soldPrice`, and `daysToSell` (the days from
`postedAt` to `soldAt`, when both are present). **Sold comps are listings too** — they're billed as
ordinary `listing` rows, at the same per-listing price as an active listing, not a separate event.

Every row of a search with sold comps on also carries sell-through summary columns, computed from
everything the run actually fetched (not just what's returned after any monitoring filter):
`activeCount` and `soldCount` (how many of each this run fetched), `sellThroughRate` (`soldCount /
(soldCount + activeCount)`, 0-1, over the window described by `compsWindowDays` — the span between
the oldest and newest sold comp fetched), `activeMedianPrice` and `soldMedianPrice` (USD), the gap
between them as `askVsSoldGapPct`, and `medianDaysToSell`. All eight are `null` when sold comps are
off, so the column set never changes with a checkbox.

**Honesty note.** Grailed's sold index reflects whatever Grailed itself marks sold — that includes
offers accepted off-platform (e.g. a seller and buyer agreeing outside Grailed's own checkout) as
well as genuine in-app sales, and Grailed doesn't distinguish the two. `sellThroughRate` and the
median prices describe *this run's fetched window*, not Grailed's full sold history for that search
— narrow your search (a specific designer/size/category) if you want the window to represent the
whole market for that niche rather than a slice of it.

Example: `{"searches": ["carhartt jacket"], "includeSoldComps": true, "maxSoldComps": 100}` returns
active Carhartt jacket listings plus up to 100 recent sold comps in the same run, with sell-through
and median-price-gap columns on every row.

**Related actors.** `vinted-listing-lookup`'s own monitoring infers a sold signal indirectly, by
noticing a listing has *gone* (delisted, most often sold); Grailed exposes its sold history directly
via a real sold index, so this actor's sold comps are Grailed's own confirmed sold rows, not an
inference. `poshmark-listing-lookup` has the same sold-comps shape for Poshmark, with its own
honesty note (Poshmark shows the last asking price, not a negotiated final price).

### Pricing

- **Listing returned**: $2 per 1,000 listings

Plus a $0.00005 start fee per run. Each event above is billed independently, only when it actually returns data — misses (`found:false`) are never charged.

No upgrade event — every field this actor declares comes from the same Algolia hit, with no
per-listing page hop.

### Sold comps

Set **"Listing type"** to **"Sold listings"** (or **"Both"**) to search Grailed's own sold-listings
index instead of (or alongside) active listings. Each sold row carries `soldPrice` and `soldAt`
straight from Grailed's own record of the sale — a real comps feed, not an asking-price guess.
This is genuinely rare among resale scrapers right now: eBay's own completed/sold search has sat
behind a login wall since 2026-07-22, and the last signed-out fallback closed 2026-08-19, so a
logged-out actor can't reach that data at any proxy tier. Grailed doesn't have that wall.

For `listingType: "both"`, your "Most listings to return per search" budget is split evenly across
the active and sold indexes, and each listing's `isSold` flag tells the two apart in one combined
result.

Want sold comps *alongside* an active search, plus sell-through and median-price-gap stats, without
switching "Listing type" away from "Active listings"? See "Sold comps and sell-through" above.

### Monitoring / only new results

Turn on **"Only return results that are new, or dropped in price"** and a search line becomes a
watchlist instead of a one-off dump:

- A listing counts as **new** the first time its Grailed listing ID is returned by this watchlist.
  For `listingType: "sold"`, that reads naturally as "newly sold since the last run" — a sold-comps
  feed rather than a listing alert.
- A listing counts as a **price drop** when its price falls by at least "Minimum price drop" (5% by
  default) since *this watchlist* last saw it — measured against the most recently seen price, so a
  listing that drops twice is compared against its latest price each time, not its original one.
  This is separate from Grailed's own `nativePriceDropCount`/`originalPrice` fields, which reflect
  Grailed's permanent record and work whether or not monitoring is on.
- Already-seen, unchanged listings are dropped before you're billed. A quiet run — nothing new,
  nothing cheaper — still finishes and returns one free row with `monitorStatus: NO_NEW_ROWS`, so a
  scheduled task shows it actually ran.
- The **first run has nothing to compare against.** By default it returns everything it finds as
  "new" (so you see your whole current search result once). Turn on **"Seed silently"** to instead
  have the first run bank everything quietly with zero rows and zero charge, and start alerting from
  the second run on — this is what stops a fresh watchlist from firing a hundred "new listing"
  messages into your Discord channel on day one.

**Schedule recipe.** Save this actor as an Apify **Task** with `deltaMode: true` and a `deltaName`
you choose, add an hourly (or daily) **Schedule**, and point the task's **webhook** at Discord,
Slack, Google Sheets, or an n8n/Make webhook URL to get pinged only when something actually
changes.

**Window limitation.** A new listing or price drop is only ever seen while it's still inside what a
run actually fetches (your "Most listings to return per search" budget, filtered by any
designer/size/category/condition/price filters you set). If a listing falls out of that window
between runs, this actor has no way to notice it. Keep searches reasonably narrow — a specific
designer, a tight category, a price band — rather than one huge catch-all if you want reliable
new/price-drop coverage.

### How to use

1. **In the Apify Console.** Open the actor page and click **Start** — the `searches` field is already pre-filled with a working example. Results land in the run's dataset as soon as each item is found.
2. **Via the API.** Call it directly with a POST request — no Console needed once you have an API token:
   ```bash
   curl "https://api.apify.com/v2/acts/accountable_eel~grailed-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
     -X POST \
     -H "Content-Type: application/json" \
     -d '{"searches":["carhartt jacket"]}'
   ```
3. **On a schedule.** Save this actor as an Apify **Task** with the input you want, then add a **Schedule** (hourly, daily, weekly) so it runs on its own — no server of your own required.

4) Turn on "Only return results that are new, or dropped in price" under Monitoring once you want a
   watchlist instead of a one-off dump — see "Monitoring / only new results" above.
5) Set "Listing type" to "Sold listings" for sold-price comps instead of active listings.

### Input

```json
{
  "searches": [
    "carhartt jacket"
  ]
}
```

One search per line — any keywords, e.g. "carhartt jacket", "arcteryx beta", "rick owens". No login required. Accepted formats: carhartt jacket, arcteryx beta, rick owens.

### Sample output

| query | found | status | searchQuery | listingType | listingCount | totalAvailable | truncated | newCount | priceDropCount | monitorStatus | activeCount | soldCount | sellThroughRate | compsWindowDays | activeMedianPrice | soldMedianPrice | askVsSoldGapPct | medianDaysToSell | listings | listingId | title | price | currency | designers | size | category | condition | color | location | postedAt | bumpedAt | isSold | soldAt | soldPrice | daysToSell | nativePriceDropCount | originalPrice | popularity | imageUrl | sellerHash | sellerId | sellerName | sellerProfileUrl | changeType | isNew | previousPrice | priceDropPct | firstSeenAt | url | scrapedAt |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| carhartt jacket | true | OK | carhartt jacket | active | 100 | 19782 | true | 0 | 0 |  | \<active listings fetched this run (sold comps only)> | \<sold comps fetched this run (sold comps only)> | \<sell-through rate: sold / (sold + active) (sold comps only)> | \<span of the fetched sold comps, oldest to newest sale (sold comps only)> | \<median asking price, usd (sold comps only)> | \<median sold price, usd (sold comps only)> | \<asking vs. sold median price gap % (sold comps only)> | \<median days from posted to sold (sold comps only)> | \<all listings found (full list)> | 106740257 | VINTAGE Carhartt Active Jacket Mens 3XL Sandstone Saddle Tan Thermal J25 Y2K Outdoor USA Bomber Jacket Brown Cotton Lined Hooded Logo | 143 | USD | Carhartt | xxl | outerwear | is\_used | brown | Other | 2026-09-23T05:43:48.108Z | 2026-09-23T05:43:39.523Z | false |  |  | \<days from posted to sold (sold listings only)> | 2 | 205 | 4667.312210648148 | https://media-assets.grailed.com/prd/listing/temp/7b16dd1460024a09b4ef97e7eab37dc7 | cd754af443d78023 | \<seller id (raw seller info only)> | \<seller username (raw seller info only)> | \<seller profile link (raw seller info only)> |  |  |  |  |  | https://www.grailed.com/listings/106740257 | 2026-09-23T06:20:15.963Z |

A search that finds nothing comes back as a row with `"found": false` and is never charged. A quiet
monitoring run comes back as a row with `"found": true, "monitorStatus": "NO_NEW_ROWS"` and is also
never charged.

### Use it from Clay, n8n, Make, or an AI agent

This actor runs synchronously over plain HTTP — call it directly from a script, a workflow tool, or an AI agent, no Apify Console needed once you have an API token.

```bash
curl "https://api.apify.com/v2/acts/accountable_eel~grailed-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"searches":["carhartt jacket"]}'
```

**n8n.** Add an HTTP Request node: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~grailed-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>`, Body Content Type `JSON`, JSON Body `{"searches":["carhartt jacket"]}` (swap in an expression from an earlier node for a real value).

**Clay.** Add an "HTTP API" column: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~grailed-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>`, Body `{"searches":["{{search}}"]}`, mapping the row's search into the `searches` array.

**MCP.** In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "Grailed Scraper: Sold Prices & New Listings | Apify" — the agent will find and run this actor.

For monitoring, point the Task's webhook (Console → your Task → Webhooks) at a Discord or Slack
incoming-webhook URL, a Google Sheets automation (via Zapier/Make/n8n listening for the webhook), or
an n8n/Make workflow's own webhook trigger, so new listings and price drops land wherever you
actually work instead of a dataset you have to remember to check.

### Tips

- Start monitoring with "Seed silently" on for any watchlist you're setting up on a schedule — it
  avoids a wall of "new" alerts for your entire current search result on day one.
- Keep a monitored search reasonably narrow (a designer, a tight category, a price band) — see
  "Window limitation" above for why a huge catch-all search misses new listings and price drops on
  rows that fall outside what gets fetched.
- Use `designers`/`sizes`/`categories`/`condition` to narrow a search server-side instead of
  filtering a big result set yourself downstream — Grailed's own facets do the work.
- `originalPrice` and `nativePriceDropCount` work on every run, monitoring or not — they're
  Grailed's own permanent record for that listing, not this actor's watchlist memory.
- A `BLOCKED` status usually clears on its own shortly; this actor doesn't need a proxy by default.

### vs. piotrv1001/grailed-scraper and the rest of the field

The current Apify Store leader for Grailed, `piotrv1001`, has 22 users and zero reviews; several
other listed Grailed scrapers haven't been updated in 4+ months. None of them expose Grailed's own
sold-listings index as a comps feed, and none offer new-listing or price-drop monitoring.

| | What it costs | What you get | Trade-off |
|---|---|---|---|
| **This actor** | Pay per listing returned; nothing for a miss or a quiet monitoring run | Active and sold listings, Grailed's own price-drop history, monitoring mode (new + price drop) | Seller location is coarse (a country/region), not a city — Grailed's own search index doesn't expose more |
| Other Grailed scrapers | Vary, several priced $1-12/1,000 | Usually active listings only, one-off dumps | No confirmed sold-comps or monitoring mode found in this niche as of this build |
| Doing it yourself | Your time to reverse-engineer the Algolia call, build a seen-listing store and a price-tracking layer | The same data | This actor's Algolia query construction, monitoring state, and key-recovery handling are the maintenance burden it absorbs |

### Data & privacy

This actor reads public search results that anyone can see without logging in. It doesn't log in,
solve CAPTCHAs, or reveal hidden contact details. Seller identity is off by default: you get a
private, always-on anonymous seller hash so you can group listings by seller without a name — raw
seller ID, username, and profile link are only included when you turn on "Include raw seller info".
Turning that on makes you responsible for having a lawful reason to process it. Photos are output as
links only, never downloaded or re-hosted. Not affiliated with Grailed.

**Is this allowed?** It collects the same public listing data your browser shows, for the searches
you choose. It's built for monitoring a search, not for copying the marketplace. Check that your use
fits Grailed's terms and your local law.

### FAQ

**Why is a row empty, or why does `found` say `false`?**
Either the input line was blank (`status: BAD_FORMAT`), Grailed's search key stopped working and
couldn't be recovered (`status: BLOCKED`), or the search matched nothing on Grailed right now
(`status: NOT_FOUND`). Check the `message` column for the specific reason. None of these are billed.

**Am I charged for a quiet monitoring run?**
No. When monitoring finds nothing new and no price drops, you get one row with
`monitorStatus: NO_NEW_ROWS` and `listingCount: 0` — `Actor.charge()` only fires when
`listingCount` is greater than zero.

**What's the difference between `priceDropCount` and `nativePriceDropCount`?**
`priceDropCount` (on the search/parent row) is *this watchlist's* count of price drops it noticed
this run — it's `0` unless monitoring is on. `nativePriceDropCount` (per listing) is Grailed's own
permanent count of that listing's price history, independent of monitoring — it can be nonzero even
on your very first, non-monitored run.

**Can I get sold prices, not just asking prices?**
Yes — set "Listing type" to "Sold listings" or "Both", or turn on "Include sold comps and
sell-through stats" to get sold comps alongside your active search plus sell-through rate and
median-price-gap columns. See "Sold comps" and "Sold comps and sell-through" above.

**Do I need to configure proxies?**
No, and this actor doesn't support one. Grailed's own Algolia search endpoint (where the actual
listing data comes from) has no anti-bot protection in front of it and needs none. grailed.com's own
homepage does sit behind a Cloudflare challenge that a proxy-less HTTP request can't clear — this
actor only visits that page as a last-resort key-recovery step if Grailed ever rotates its public
search key, and even that recovery attempt runs without a proxy per this build's scope.

**What happens if Grailed rotates its Algolia key?**
This actor tries a live re-read of grailed.com once, then reports `status: BLOCKED` with a message
that says the key appears to have rotated, rather than silently returning nothing. This shows up as
a real, visible miss — not a run that quietly looks healthy while returning garbage.

**Can an AI agent call this directly?**
Yes. It's registered on the Apify MCP server — an agent in Claude, Cursor, or another MCP client can
find and run it by name ("Grailed Scraper: Sold Prices & New Listings | Apify"), or you can call the
REST endpoint shown above from any script or workflow tool.

# Actor input Schema

## `searches` (type: `array`):

One search per line — any keywords, e.g. "carhartt jacket", "arcteryx beta", "rick owens". No login required. Accepted formats: carhartt jacket, arcteryx beta, rick owens. You're only charged for the ones we actually find — a miss costs nothing.

## `testRun` (type: `boolean`):

Turn this on to test your input on a small sample before running the full list. Turn it off to process everything.

## `onlyFound` (type: `boolean`):

Only keep rows where something was actually found. Misses are always free, whether or not you show them here.

## `includeKeywords` (type: `array`):

Optional. Only keep results that mention at least one of these words (e.g. a job title, a city, a product name). Leave empty to keep everything.

## `excludeKeywords` (type: `array`):

Optional. Drop any result that mentions one of these words. Leave empty to skip nothing.

## `maxResults` (type: `integer`):

Optional. Stop the run once this many results have been found — useful for a quick, cheap sample. Leave blank for no limit.

## `listingType` (type: `string`):

Sold listings are Grailed's own sold-price archive — a comps feed, not a live-for-sale listing. "Both" splits your "Most listings to return" budget evenly across the two.

## `maxListingsPerSearch` (type: `integer`):

Grailed's search returns up to 1,000 matches per query (Algolia's own pagination window); this actor pages in batches of 100 to reach your limit. You pay per listing returned, so this is also your budget control.

## `includeSoldComps` (type: `boolean`):

Off by default. When on, this search also fetches Grailed's sold-listings index for the same keywords and filters, returns each sold comp as an ordinary listing row (isSold, soldAt, soldPrice, daysToSell), and adds sell-through summary columns (activeCount, soldCount, sellThroughRate, activeMedianPrice, soldMedianPrice, askVsSoldGapPct, medianDaysToSell) to every row of this search. Sold comps are billed as ordinary listings — see "Sold comps and sell-through" in the README.

## `maxSoldComps` (type: `integer`):

Only used when "Include sold comps" is on. Caps how many sold listings this search fetches for comps, newest sold first. Max 200.

## `designers` (type: `array`):

Optional. Exact designer name(s) as Grailed spells them, e.g. "Carhartt", "Rick Owens", "Arc'teryx". Leave empty for any designer.

## `sizes` (type: `array`):

Optional. Grailed's own size labels for the category you're searching, e.g. "m", "l", "32", "10.5". Leave empty for any size.

## `categories` (type: `array`):

Optional. Grailed's own category slugs, e.g. "outerwear", "tops", "bottoms", "footwear", "accessories". Leave empty for any category.

## `condition` (type: `string`):

Optional. Matches Grailed's own condition facet on the listing. Leave as "Any condition" to skip this filter.

## `minPrice` (type: `integer`):

Optional. Leave empty for no minimum.

## `maxPrice` (type: `integer`):

Optional. Leave empty for no maximum.

## `deltaMode` (type: `boolean`):

Turns this actor into a monitor. A listing counts as new when its Grailed listing ID has not been returned by a previous run of the same watchlist, and as a price drop when its price falls since it was last seen (see "Minimum price drop" below). For sold listings, "new" means newly sold since the last run — a comps feed. Already-seen, unchanged listings are dropped before you are billed, so a quiet run costs only the run fee. The first run has nothing to compare against, so (unless "Seed silently" is on) it returns everything and remembers it.

## `deltaName` (type: `string`):

Leave empty and we derive one from this run's search settings, so two schedules with different settings keep separate memories. Type your own name to keep one memory across a settings change, or to have two schedules share one. Naming a watchlist with monitoring off still stamps each row with "Is this new?" and "First seen" so you can filter it yourself in Sheets, n8n or Make.

## `alertOnNew` (type: `boolean`):

Include newly-seen listings (or, for sold listings, newly-sold ones) when monitoring is on. Turn off to get price-drop alerts only.

## `alertOnPriceDrop` (type: `boolean`):

Include listings whose price dropped since this watchlist last saw them. Turn off to get new-listing alerts only.

## `minPriceDropPct` (type: `integer`):

A listing must drop by at least this percentage since it was last seen by THIS monitor to be reported as a price-drop. Independent of Grailed's own price-drop history below, which needs no monitoring to work.

## `skipFirstRun` (type: `boolean`):

On by default for most buyers' first schedule run: instead of returning every current listing as "new" the first time a watchlist runs, this banks them silently and starts alerting from the second run on. Stops a fresh watchlist from spamming a hundred messages to your webhook on day one.

## `includeSellerInfo` (type: `boolean`):

Off by default. When on, adds the seller's Grailed user ID, username and profile link. An anonymous seller hash is always included either way, so you can group listings by seller without turning this on. Turning it on makes you responsible for having a lawful reason to process that data.

## `columns` (type: `array`):

Choose which pieces of information to include in each result row. All are included by default.

## `expandRows` (type: `boolean`):

When on, each listing found gets its own row instead of being grouped under its search. You're still only charged once per search, no matter how many rows it produces.

## `maxConcurrency` (type: `integer`):

Parallel requests. Keep conservative — this target has no browser fallback, so getting blocked costs more than slow-and-steady.

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

Apify Proxy config. Residential recommended for anti-bot-sensitive targets.

## Actor input object example

```json
{
  "searches": [
    "carhartt jacket"
  ],
  "testRun": false,
  "onlyFound": false,
  "includeKeywords": [],
  "excludeKeywords": [],
  "listingType": "active",
  "maxListingsPerSearch": 100,
  "includeSoldComps": false,
  "maxSoldComps": 50,
  "designers": [],
  "sizes": [],
  "categories": [],
  "condition": "",
  "deltaMode": false,
  "deltaName": "",
  "alertOnNew": true,
  "alertOnPriceDrop": true,
  "minPriceDropPct": 5,
  "skipFirstRun": false,
  "includeSellerInfo": false,
  "columns": [
    "searchQuery",
    "listingType",
    "listingCount",
    "totalAvailable",
    "truncated",
    "newCount",
    "priceDropCount",
    "monitorStatus",
    "activeCount",
    "soldCount",
    "sellThroughRate",
    "compsWindowDays",
    "activeMedianPrice",
    "soldMedianPrice",
    "askVsSoldGapPct",
    "medianDaysToSell",
    "listings",
    "listingId",
    "title",
    "price",
    "currency",
    "designers",
    "size",
    "category",
    "condition",
    "color",
    "location",
    "postedAt",
    "bumpedAt",
    "isSold",
    "soldAt",
    "soldPrice",
    "daysToSell",
    "nativePriceDropCount",
    "originalPrice",
    "popularity",
    "imageUrl",
    "sellerHash",
    "sellerId",
    "sellerName",
    "sellerProfileUrl",
    "changeType",
    "isNew",
    "previousPrice",
    "priceDropPct",
    "firstSeenAt",
    "url"
  ],
  "expandRows": true,
  "maxConcurrency": 5,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `results` (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 = {
    "searches": [
        "carhartt jacket"
    ],
    "includeKeywords": [],
    "excludeKeywords": [],
    "designers": [],
    "sizes": [],
    "categories": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("accountable_eel/grailed-listing-lookup").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 = {
    "searches": ["carhartt jacket"],
    "includeKeywords": [],
    "excludeKeywords": [],
    "designers": [],
    "sizes": [],
    "categories": [],
}

# Run the Actor and wait for it to finish
run = client.actor("accountable_eel/grailed-listing-lookup").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 '{
  "searches": [
    "carhartt jacket"
  ],
  "includeKeywords": [],
  "excludeKeywords": [],
  "designers": [],
  "sizes": [],
  "categories": []
}' |
apify call accountable_eel/grailed-listing-lookup --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,accountable_eel/grailed-listing-lookup"
        }
    }
}
```

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/A3D8aICJBJMpVt8Rq/builds/Bob0x25sVel1Xcnfo/openapi.json