Skip to main content
Menu
Product
Platform overview How it works All features Integrations API Security
Solutions
For suppliers For resellers For sales reps Marketplace
Pricing
Resources
Guides Video tutorials FAQ Sales partners Accessibility
Contact
Sign in
Supplier app Reseller portal Marketplace
Request a demo Start free trial
API Integration

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.

Start Free Trial Request a Demo

How API access works

  1. Issue a scoped key Keys are created per workspace with a label and defined scope — list catalogs, fetch rows — and revoke instantly when retired.
  2. Discover catalogs List the catalogs the key is approved for, with enough metadata to drive an automated pipeline.
  3. Pull product rows Fetch rows with pricing, inventory, image references, and status — reflecting Catalog Rules for the consuming relationship.
  4. Sync on your schedule Poll when it suits your systems; data is generated from the current published catalog, so every pull is fresh.
Scoped API keysCatalog listingProduct rowsHTTPS only

Why teams use it

No file shuffling

Systems consume the catalog directly — the download-then-import loop disappears from the workflow.

Least-privilege keys

Read-scoped keys can list and fetch — nothing else. Compromise exposure is bounded by design, and revocation is instant.

Always-current data

Responses come from the current published catalog with rules applied — there is no stale export layer in between.

Commercial terms intact

API consumers get the same rule-applied view as every other surface — pricing tiers and product restrictions hold in code paths too.

Capabilities

Scoped API keys (per workspace)Key labels, rotation & revocationCatalog listingProduct row accessPricing by roleInventory & restock dataImage referencesDiscontinued statusRule-applied responsesHTTPS-only transport

Good to know

Authentication & security

Requests authenticate with API keys sent over HTTPS. Read-only keys cover catalogs, inventory, prices and your purchase orders; read-write keys can also create, cancel and message on purchase orders. Keys are stored protected and can be revoked at any time.

Errors and limits

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

JSON Catalog Sharing Reseller Portal API & Webhooks

Related written guides

CSV vs JSON vs API vs FTP Product Feeds

Compare CSV, JSON, API, and FTP product-feed methods, understand how each format is delivered, and choose the right catalog workflow for your business.

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?

Not necessarily. Read-only keys cover catalogs, inventory, prices and your purchase orders. Read-write keys add creating, cancelling and messaging on purchase orders. The API documentation is the source of truth for the exact surface.

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.

Start Free Trial Request a Demo