Update work-item blocker
Updates, resolves, reopens, or transitions one existing blocker.
PATCH
/api/v1/work-items/:id/blockers/:blockerIdAuthorization
work-items:blockersapi key scoperequiredRequired scope when calling with an API key.
Path parameters
idstringrequiredCanonical work-item ID
Example: work_01k2...
blockerIdstringrequiredBlocker ID
Example: blocker_01k7...
Request body
actionstringoptional"update" | "resolve" | "transition"Blocker command
titlestringoptionalReplacement title
severitystringoptionalReplacement severity
statusstringoptionalTarget blocker status
resolutionstringoptionalResolution note
confirmbooleanrequiredMust be true
Example request
{
"action": "resolve",
"resolution": "Credentials received",
"confirm": true
}Request
curl -X PATCH "https://www.digitalstack360.com/api/v1/work-items/work_01k2.../blockers/blocker_01k7..." \
-H "Authorization: Bearer $DS_API_KEY" \
-H "Idempotency-Key: work-42-blocker-update-v1" \
-H "Content-Type: application/json" \
-d '{"action":"resolve","resolution":"Credentials received","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": "resolved",
"resolution": "Credentials received"
},
"changed_fields": [
"blockers"
]
}
}Errors
401
missing_authNo credentials provided
401
invalid_api_keyAPI key is invalid or revoked
400
bad_requestMissing or invalid request fields
403
scope_insufficientKey lacks the required write scope
403
scope_insufficientKey lacks work-items:blockers scope
400
invalid_blocker_transitionRequested blocker status is invalid
404
blocker_not_foundBlocker does not exist or is outside the resolved workspace