Retail catalog intelligence · REST · OpenAPI 3.1

Retailer catalog data, behind one documented API.

Product rows and coverage across retailers, categories, and departments — three GET endpoints, one filter set, one OpenAPI document. Read the whole reference without an account, then sign in for a token and make your first call in minutes.

Open Explorer Read the quickstart Get an API key

errors you can act on

$ curl "…/v1/catalog?retailer=home_depot&category=power+tool"

HTTP/2 400  application/problem+json
{
  "code": "unknown_category",
  "retryable": false,
  "recovery": "…or use one of the suggested values.",
  "valid_options": ["power_tools", "hand_tools", "tool_storage"]
}

$ curl "…/v1/catalog?retailer=home_depot&category=power_tools"

HTTP/2 200  6 rows · 118 ms

No account

Explorer

Build a request with filters, watch the cURL update, read the response schema. Sign in only to run it live.

OpenAPI 3.1

API reference

Three endpoints, one filter set, generated from the spec. Download it at /openapi.json.

The data

Data dictionary

Every object and field, with per-field coverage published up front — so you design around the gaps.

Built for agents first

An agent can't ask a follow-up question, so nothing here needs one. Every page is real HTML with a .md twin, every error carries retryable and recovery, rate limits ride on every response, and /llms.txt indexes it all.