Catalog data, on demand and in code
Downloads work for people; systems want endpoints. The catalog API gives approved consumers programmatic access to published catalogs — list what's available, pull product rows with pricing, inventory, images, and status, and keep your own systems synced on your own schedule, authenticated with scoped, revocable keys.
How API access works
- Issue a scoped key Keys are created per workspace with a label and defined scope — list catalogs, fetch rows — and revoke instantly when retired.
- Discover catalogs List the catalogs the key is approved for, with enough metadata to drive an automated pipeline.
- Pull product rows Fetch rows with pricing, inventory, image references, and status — reflecting Catalog Rules for the consuming relationship.
- Sync on your schedule Poll when it suits your systems; data is generated from the current published catalog, so every pull is fresh.
Why teams use it
Systems consume the catalog directly — the download-then-import loop disappears from the workflow.
Read-scoped keys can list and fetch — nothing else. Compromise exposure is bounded by design, and revocation is instant.
Responses come from the live published catalog with rules applied — there is no stale export layer in between.
API consumers get the same rule-applied view as every other surface — pricing tiers and product restrictions hold in code paths too.
Capabilities
Good to know
Requests authenticate with API keys sent over HTTPS. Keys are scoped read-only in the current surface, stored protected, and scoped to a single workspace's approved data — the same tenant isolation as the rest of the platform.
Error responses are explicit about what went wrong — bad key, unknown catalog, unauthorized scope — and access patterns are monitored, so integration issues surface as messages rather than mysteries.
Works together with
Common questions
Who can get an API key?
Keys are issued per workspace — vendors for their own data, and resellers for the catalogs they're approved to access, where the vendor's plan supports API delivery.
Is the API read-only?
The current documented surface is read access — listing catalogs and pulling product rows. Anything beyond the documentation isn't claimed; the docs are the source of truth for what a key can do.
What format do responses come in?
Structured JSON with predictable keys — the same clean data model the JSON feed integration describes, delivered per request.
Build one catalog that works everywhere.
Start a 14-day free trial and see it working on your own catalog — onboarding call included.