createOrgStyle

mutation · in the family Org style

What it does

Create a new your organization’s enablement of a shared style — selling it locally at your organization.

Create an OrgStyle selection — the per-org ENABLEMENT of a group Style; 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:createOrgStyle

Arguments

Name	Type	Required	Notes
`input`	NewOrgStyleInput `NewOrgStyleInput!`	yes	No further notes.

Returns

OrgStyle OrgStyle! — An OrgStyle selection — the per-org ENABLEMENT of a group Style: selection strictly required before the org ranges/sells it. Parent = the ORGANIZATION (not the family root). NO domain payload (per-org assortment/pricing enrichments arrive additively at their own slices). Freely deactivatable/doomable; a NON-doomed selection blocks the master Style doom only. Creating one is floor-gated: the org must HAVE a defaultCurrency and every non-doomed Product of the style must price it (CONFLICT/CURRENCY_FLOOR, site 1).

Example request

mutation ExampleCreateOrgStyle($input: NewOrgStyleInput!) {
  createOrgStyle(input: $input) {
    id
    sysId
    type
    caption
    status
    parentId
    rootId
    createdAt
    updatedAt
    revisionNum
    revision
    styleId
    code
  }
}

Variables:

{
  "input": {
    "caption": "Blue jeans",
    "organizationId": "01900000-0000-7000-8000-44b781470000",
    "styleId": "01900000-0000-7000-8000-2f797c8b0000"
  }
}

Send it with the envelope naming the version: "extensions": {"at": {"version": {"name":"genesis","number":0}}}.

Example response

{
  "data": {
    "createOrgStyle": {
      "id": "01900000-0000-7000-8000-37386ae00000",
      "sysId": "EY-EXMP-0000-000F",
      "type": "OrgStyle",
      "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",
      "styleId": "01900000-0000-7000-8000-2f797c8b0000",
      "code": "BJ-001"
    }
  },
  "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)
NOT_FOUND/* — That record could not be found. (NOT_FOUND)
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.

Used in

Switch shared catalog entries on for your organization