V2 API Overview
This section documents the V2 API routes with prefix:
/api/v2Authentication
- Include your API token as a Bearer token in the
Authorizationheader.
Global Response Fields
All V2 JSON responses include:
{
"response_time": "XXXms",
"request_fulfilled": true,
"request_debited": false
}Meaning:
response_time: runtime of the request.request_fulfilled:truewhen HTTP status is less than400.request_debited:trueonly when usage was debited on success.
Why UID Routes Exist
Some products can share the same SKU while still having meaningful differences (for example color variants). In those cases, SKU-based lookups may not be specific enough.
Use product_unique_id from search responses when you need exact product targeting:
- Product lookup by UID:
/api/v2/product/lookup/uid/{product_unique_id} - Image lookup by UID:
/api/image/uid/{product_unique_id}
This gives you a stable way to fetch the exact product details and image for one specific variant.
The V2 routes at a glance
| Route | Answers | Page |
|---|---|---|
/api/v2/barcode/lookup/{barcode} | One barcode -> product and size | Lookup by barcode |
/api/v2/barcode/lookup/sku/{style_code} | One style code -> its barcodes per size | Barcodes by SKU |
/api/v2/product/search | Keywords or a style code -> products | Search products |
/api/v2/product/search/bulk | Many style codes in one call | Search bulk |
/api/v2/product/lookup/sku/{style_code} | One style code -> every variant | Lookup by SKU |
/api/v2/product/lookup/uid/{uid} | One unique ID -> exactly one variant | Lookup by UID |
/api/v2/product/details/{style_code} | Style code -> full record with size run | Product details |
/api/v2/product/latest | Recently added or recently released | Latest products |
/api/v2/product/upcoming | Release dates after today | Upcoming products |
/api/v2/product/alternatives/{style_code} | StockX and GOAT slugs for a product | Product alternatives |
/api/v2/prices/{style_code}, /api/v2/prices/barcode/{barcode} | StockX and Alias resale prices per size | Resale prices |
/api/v2/token/usage | Remaining calls and plan limits, not debited | Token usage |
The V1 routes with prefix /api/v1 stay up for existing integrations; new work should use V2.