Sold comps that carry the asking price and the real one
The Grailed API returns curated menswear, streetwear and archive-fashion resale data as clean JSON.
6 active endpoints. Every call is 1 credit.
- POST/grailed/v1/search
- POST/grailed/v1/listing_detail
- POST/grailed/v1/sold_listings
- POST/grailed/v1/seller_listings
- POST/grailed/v1/designers
- POST/grailed/v1/designer_detail
What Grailed endpoints does ReefAPI ship?
6 live read endpoints. Read-only data API: no writes, no account actions, no dashboard access on the target site.
Grailed API
3 of 6 endpoints, ready to run
Resale comps: every row carries the price the seller asked, the price it ACTUALLY sold for and the moment it sold — plus designer, size, colour, condition and category. This is the difference between a valuation and a guess.
{ "ok": true, "meta": { "api": "grailed", "endpoint": "sold_listings", "mode": "live", "latency_ms": 771.6, "record_count": 40, "cache_hit": false }, "data": { "listings": [ { "id": 98971399, "title": "Stone Island Black Nylon Jacket", "url": "https://www.grailed.com/listings/98971399", "price": 220, "currency": "USD", "size": "m", "condition": "is_gently_used", "condition_label": "Gently Used", "color": "black", "category": "outerwear", "category_path": "outerwear.light_jackets", "department": "menswear", "designers": [ { "id": 101, "name": "Stone Island", "slug": null } ], "designer_names": "Stone Island", "strata": "grailed", "location": "United States", "follower_count": 51, "photo_count": 5, "cover_photo": "https://media-assets.grailed.com/prd/listing/temp/fb3d06fa79044847a1c4bbe9b9383884", "buy_now": true, "make_offer": true, "sold": true, "created_at": "2026-06-20T03:06:09.908Z", "sold_price": 200, "sold_at": "2026-08-28T18:23:35.570Z" }, { "id": 95674213, "title": "Stone Island Nylon Metal Shorts Swimming Trunks", "url": "https://www.grailed.com/listings/95674213", "price": 90, "currency": "USD", "size": "34", "condition": "is_gently_used", "condition_label": "Gently Used", "color": "gold", "category": "bottoms", "category_path": "bottoms.shorts", "department": "menswear", "designers": [ { "id": 101, "name": "Stone Island", "slug": null } ], "designer_names": "Stone Island", "strata": "grailed", "location": "Europe", "follower_count": 6, "photo_count": 9, "cover_photo": "https://media-assets.grailed.com/prd/listing/temp/7bc40505ebdc4214b42801029e978563", "buy_now": true, "make_offer": true, "sold": true, "created_at": "2026-04-20T19:32:30.144Z", "sold_price": 60, "sold_at": "2026-08-28T18:16:07.226Z" }, { "id": 97929098, "title": "Stone Island Bermuda Fleece Shorts Pants Trousers Grey", "url": "https://www.grailed.com/listings/97929098", "price": 229, "currency": "USD", "size": "34", "condition": "is_new", "condition_label": "New/Never Worn", "color": "gray", "category": "bottoms", "category_path": "bottoms.shorts", "department": "menswear", "designers": [ { "id": 101, "name": "Stone Island", "slug": null } ], "designer_names": "Stone Island", "strata": "grailed", "location": "Europe", "follower_count": 45, "photo_count": 11, "cover_photo": "https://media-assets.grailed.com/prd/listing/temp/ba2bef2f12024cb3893d1c4077dcb636", "buy_now": true, "make_offer": true, "sold": true, "created_at": "2026-06-02T16:11:23.081Z", "sold_price": 170, "sold_at": "2026-08-28T14:16:29.378Z" } ] } }
How the Grailed API works
Grailed is a normal ReefAPI surface — the same four rules that hold for every other engine on the key.
No OAuth app, no request signing, no per-site account. One key covers all 184 engines.
Every route is a POST with a JSON body. Parameters are validated against the published schema before anything is charged.
Credits, not seats. Failed and blocked calls are never charged, and cache hits cost nothing.
One envelope everywhere. meta carries latency_ms, record_count and the endpoint that answered.
Value a garment against what it really sells for
A price on a live listing is an opinion. The number that settles an argument is what somebody paid last week, and it is a different field on a different endpoint.
{"query": "stone island"}Turns your brand string into the exact name the filters accept, with the slug and a listing count. Skip this and a designer filter silently matches nothing.
{"designer": "Stone Island", "size": "l", "sort": "newest"}Comps with sold_price and sold_at on every row, next to the price that was asked. Narrow with filters rather than paging — the ceiling is measured below.
{"designer": "Stone Island", "size": "l", "price_to": 300}The live side of the same market, so you can see what is being asked today against what cleared this week.
A defensible price for one garment in one size, built from real transactions rather than from asking prices — and the live inventory that is currently competing with it.
curl -X POST https://api.reefapi.com/grailed/v1/sold_listings \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"query":"supreme","per_page":5}'{
"ok": true,
"data": { … },
"meta": {
"api": "grailed",
"endpoint": "sold_listings",
"mode": "live",
"latency_ms": …,
"record_count": …
},
"error": null
}Grailed condition, strata and price fields as they come back
Grailed's filters take machine enum values while the response also carries a human label, and mixing the two up is the usual reason a filter silently matches nothing, since most filters are ignored on a bad value rather than rejected. Rows measured 2026-08-27 on live search, sold_listings, listing_detail and designers calls.
| Field | Values seen live | What to watch |
|---|---|---|
| condition | is_new, is_gently_used, is_used, is_worn, is_not_specified | Filter with the enum; condition_label carries the display text such as "Gently Used" |
| strata | grailed, hype, sartorial, basic | Grailed's curation tier, not a product category |
| price / currency | Whole-dollar integers: 671, 199, 34, 17 | currency was "USD" on every row, including listings from Europe-based sellers |
| sold_price / sold_at | Only on sold_listings. ISO-8601 with milliseconds. | 199 sold at 2026-08-26T14:11:25.298Z; sold_price equalled price on the rows measured |
| size / pretty_size / exact_size | "s" against "US S / EU 44-46 / 1" against null | Filter with the lowercase facet value; pretty_size is display only |
| designers[].slug | null in search and sold rows, filled in listing_detail | Stone Island is id 101, name "Stone Island", slug "stone-island" |
| shipping | Per-region flat amounts in USD | us 30, ca 30, uk 30, eu 30, asia 35, au 25, other 40, each with an enabled flag |
| pagination | 200 pages maximum at up to 100 per page | One sold query reported total_results 19,611 against total_pages 200, so about 20,000 rows are reachable |
measurements[] came back as an empty array on a listing whose own description spells the measurements out in full: "Shoulder: 46.5cm, Chest: 54cm, Length: 65.5cm, Sleeve: 64.5cm". Sellers type them into free text instead of Grailed's structured fields, so parse `description` if you need garment dimensions. `color` behaves the same way: it was null on that listing while traits carried {"name": "color", "value": "blue"} and {"name": "country_of_origin", "value": "IT"}.
Real sale prices, one currency, and where paging stops
Measured against the live gateway on several designers and queries. One of these will decide how you build the crawl.
Forty of forty sold rows carried sold_price, sold_at and the original asking price together. Eleven of the forty sold at exactly the asking price; the rest closed below it, in a band running from a few per cent under to roughly half off. You do not have to infer a discount — both numbers are there and you can divide them yourself.
Every listing and every comp we measured carried currency: USD on the row itself, not left to be inferred from a locale. Grailed's price filters are dollars too, so a price band means the same thing on the request and on the response.
Page 25 returned a full forty rows. Page 26 returned zero, with has_more false and the reported total dropping to zero — a clean stop, but a stop, and it lands at 25 pages of 40 against the 22,929 results the same query claims. Narrow with designer, size, category and price band; do not try to walk a broad query to the end, because there is no end to reach.
The forty newest sold rows for one query spanned three days. Sorted newest-first, this is a rolling window of what actually cleared, which is what makes it usable for pricing rather than for history.
Run back to back, one comp query returned the identical forty listing ids both times, and page one and page two of it shared nothing. Deterministic in both directions, so a nightly diff is signal.
Grailed is a person-to-person market: every row carries the seller's handle, avatar, profile link and trading history, and the API returns all of it. The sample response on this page drops that block before it is published. That is our rule about our own indexable pages, not a limit on what you receive.
An invented listing id answers NOT_FOUND with retryable false, naming the id. Sold items stay reachable through sold_listings rather than vanishing, so a not-found here means the listing was deleted or never existed — a different decision from an item that simply sold.
Rows carry a machine condition code with a human label beside it, a market tier that separates the curated grail listings from the rest, and a category path a level deeper than the top-level category. Every one of them is also a filter, so a comp set can be narrowed to the exact shape of the thing you are valuing.
What people build with Grailed
The jobs this data is most often used for.
endpoints
credit per call
Resale-price tools call search and sold_listings to value an item from real completed sales.
Fashion apps use designer_detail and search to surface listings by brand and category.
Resellers use seller_listings to track a competitor's inventory and pricing on Grailed.
What Grailed data costs
The cheapest call here is 1 credit, so $15/mo (Pro) buys 10,000 of them — $1.50 per 1,000 credits. Credits roll over and never expire, and failed or blocked calls are not charged.
Full pricing →- 1,000 free credits on signup, no card
- One key, all 184 APIs, one credit pool
- Failed and blocked calls are never charged
- Credits roll over and never expire
Call it in two lines
Sign up, get 1,000 credits and one key that works on every engine. Then this is the whole protocol.
curl -X POST https://api.reefapi.com/grailed/v1/sold_listings \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"query":"supreme","per_page":5}'import requests
r = requests.post(
"https://api.reefapi.com/grailed/v1/sold_listings",
headers={"x-api-key": REEF_KEY},
json={
"query": "supreme",
"per_page": 5
},
)
print(r.json()["data"])Have a question? We got answers.
The questions people actually ask before wiring up Grailed.
Get a free key →What are the condition values, exactly?▾
Five: is_new (New/Never Worn), is_gently_used (Gently Used), is_used (Used), is_worn (Well Worn) and is_not_specified (Not Specified). Filters take the underscore-prefixed enum, while each returned listing carries both `condition` with the enum and `condition_label` with the display string. There is no numeric condition score. The "CONDITION: 9/10" you often see on Grailed is seller free text inside `description`, not a field.
What is strata and how is it different from category?▾
strata is Grailed's curation tier, which is orthogonal to what the item is. Four values came back live: grailed (high-end and archive designers), hype (streetwear and hyped brands), sartorial (tailored menswear) and basic (entry level). A Supreme box logo hoodie returned strata "hype" with category "tops" and category_path "tops.sweatshirts_hoodies", while a Stone Island denim jacket returned strata "grailed" with category_path "outerwear.denim_jackets". Use category or category_path for what it is, and strata for which market you are pricing.
Are the sold comps real transaction prices?▾
They are the prices Grailed records against completed sales, returned as sold_price with a sold_at ISO-8601 timestamp down to milliseconds. A live sold_listings search for "supreme box logo" sorted newest reported total_results 19,611, and the top row was a hoodie at sold_price 199 sold at 2026-08-26T14:11:25.298Z. In every row measured sold_price matched the listed price, so compare the two fields yourself rather than assuming an accepted offer is always reflected. Both ship on every sold row.
Why is measurements[] empty when the listing clearly has measurements?▾
Because Grailed's structured measurement fields are optional and most sellers ignore them. A live listing_detail call returned measurements: [] on a Stone Island jacket whose description contained "MEASUREMENTS: Shoulder: 46.5cm, Chest: 54cm, Length: 65.5cm, Sleeve: 64.5cm". If garment dimensions matter to your product, plan on parsing `description` and treat measurements[] as a bonus when it is populated. That same listing did return pretty_size "US S / EU 44-46 / 1", which is at least a consistent cross-region size string.
Is everything priced in USD even for sellers outside the US?▾
Yes. Every listing measured returned currency "USD", including rows whose seller location was Europe or Asia. Grailed quotes its whole marketplace in dollars, and the price_from and price_to filters are USD too. Prices come back as whole integers rather than decimals (671, 199, 34, 31), so there are no cents to divide out.
How deep can I page a search?▾
Up to 200 pages at up to 100 results per page, which caps any single query at roughly 20,000 rows regardless of how many matches exist. A sold search reported total_results 19,611 against total_pages 200, so it just fit; a broad active search reported 6,168 matches, well inside the ceiling. Page with `page` while meta.pagination.has_more is true, and when a query is bigger than the ceiling, split it with filters such as designer, category_path or a price band rather than paging harder.
How do I filter by designer without guessing the spelling?▾
Call the designers action first: it takes a partial name and returns the exact string the filters expect. A live lookup for "stone" returned 19 designers, with Stone Island coming back as id 101, name "Stone Island", slug "stone-island", listings_count 20,688, departments [menswear, womenswear] and a collaborations list naming "Supreme x Stone Island" with designer_ids [6, 101]. Feed the exact `name` into the designer filter on search or sold_listings, and the `slug` into designer_detail.
What does the seller object contain, and does it differ between actions?▾
Yes, listing_detail returns considerably more. Search and sold rows give id, username, rating_average, rating_count, total_bought_and_sold and trusted_seller. listing_detail adds location, avatar_url, listings_for_sale_count, sold_count, follower_count, verified and the account's created_at. A live call returned seller ROAMWALK, id 1839334, rating_average 4.9 from 3,135 ratings, 5,862 items bought and sold, 31,361 listings for sale, trusted_seller false and verified false, on an account opened in 2018. The listing itself also carries was_digitally_authenticated, which was true on that item.
What is the Grailed API?▾
Grailed API is a ReefAPI endpoint group for grailed It returns live JSON through POST requests under /grailed/v1.
Is the Grailed API free to try?▾
Yes. ReefAPI starts with 1,000 free credits, no card required. Grailed calls use the same shared credit balance as every other ReefAPI engine.
Do I need a Grailed login or account?▾
No login to Grailed is needed for the API response. You call ReefAPI with your x-api-key header, and the playground can run live examples before you create a production key.
How fresh is the Grailed data?▾
The page example is captured from a live search call, and production requests fetch live data through ReefAPI rather than a static sample.
How many credits does the Grailed API use?▾
Grailed actions currently cost 1 credit per successful call. Failed or blocked calls are free, and all APIs draw from one credit pool.
Can I call Grailed from an AI assistant or MCP client?▾
Yes. Connect ReefAPI once through MCP and your assistant can call grailed actions with the same key, credit pool and JSON envelope used by normal REST requests.
36 E-commerce & Marketplaces APIs on the same key
One key, one credit pool, one response envelope. If you are pulling Grailed, you are one call away from the rest of the category — no second contract, no second integration.
Need something this API does not do?
Name the endpoint, the field, or a source we do not carry yet. We ship new APIs every week and you would be first to get the key. Real people read every message and reply the same day.
Try it on your own data before you pay anything
The call above is the real endpoint, not a recording. A free key gives you 1,000 credits, the other 183 APIs, and the same envelope everywhere.
Endpoints, parameters and credit costs on this page are read from the live catalog and cannot drift from what the API accepts. Field notes were captured on 2026-08-28.