Raise or manage work-item blocker

Raises, updates, resolves, or transitions a blocker linked to a work item.

POST/api/v1/work-items/:id/blockers

Authorization

work-items:blockersapi key scoperequired

Required scope when calling with an API key.

Path parameters

idstringrequired

Canonical work-item ID

Example: work_01k2...

Request body

actionstringoptional"raise" | "update" | "resolve" | "transition"

Blocker command

blocker_idstringoptional

Required for update, resolve, and transition

titlestringoptional

Blocker title

severitystringoptional

Blocker severity

statusstringoptional

Target blocker status

confirmbooleanrequired

Must be true

Example request

{
  "action": "raise",
  "title": "Waiting on customer credentials",
  "severity": "high",
  "confirm": true
}

Request

POST /api/v1/work-items/:id/blockers

curl -X POST "https://www.digitalstack360.com/api/v1/work-items/work_01k2.../blockers" \
  -H "Authorization: Bearer $DS_API_KEY" \
  -H "Idempotency-Key: work-42-blocker-v1" \
  -H "Content-Type: application/json" \
  -d '{"action":"raise","title":"Waiting on customer credentials","severity":"high","confirm":true}'

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

Response

200 OK

{
  "data": {
    "blocker": {
      "id": "blocker_01k7...",
      "status": "open",
      "severity": "high"
    },
    "changed_fields": [
      "blockers"
    ]
  }
}

Errors

401

missing_auth

No credentials provided

401

invalid_api_key

API key is invalid or revoked

400

bad_request

Missing or invalid request fields

403

scope_insufficient

Key lacks the required write scope

403

scope_insufficient

Key lacks work-items:blockers scope

400

blocker_title_required

title is required when raising a blocker

404

blocker_not_found

Blocker does not exist or is outside the resolved workspace