Catalog Product — Create
Equivalent to POST /api/admin/catalog/products.
Step-1 create — mirrors the Bagisto admin Create-Product wizard step 1. Only the bare-minimum fields are accepted at this step; everything else (name, description, price, variants, booking slots, etc.) is added through the Update mutation.
Operation
| Operation | Type |
|---|---|
createAdminCatalogProduct | Mutation |
Input
| Field | Type | Required | Notes |
|---|---|---|---|
sku | String! | yes | Must be unique. |
attributeFamilyId | Int! | yes | Existing family ID. |
type | String! | yes | One of simple, virtual, downloadable, grouped, bundle, configurable, booking. |
superAttributes | Object | conditional | Required when type=configurable — map of attribute code (or id) → non-empty list of option ids. e.g. { "color": [1, 2], "size": [6, 7] }. |
For every type except configurable, the input is just sku + attributeFamilyId + type. Configurable additionally requires superAttributes, from which the store generates the cartesian product of variants.
Notes
- Step-1 only: name, description, price, etc. are added via the Update mutation.
- Booking sub-type (
default/appointment/event/rental/table) and its slots/tickets are set in step 2. - See Update for the per-type structure payloads (variants, bundle options, links, booking slots/tickets).