Updated 10 September 2026
Sneaker data methodology. Context comes first.
How KicksAPI collects, normalises and presents sneaker price and product data.
Sources
KicksAPI receives asking prices and product data from StockX and GOAT through a data provider, for the United States, the United Kingdom, Germany and the Netherlands. Retailer prices are planned but not yet included. Every value carries its source and observation time. The interactive sample on this site is a static example; the API returns current data.
Asking prices and sales
An asking price is what a seller requests. A completed-sale price records an actual transaction. They must remain distinct; KicksAPI currently returns asking prices only. Product, size, condition, market, currency and delivery type determine whether two observations are comparable.
Update frequency
Prices are collected as daily snapshots. Supplier caching can add delay before KicksAPI receives a value, so source timestamps accompany every price and applications should show its age. History depth per product depends on when observation started and is returned with each history response.
Scope and permissions
Every plan covers use inside your own applications, tools and dashboards. Redistribution or resale of the raw feed needs a written agreement. KicksAPI is independent of the marketplaces mentioned on this site.