Assign or unassign work item
Assigns, reassigns, or unassigns the canonical work item. Jira-backed work items pass the assignment through to Jira using the configured identity mapping/account id.
POST
/api/v1/work-items/:id/assignmentAuthorization
work-items:assignapi key scoperequiredRequired scope when calling with an API key.
Path parameters
idstringrequiredCanonical work-item ID
Example: work_01k2...
Request body
assignee_user_idstringoptionalDigitalStack user ID, or null to unassign
expected_versionnumberoptionalOptimistic work-item version guard
confirmbooleanrequiredMust be true
Example request
{
"assignee_user_id": "user_jordan",
"expected_version": 9,
"confirm": true
}Request
curl -X POST "https://www.digitalstack360.com/api/v1/work-items/work_01k2.../assignment" \
-H "Authorization: Bearer $DS_API_KEY" \
-H "Idempotency-Key: work-42-assign-jordan-v1" \
-H "Content-Type: application/json" \
-d '{"assignee_user_id":"user_jordan","expected_version":9,"confirm":true}'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...",
"assignee_user_id": "user_jordan",
"version": 10
},
"changed_fields": [
"assignee_user_id"
]
}
}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:assign scope
400
assignee_not_eligibleAssignee is not eligible for the work item team