Nike Category Taxonomy API

Endpoint facts

Method

GET

API path

/nike/categories

Auth

apiKey

Credits

1 credit/request

Platform

Nike

Response schema

#/definitions/nike.categoriesResponseDoc

Overview

Returns Nike's full Men/Women/Kids/Jordan category and subcategory taxonomy tree, sourced directly from Nike.com's own nav mega-menu. Each top-level entry (Men, Women, Kids, Jordan) breaks down into named groups (e.g. Shoes, Clothing, Accessories, Shop By Sport -- Women additionally carries a Shop by Color group, and Jordan is organized by Men/Women/Kids instead of by product type), each with its own subcategory entries. Every subcategory (and most groups) carries a slug usable as a future category-browse endpoint's path/slug input, and is directly browsable today at https://www.nike.com/w/<slug>. This mirrors the live nav exactly, including its seasonal/promotional groups (e.g. Limited Time, New & Featured) alongside the stable structural ones -- Nike's own markup does not distinguish the two. 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

1 credit/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

- The response has one entry per top-level tab, in order: `Men`, `Women`, `Kids`, `Jordan`. - Each top-level entry breaks down into named `groups` (for example `Shoes`, `Clothing`, `Accessories`, `Shop By Sport` -- `Women` additionally carries a `Shop by Color` group, and `Jordan` is organized by `Men`/`Women`/`Kids` instead of by product type). - Each group lists its `subcategories` -- the individual entries a caller would browse (for example `Jordan` under `Men` > `Shoes`, or `Dark Neutrals` under `Women` > `Shop by Color`). - Most groups and subcategories carry a non-empty `slug` -- the bare identifier from Nike's own `/w/<slug>` browse-page URL. `slug` is directly browsable today at `https://www.nike.com/w/<slug>` and is the value a future Nike category-browse endpoint would expect as its `path`/`slug` input. A small number of entries point at a distinct standalone hub page instead of a `/w/` browse page (for example `Shop By Sport`'s own `All Conditions Gear` entry) -- those carry an empty `slug`. - This mirrors the live nav exactly, including its seasonal/promotional groups (`Limited Time`, `New & Featured`, and similar) alongside the stable structural ones -- Nike's own markup does not distinguish the two, so this endpoint does not either. - Two collab/campaign tabs visible in the live nav alongside Men/Women/Kids/Jordan (a NikeSKIMS collection tab and a site-wide Sale tab) are intentionally not included -- they are not part of the stable taxonomy this endpoint documents. ```json {"code":200,"msg":"OK","data":{"source_url":"https://www.nike.com/","fetched_at":"2026-08-10T00:00:00Z","categories":[{"name":"Men","path":"/men","groups":[{"name":"Shoes","path":"/w/mens-shoes-nik1zy7ok","slug":"mens-shoes-nik1zy7ok","subcategories":[{"name":"All Shoes","path":"/w/mens-shoes-nik1zy7ok","slug":"mens-shoes-nik1zy7ok"},{"name":"Jordan","path":"/w/mens-jordan-shoes-37eefznik1zy7ok","slug":"mens-jordan-shoes-37eefznik1zy7ok"}]}]},{"name":"Women","path":"/women","groups":[{"name":"Shop by Color","path":"/w/womens-matching-sets-clothing-2lukpz5e1x6z6ymx6","slug":"womens-matching-sets-clothing-2lukpz5e1x6z6ymx6","subcategories":[{"name":"Dark Neutrals","path":"/w/womens-color-shop-brown-4elb3z5e1x6","slug":"womens-color-shop-brown-4elb3z5e1x6"}]}]},{"name":"Jordan","path":"/jordan","groups":[{"name":"Sport","subcategories":[{"name":"Basketball","path":"/w/jordan-basketball-37eefz3glsm","slug":"jordan-basketball-37eefz3glsm"}]}]}]}} ```

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