On this page
createOptionGroup
mutation · in the family Option group
What it does
Create a new option group — a dimension like Size or Colour that variants vary by at your organization.
Create an OptionGroup in the caller's org group; requires the unrestricted capability.
Who may call it
Capability area: Catalog structure — Creating and retiring catalog families and whole items.
- Owner
- Manager
- An API key whose scope allows
api:createOptionGroup
Arguments
| Name | Type | Required | Notes |
|---|---|---|---|
input | NewOptionGroupInput NewOptionGroupInput! | yes | No further notes. |
Returns
OptionGroup OptionGroup! — An option group — the PICK-SOURCE for option dimensions (a size run, a brand color palette), typed from the canned registry (color/size drive the spine tier defaults; custom groups feed descriptive attributes that never explode variants). Holds ordered OptionValue children (their parent). NO org selection ever. Referenced BY Style schemes at the spine.
Example request
mutation ExampleCreateOptionGroup($input: NewOptionGroupInput!) {
createOptionGroup(input: $input) {
id
sysId
type
caption
status
parentId
rootId
createdAt
updatedAt
revisionNum
revision
optionGroupType
code
defaultSizeRunId
}
}
Variables:
{
"input": {
"caption": "Blue jeans",
"optionGroupType": "color"
}
}
Send it with the envelope naming the version: "extensions": {"at": {"version": {"name":"genesis","number":0}}}.
Example response
{
"data": {
"createOptionGroup": {
"id": "01900000-0000-7000-8000-37386ae00000",
"sysId": "OP-EXMP-0000-000F",
"type": "OptionGroup",
"caption": "Blue jeans",
"status": "active",
"parentId": "01900000-0000-7000-8000-065235280000",
"rootId": "01900000-0000-7000-8000-a093dd800000",
"createdAt": "2027-01-31T00:00:00.000Z",
"updatedAt": "2027-01-31T00:00:00.000Z",
"revisionNum": 1,
"revision": "01900000-0000-7000-8000-b7960e180000",
"optionGroupType": "color",
"code": "BJ-001",
"defaultSizeRunId": "01900000-0000-7000-8000-c20b3cc50000"
}
},
"extensions": {
"at": {
"callId": "01EXAMPLE-CALL-ID",
"version": {
"requested": {
"name": "genesis",
"number": 0
},
"serviced": {
"name": "genesis",
"number": 0
}
}
}
}
}
Errors this call can answer
VALIDATION/INVALID— Something in the request is not valid. (VALIDATION)AUTHN/REQUIRED— Sign in to do this. (AUTHN)AUTHZ/FORBIDDEN— Your role does not allow this action. (AUTHZ)RATE_LIMIT/THROTTLED— Too many requests in a short time. (RATE_LIMIT)CONFLICT/*— The record’s state, or a change made in the meantime, does not allow this; the codes are on the CONFLICT page. (CONFLICT)VALIDATION/VERSION_REQUIRED— The request did not say which app version it came from. (VALIDATION)
Dry run
Add dryRun: true to the request envelope (extensions.at) to rehearse this call: every check runs, the write is rehearsed against the current records and nothing is stored; the answer is the refusal a real call would give, or the record it would create. Every response to a rehearsal carries dryRun: true, so a rehearsed record is never mistaken for a saved one.