Nordstrom category or brand listing · Nordstrom API

GET https://api.api.sh/nordstrom/v1/category

1 credit / call e-commerce try it in the playground →

Products in a Nordstrom category or brand page, with the site's sort and filters: name, brand, price, regular price, discount, rating, review count, colors, images and link, plus the filters the page offers with the values to send back. Pass next_page back as page; it is null on the last page. Every response includes credits_used: the credits this call cost.

Parameters

name	type	description
`path`required	string	Listing path, for example /browse/women/clothing/dresses or /brands/nike (a nordstrom.com link works too). Example: `/browse/women/clothing/dresses`
`sort`	featured \| newest \| price_asc \| price_desc \| rating \| discount	featured, newest, price_asc, price_desc, rating or discount.
`brand`	string	Brand filter value, as listed in `filters` (for example nike).
`color`	string	Color filter value (for example black).
`price`	string	Price range in dollars (for example 50-100).
`size`	string	Size filter value, as listed in `filters`.
`sale`	string	regular or sale.
`discount`	string	Minimum discount filter value (for example 30.0-*).
`product_type`	string	Product type filter value, as listed in `filters`.
`length`	string	Length filter value (for example mini).
`occasion`	string	Occasion filter value (for example bridal).
`material`	string	Material filter value, as listed in `filters`.
`style`	string	Style filter value, as listed in `filters`.
`fabric`	string	Fabric filter value, as listed in `filters`.
`feature`	string	Feature filter value, as listed in `filters`.
`closure`	string	Closure filter value, as listed in `filters`.
`width`	string	Width filter value, as listed in `filters`.
`gender`	string	Gender filter value: men, women, boys or girls (as listed in `filters`).
`activity`	string	Activity filter value, as listed in `filters` (for example athleisure).
`page`	integer	Page number. Pass `next_page` from the previous response; it is null on the last page.

Every endpoint also takes fresh, raw, fields (see lean responses and caching).

Example

curl "https://api.api.sh/nordstrom/v1/category?path=%2Fbrowse%2Fwomen%2Fclothing%2Fdresses" \
  -H "x-api-key: $APISH_KEY"

import os, requests

res = requests.get(
    "https://api.api.sh/nordstrom/v1/category",
    params={"path": "/browse/women/clothing/dresses"},
    headers={"x-api-key": os.environ["APISH_KEY"]},
    timeout=120,
)
res.raise_for_status()
data = res.json()

const url = new URL("https://api.api.sh/nordstrom/v1/category");
url.searchParams.set("path", "/browse/women/clothing/dresses");

const res = await fetch(url, { headers: { "x-api-key": process.env.APISH_KEY } });
if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);
const data = await res.json();

Response

A JSON object with the fields described above, plus raw (the source's own data), cached, fetched_at and credits_used. Errors return {"success": false, "error": "…"} with the HTTP status (see errors). A lookup that ran but found nothing (404) costs the price above; refused calls and errors on our side are free (what's charged).

The fastest way to see the full response is the playground: it runs this endpoint with your account and shows the exact JSON.