GET /stores/{domain} describes what StoreRouter indexes for one store (retailer). It returns every catalog that serves the domain, with:
- the number of indexed products;
- the search facets populated on those products, with coverage and top values;
- a current-price histogram;
- the store’s assortment profile, when one is published.
stores, or its catalog in catalogs, on POST /products/search.
Stores are distinct from brands. A store sells products; a brand makes them. For brands, see Get brand coverage.
Counts describe the store’s observed, indexed assortment. They are approximate snapshots, not live inventory or the number of products a search would return. Use
POST /products/facet-counts for counts under specific filters./v1 route.
Request
Path parameters
The store’s bare host, such as
thereformation.com. Not a URL. The host is lowercased and a leading www. is removed, so www.TheReformation.com reads the same store. The SDKs also accept a full product URL and extract its host.POST /stores/search.
Response
One entry per catalog serving the domain, sorted by
catalog. Several catalogs can share a domain; that does not make them the same store.Profile distributions
Eachdistributions entry describes one field within the profile’s population:
Profile counts and timestamps belong to the profile’s own generation, which can differ from the coverage snapshot.
Example response
Abbreviated to one field and two price buckets:Caching
Coverage snapshots are cached per catalog for about a day. Responses carry anETag and Cache-Control: private, no-cache. Send the saved ETag in If-None-Match to revalidate; a match returns 304 with no body.
Errors
See the overview for authentication and rate-limit errors.
Operation ID:
getStore. SDK methods: Python get_store(url_or_host); TypeScript getStore(urlOrHost). The CLI command is storerouter stores show <domain|url>. The MCP equivalent is get_store.