Nike APInike.com ↗
Search Nike products, retrieve detailed pricing, sizing, color variants, and availability, plus autocomplete suggestions — all from Nike.com via a single API.
What is the Nike API?
The Nike.com API covers 3 endpoints for querying the Nike product catalog: search by keyword, fetch full product details, and retrieve autocomplete suggestions. The get_product_details endpoint returns over a dozen fields per product including current and original price, size availability status, color variants with image URLs, gender targeting, and a style-color code you can use to look up any individual SKU.
curl -X GET 'https://api.parse.bot/scraper/948eed75-bed5-4b47-9963-56d40cdec23b/search_products?page=1&count=24&query=running+shoes&language=en&marketplace=US' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace nike-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Nike Product Search API — bounded, re-runnable walkthrough."""
from parse_apis.nike_product_search_api import Nike, ProductNotFound
client = Nike()
# Search for running shoes — limit= caps TOTAL items fetched across pages.
for product in client.productsummaries.search(query="running shoes", limit=5):
print(product.title, product.price.current_price, product.color.label)
# Drill-down: take ONE item, then navigate to its full detail via .details().
summary = client.productsummaries.search(query="air max", limit=1).first()
if summary:
detail = summary.details()
print(detail.full_title, detail.color_description)
for size in detail.sizes[:5]:
print(size.label, size.localized_label, size.status)
# Direct product lookup by style-color code.
try:
shoe = client.products.get(style_color="IB1873-110")
print(shoe.title, shoe.product_type)
for benefit in shoe.enhanced_benefits:
print(benefit.header)
except ProductNotFound as exc:
print(f"Product not found: {exc.style_color}")
# Autocomplete suggestions for partial queries.
for suggestion in client.suggestions.search(query="basketball", limit=5):
print(suggestion.display_text, suggestion.search_text)
print("exercised: productsummaries.search / summary.details / products.get / suggestions.search")
Full-text search over Nike's product catalog. Returns paginated product summaries with prices, colors, images, and links. Pagination via page number; each page contains up to `count` items. Only the US marketplace with English language is confirmed working.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number (1-based) |
| count | integer | Products per page. Must be 24, 50, or 100. Other values are rounded to nearest valid option. |
| queryrequired | string | Search keyword (e.g., 'running shoes', 'air max', 'basketball shoes') |
| language | string | Language code. Only 'en' is confirmed working. |
| marketplace | string | Marketplace/country code. Only 'US' is confirmed working. |
{
"type": "object",
"fields": {
"page": "integer - current page number",
"count": "integer - products per page",
"query": "string - the search query used",
"products": "array of product summary objects with product_code, title, subtitle, product_type, price, color, images, url, featured_attributes",
"total_pages": "integer - total number of pages",
"total_results": "integer - total number of matching products"
}
}About the Nike API
Search and Browse Nike Products
The search_products endpoint accepts a query string and returns paginated product listings from Nike.com. You can request 24, 50, or 100 results per page using the count parameter (other values are rounded to the nearest valid option), and navigate results with the page parameter. Each result object includes product_code, title, subtitle, product_type, price, color, a set of images, a direct url, and featured_attributes. The endpoint also returns total_results and total_pages so you can build accurate pagination. Only the US marketplace (marketplace: 'US') with English (language: 'en') is confirmed to work reliably; other combinations may return upstream errors.
Product Details by URL or Style-Color Code
get_product_details accepts either a full Nike product URL via product_url or a style-color code via style_color (for example, HQ2050-101). The response includes a price object with currency, current_price, original_price, and discount_percentage; a sizes array where each entry carries a label, localized_label, and status (so you can tell which sizes are in stock); and an images array keyed by colorway, each with square_url, portrait_url, pdp_url, color_description, and status. Additional fields include description, genders, product_type, and full_title.
Autocomplete Suggestions
The search_suggestions endpoint takes a partial query string and returns a list of suggestion objects, each with a display_text (formatted for display) and a search_text (the raw term to pass back into search_products). An optional count parameter caps the number of suggestions returned. Like the search endpoint, only country: 'US' and language: 'en' are confirmed to work.
The Nike API is a managed, monitored endpoint for nike.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when nike.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official nike.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build a Nike product price tracker using
current_priceandoriginal_pricefromget_product_detailsto monitor discounts over time. - Aggregate size availability across colorways by checking the
statusfield in thesizesarray for a given style-color code. - Power a Nike product search interface with real-time autocomplete using the
search_suggestionsendpoint. - Create a sneaker catalog by crawling search results from
search_productswith theair maxor similar query and storing product metadata. - Compare colorway image assets by iterating the
imagesarray returned byget_product_detailsand pullingportrait_urlorsquare_urlper variant. - Feed affiliate or comparison sites by extracting
url,price, andtitlefields fromsearch_productsresults for specific product queries.
| 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 | 100 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 Nike have an official developer API?+
What does `get_product_details` return that `search_products` does not?+
get_product_details returns granular fields that the search listing omits: a full sizes array with per-size status values, a description string, discount_percentage in the price object, all colorway images with their individual pdp_url and color_description, and the genders array. search_products returns higher-level listing data suited for browsing rather than per-product detail.Does the API cover marketplaces outside the US?+
marketplace parameter on search_products and the country parameter on search_suggestions accept other values (e.g. 'GB'), but these may return upstream errors. You can fork this API on Parse and revise it to target a specific non-US locale if you need consistent international coverage.Does the API expose product reviews or ratings?+
What values are valid for the `count` parameter in `search_products`?+
count used, so you can verify what was applied.