Get work-item operation context

Returns the current work-item version, allowed transitions, editable fields, supported commands, and provider writeback posture before applying a command. `transition_vocabulary` says what `flow_state_id` values are — `execute_flow_state` ids for canonical items, or the ticket status string itself for ticket-backed items, which have no flow states. When `allowed_transitions` is empty, `transitions_unavailable_reason` says why, or is null if the empty list is the real answer.

GET/api/v1/work-items/:id/operations/context

Authorization

work-items:readapi key scoperequired

Required scope when calling with an API key.

Path parameters

idstringrequired

Canonical work-item ID

Example: work_01k2...

Request

GET /api/v1/work-items/:id/operations/context

curl -X GET "https://www.digitalstack360.com/api/v1/work-items/work_01k2.../operations/context" \
  -H "Authorization: Bearer $DS_API_KEY"

Examples use a placeholder key from your environment. Store your key in $DS_API_KEY — never commit it.

Response

200 OK

{
  "data": {
    "work_item": {
      "id": "work_01k2...",
      "key": "DSN-42",
      "version": 7
    },
    "version": 7,
    "transition_vocabulary": "execute_flow_state",
    "allowed_transitions": [
      {
        "flow_state_id": "state_doing",
        "name": "In Progress",
        "to_bucket": "in_progress",
        "is_terminal": false
      }
    ],
    "transitions_unavailable_reason": null,
    "editable_fields": [
      "assignee_user_id",
      "labels",
      "points",
      "due_date"
    ],
    "supported_commands": [
      "comment",
      "status",
      "assignment",
      "dates",
      "estimate",
      "labels",
      "dependencies",
      "blockers",
      "focus",
      "bulk"
    ]
  }
}

Errors

401

missing_auth

No credentials provided

401

invalid_api_key

API key is invalid or revoked

403

scope_insufficient

Key lacks work-items:read scope

404

not_found

Work item does not exist or is outside the resolved workspace