supreme.com APIsupreme.com ↗
Access Supreme product listings, season previews, news, lookbooks, and store locations via a single API. 13 endpoints covering current and past seasons.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/245bc22a-05fc-4daf-b21a-cc3e8b57d37a/get_shop_status' \ -H 'X-API-Key: $PARSE_API_KEY'
Get current shop status including region info, active season, shop URL, and lookbook links.
No input parameters required.
{
"type": "object",
"fields": {
"season": "string, current active season name",
"regions": "integer, number of regional configurations",
"lookbook": "object with title and url of current lookbook",
"shop_url": "string, URL to the shop page",
"alert_message": "string or null, current alert bar message",
"web_store_code": "integer, web store identifier code",
"footer_previews": "array of season preview links with title and url"
},
"sample": {
"data": {
"season": "spring/summer 2026 preview",
"regions": 6,
"lookbook": {
"url": "/lookbook/45",
"title": "Spring/Summer 2026 Lookbook"
},
"shop_url": "https://eu.supreme.com/pages/shop",
"alert_message": null,
"web_store_code": 202,
"footer_previews": [
{
"url": "/previews/springsummer2026",
"title": "Spring/Summer 2026 Preview"
}
]
},
"status": "success"
}
}About the supreme.com API
The Supreme API exposes 13 endpoints covering the brand's product catalog, seasonal previews, news articles, lookbooks, and retail store data. Use get_product_listings to pull all current-season items with variants and categories, get_stores to retrieve worldwide retail locations with coordinates and hours, or get_lookbook to fetch look images paired with linked products — all in structured JSON.
Product Catalog and Season Data
The get_product_listings and get_season_preview endpoints return the full product catalog for a given season, accepting an optional season parameter like 'springsummer2026' or 'fallwinter2025'. Each product object includes _id (UUID), slug, title, category, variants (with per-variant title, description, and images), and a description field. To narrow by category, use get_products_by_category with a category_slug value obtained from get_categories. Detailed per-product data including all variant images is available via get_product_detail, which accepts either a UUID or slug as product_handle.
Shop Status, News, and Lookbooks
get_shop_status returns the currently active season name, the shop URL, any active alert bar message, regional configuration count, and footer_previews — an array of season preview links. News content is accessible via get_news_list, which returns articles with full body, images, publishedAt timestamps, and slugs. Individual articles can be fetched with get_news_article by UUID or numeric slug. Lookbooks are indexed through get_lookbook_list, which returns IDs and titles, and retrieved individually with get_lookbook using a lookbook_id like '45' for Spring/Summer 2026.
Store Locations
get_stores returns every Supreme retail location worldwide, including slug, title, address, opening hours, region (e.g. 'us', 'eu', 'jp', 'cn'), and a location object with lat/lng coordinates. get_store_detail accepts a store_slug such as 'new-york' or 'paris' and adds phoneNumber to the response. The get_about endpoint retrieves the brand history page as structured content blocks plus extracted plain-text strings in body_text.
- Track new-season product drops by polling
get_shop_statusfor season changes and then fetchingget_season_preview - Build a Supreme product browser filtered by category using
get_categoriesandget_products_by_category - Display lookbook imagery and linked products for a given season using
get_lookbookwith a specificlookbook_id - Map all Supreme retail stores with coordinates from
get_storeslocation objects for a store-finder feature - Aggregate Supreme news content with publication dates by pulling
get_news_listand resolving full articles viaget_news_article - Monitor the Supreme alert bar message and active shop URL in real time using
get_shop_status - Retrieve per-variant images and descriptions for a specific product using
get_product_detailwith a UUID or slug
| 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 Supreme have an official developer API?+
What does `get_product_detail` return, and how do I find the right product handle?+
get_product_detail returns the product's UUID, slug, title, category object, variant array (each with title, description, and images), and description text. The required product_handle input accepts either the UUID or slug from a prior get_product_listings or get_season_preview call. The optional season parameter scopes the lookup; if the product isn't found in that season the endpoint returns a stale_input signal.Does the API expose live inventory, pricing, or add-to-cart availability?+
How are seasons referenced across endpoints?+
'springsummer2026' or 'fallwinter2025'. Most catalog endpoints — get_season_preview, get_categories, get_products_by_category, and get_product_detail — accept a season string parameter. When omitted, they default to the current active season. The active season name is also returned by get_shop_status in its season field.Does the API cover regional product differences or Japan/China-specific catalogs?+
regions count from get_shop_status and a region field per store in get_stores and get_store_detail, but product listings are not currently split by regional catalog. You can fork it on Parse and revise to add region-filtered product endpoints if that distinction is needed.