StockX upcoming release calendar API

Endpoint facts

Method

GET

API path

/stockx/releases

Auth

apiKey

Credits

2 credits/request

Platform

StockX

Response schema

#/definitions/stockx.releasesResponseDoc

Overview

Returns a date-ordered page (release date ascending) of StockX's upcoming release calendar: new and restocked products releasing on or after the given date, with normalized product summaries, headline pricing, and each item's published release date. Credential-free public data from the same GraphQL API backing StockX's own releases page. Developers commonly use this endpoint for data enrichment, monitoring, research dashboards, internal automation, and agent-native workflows that need repeatable structured public web data. Authentication uses the documented Crawlora headers, and usage is metered with the credit cost shown on this page.

Authentication

Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.

Billing

Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.

Credit cost

2 credits/request

Charged response

Successful 2xx responses

Infrastructure behavior

This endpoint is executed through Crawlora's managed scraping infrastructure.

• Proxy strategy: managed automatically where needed
• Browser rendering: enabled for supported targets that require rendered HTML or JavaScript execution
• Browser cluster: supported dynamic workloads can be routed through distributed browser instances
• Retry behavior: automatic retry/fallback may be used depending on endpoint type
• Challenge handling: challenged pages or unusable upstream HTML are detected and surfaced clearly when they cannot be used
• Billing: credits are charged only for successful 2xx responses
• Observability: responses include request context where available

Response behavior

- Results are always sorted by release date ascending, starting from `from`. StockX's release calendar mixes true street-date releases with items whose original street date has passed but were newly listed/restocked, so an occasional older `release_date` appearing near the top of the page is expected upstream behavior, not a parser bug. - `total_count` reflects StockX's full matching-result count for the applied `from` filter, not just `len(releases)`. - Each `releases[]` entry uses the same shape as a `/stockx/search` result row, with `release_date` additionally populated from StockX's own published release-date trait. - An invalid `from` value (not `YYYY-MM-DD`) returns `400` before any upstream request is made. Example response: ```json { "code": 200, "msg": "OK", "data": { "from": "2026-08-04", "page": 1, "limit": 20, "total_count": 469, "releases": [ { "id": "019eaf97-6952-7315-aaca-64a3d36b691d", "url_key": "nike-kobe-5-protro-jalen-brunson-ny-vs-ny-pe", "title": "Nike Kobe 5 Protro Jalen Brunson NY vs. NY PE", "brand": "Nike", "model": "Nike Kobe 5 Protro", "gender": "men", "product_category": "sneakers", "image_url": "https://images.stockx.com/images/nike-kobe-5-protro-jalen-brunson-ny-vs-NY-pe.jpg", "release_date": "2026-08-04", "lowest_ask": 520, "highest_bid": 550, "last_sale": 599 } ] } } ```

Error behavior

Crawlora does not silently return bad data when the upstream page cannot be used.

When possible, Crawlora returns structured error context so your integration can retry, back off, or inspect the request.

Related