Catalog
Products
The product row itself — sku, kind, parent_id, the scoped attribute document, the grid and the batch resolver.
Data model
Attributes, groups, options, families, family attributes, variants and measurement families. The catalog's shape is data, not schema.
Categories
The tree, membership, and rule-driven categories with preview and recompute.
References
Brands, manufacturers and any other domain a product points at by attribute value.
Assets
Asset families and assets, and the three ways an asset binds to bytes.
Associations
Association types and product associations, including quantified relations.
Completeness
Measure a product against what its family requires, and read the field list per family.
Import and export
Profiles, uploads, exports and the bulk-job poll — how catalog data moves in volume.
The catalog is the products app: 16 entities and 92 capability routes, all under https://api.revenexx.com/v1/products — plus the shared io app under /v1/io for bulk import and export.
The one thing to understand first
A product row carries only what every product has: sku, kind, family_id, enabled, tax_class. Everything the merchant modelled — names, descriptions, weights, colours, technical data — lives in a single attribute_values jsonb document, keyed by attribute code.
That means the catalog's shape is data, not schema. Adding a "load capacity in kg" property to a product family is a row in attributes and a row in family_attributes, not a migration. A client that hard-codes column names will not survive a merchant modelling their own catalog; a client that reads GET /v1/products/attribute-schema will.
Routes at a glance
| Area | Base path |
|---|---|
| Products | /v1/products |
| Grid and batch | /v1/products/grid, /v1/products/batch, /v1/products/labels |
| Attributes and families | /v1/products/attributes, /attribute_groups, /attribute_options, /families, /family_attributes, /family_variants, /measurement_families |
| Categories | /v1/products/categories, /v1/products/product_categories |
| References | /v1/products/reference_entities, /reference_entity_records |
| Assets | /v1/products/asset_families, /v1/products/assets |
| Associations | /v1/products/association_types, /v1/products/product_associations |
| Completeness | POST /v1/products/{id}/completeness, GET /v1/products/attribute-schema |
| Vocabularies | GET /v1/products/vocabularies, /vocabularies/{name} |
| Bulk | /v1/io/profiles, /v1/io/uploads, /v1/io/imports, /v1/io/exports, /v1/io/bulk-jobs |
Every one of them is browsable and callable in the API Explorer.
In this group
- Products — the row, the variant hierarchy, the attribute document, the grid.
- Data model — attributes, groups, options, families, variants, measurement families.
- Categories — the tree, membership, rules.
- References — brands, manufacturers and other reference domains.
- Assets — asset families, assets, and where the bytes live.
- Associations — cross-sells, accessories, quantified relations.
- Completeness — how complete is this product, and against what.
- Import and export — profiles, jobs, files.