grailed.com APIgrailed.com ↗
Access Grailed marketplace data: search listings by designer, size, and condition; get seller profiles, reviews, categories, and curated collections.
curl -X GET 'https://api.parse.bot/scraper/1d371b7c-7d43-4fc3-8c3e-fbce675b34ac/search_listings?page=0&sort=price_low&limit=10&query=nike+dunk&department=menswear' \ -H 'X-API-Key: $PARSE_API_KEY'
Search for listings with optional filters like department, category, designer, size, and condition. Supports various sort orders and pagination.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number (0-indexed) |
| size | string | Size filter |
| sort | string | Sort order: most_relevant, price_low, price_high, newest, popular |
| limit | integer | Results per page |
| query | string | Search keyword |
| category | string | Category path filter (e.g. footwear.lowtop_sneakers) |
| designer | string | Designer name filter |
| condition | string | Condition filter (is_new, is_gently_used, is_used, is_worn) |
| department | string | Department filter (menswear, womenswear) |
{
"type": "object",
"fields": {
"hits": "array of listing objects with id, title, price, designers, condition, photos, seller info",
"page": "integer current page number",
"nbHits": "integer total number of matching listings",
"nbPages": "integer total number of pages"
},
"sample": {
"data": {
"hits": [
{
"id": 96733038,
"size": "12",
"price": 120,
"title": "Nike Dunk Low Brazil Green Yellow Size 12",
"condition": "is_gently_used",
"department": "menswear",
"designer_names": "Nike"
}
],
"page": 0,
"nbHits": 17125,
"nbPages": 100
},
"status": "success"
}
}About the grailed.com API
The Grailed API provides 9 endpoints covering the full Grailed fashion resale marketplace — from searching listings with filters like designer, condition, and category via search_listings, to retrieving detailed seller profiles, buyer reviews, and curated homepage collections. Each listing response includes price, photos, seller info, shipping rates, and designer attribution, giving you structured access to the data that powers one of the largest menswear and womenswear resale platforms.
Search and Listing Data
The search_listings endpoint accepts filters for query, category (using dot-notation paths like footwear.lowtop_sneakers), designer, size, condition, and sort order (most_relevant, price_low, price_high, newest, popular). Results are paginated (0-indexed page) and return an array of listing objects alongside nbHits and nbPages for cursor management. The get_listing_detail endpoint accepts a listing_id and returns the complete listing record: price, size, condition, description, photos (with url, width, height), associated designers, seller profile, and itemized shipping rates by region.
Seller and Review Data
get_seller_profile returns a seller's top_designers and an array of ratings objects. get_seller_listings pages through all active listings for a given user_id, returning the same hit shape as the search endpoint. get_seller_reviews returns the full review history for a seller including each review's rating, tag_list, free-text note, and the associated listing details — useful for building trust-signal dashboards or vetting sellers before integrating them into a workflow.
Categories, Designers, and Collections
get_categories returns the complete category hierarchy for both menswear and womenswear departments, with each node carrying a slug and subcategory paths that map directly to the category filter in search_listings. list_popular_designers returns up to 100 designer objects with id, name, slug, count (number of active listings), and departments. get_homepage_collections exposes curated capsule collections with name, published_at, followerno, and a detail_page containing slug and description.
Similarity and Discovery
The get_similar_listings endpoint takes a listing_id and returns a hits array of similar items matched by designer and category, along with pagination metadata. This is useful for building recommendation flows or scraping the competitive landscape around a specific item.
- Track price trends for specific designers by querying
search_listingswithsort: price_lowandsort: price_highover time - Build a seller reputation tool by combining
get_seller_profile,get_seller_reviews, andget_seller_listingsfor a given user - Populate a resale price database by paginating
search_listingsfiltered bycondition: is_newand specific designers - Detect arbitrage opportunities by comparing
get_similar_listingsresults against a listing'spricefield - Build a category browser using the full menswear and womenswear hierarchy from
get_categories - Monitor designer popularity shifts using the
countfield fromlist_popular_designerspolled over time - Curate editorial content feeds using
get_homepage_collectionsto surface Grailed's capsule collections
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Grailed have an official public developer API?+
What does `get_listing_detail` return beyond what `search_listings` provides?+
get_listing_detail returns fields not present in the search hit objects: a full description string, itemized shipping rates broken out by region, and a higher-fidelity photos array with explicit width and height per image. The search endpoint returns enough to display a card; the detail endpoint returns enough to display a full listing page.Does pagination work the same way across all list endpoints?+
page parameters and return nbHits and nbPages for range control — this applies to search_listings, get_seller_listings, and get_similar_listings. get_seller_reviews and get_seller_profile do not currently expose pagination parameters and return results in a single response. You can fork the API on Parse and revise it to add paginated review fetching if you need to handle high-volume review histories.Does the API expose sold/completed listing history or just active listings?+
search_listings or get_seller_listings. Historical sale prices and sold-out inventory are not exposed. You can fork the API on Parse and revise it to add an endpoint targeting completed transaction data if that becomes available from the source.Can I filter `search_listings` by multiple designers or sizes at once?+
designer and size parameters each accept a single value per request. Multi-value filtering is not currently supported in one call. You can parallelize requests across values client-side, or fork the API on Parse and revise it to support comma-separated or array-style multi-value inputs.