Status Mutations

Status mutations are scoped to the board associated with the API key and require a write-enabled key. Each mutation returns a Status directly.

Create Status

color is optional. When omitted, the server uses #000000.

mutation CreateStatus($name: String!, $color: String) {
  createStatus(name: $name, color: $color) {
    id
    color
    name
    type
  }
}

Field	Type	Description
name	String!	Name of the custom status
color	String	Display color; defaults to #000000

Update Status

Only id is required. Omit color or name to leave that value unchanged.

mutation UpdateStatus(
  $id: String!
  $color: String
  $name: String
) {
  updateStatus(id: $id, color: $color, name: $name) {
    id
    color
    name
    type
  }
}

Field	Type	Description
id	String!	ID of the custom status to update
color	String	New display color
name	String	New status name

Delete Status

mutation DeleteStatus($id: String!) {
  deleteStatus(id: $id) {
    id
    color
    name
    type
  }
}

Field	Type	Description
id	String!	ID of the custom status to delete

The public API does not expose a status-reordering mutation. Reordering in the Nolt application uses an internal API and is not part of this reference.

Error Handling

The API returns GraphQL errors when the API key is invalid or read-only, the status does not exist, or the status belongs to another board.