Skip to main content

Catalog workflows

Use catalog endpoints to keep products, variations, categories, and vendor profiles aligned with your system of record.
Product creation requires at least one variation. Category and vendor create endpoints accept the fields shown in the API reference.

Before you write data

List capabilities

Confirm which resources and actions your application can use.
cURL

Pick scopes

Add write scopes only for the resources your workflow changes: products.write, categories.write, or vendors.write.

Create supporting records first

Create or look up categories and vendors before creating products that reference them.

Create a product

This example creates a product with one sellable variation.
Response

Product fields to plan for

string
required
Product name shown to operators and integrations.
object[]
required
One or more variations. Each variation can carry pricing, unit, SKU, barcode, tax, and eligibility fields.
boolean
default:"true"
Whether the product should participate in catalog sync behavior.
string[]
Supported values include gluten, dairy, nut, soy, shellfish, egg, wheat, fish, and sesame.

Create a category

Use categories to organize products and build category trees.
cURL

Create a vendor

Vendor profiles support purchasing and catalog workflows that need supplier context.
cURL

Read after write

After creating or updating records, read them back before marking your sync job complete.

Get product

Verify product fields and generated variation IDs.

Category tree

Confirm category hierarchy.

Get vendor

Confirm vendor profile fields.