updateCategory

mutation · in the family Category

What it does

Edit a category — the product tree’s branches — change its details.

Edit a Category's mutable attributes. Requires the unrestricted capability + the record's CURRENT revision. The merchandise-Division pointer follows the same gates (merchandise-type target) and clears with explicit null; both pointers stay mutually exclusive on the merged record.

Careful

Edits take effect immediately and write a new revision; the old revision stays in history.

Who may call it

Capability area: Catalog editing — Changing what you sell — the details of styles, products, variants and their identifiers.

Owner
Manager
Associate Manager
An API key whose scope allows api:updateCategory

Arguments

Name	Type	Required	Notes
`id`	ID `ID!`	yes	The id of the record.
`revision`	ID `ID!`	yes	The revision id you read on the record; the change is refused if an edit landed in the meantime.
`input`	EditCategoryInput `EditCategoryInput!`	yes	No further notes.

Returns

Category Category! — A category — ONE recursive construct for the whole navigation spectrum (3 flat categories or a 6-level hierarchy; no fixed Department/Subcategory types). inactive = hidden from navigation, still reportable.

Example request

mutation ExampleUpdateCategory($id: ID!, $revision: ID!, $input: EditCategoryInput!) {
  updateCategory(id: $id, revision: $revision, input: $input) {
    id
    sysId
    type
    caption
    status
    parentId
    rootId
    createdAt
    updatedAt
    revisionNum
    revision
    treeParent
    merchandiseDivisionId
    code
  }
}

Variables:

{
  "id": "01900000-0000-7000-8000-37386ae00000",
  "revision": "01900000-0000-7000-8000-b7960e180000",
  "input": {
    "caption": "Blue jeans"
  }
}

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

Example response

{
  "data": {
    "updateCategory": {
      "id": "01900000-0000-7000-8000-37386ae00000",
      "sysId": "CT-EXMP-0000-000F",
      "type": "Category",
      "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",
      "treeParent": "01900000-0000-7000-8000-e095a88d0000",
      "merchandiseDivisionId": "01900000-0000-7000-8000-7ab1ed960000",
      "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.