Update work-item dates

Sets or clears start, due, target, sprint, or ordering fields through the schedule command boundary. Jira due-date writeback is supported; custom start/target writeback requires configured Jira field mappings.

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

Authorization

work-items:scheduleapi key scoperequired

Required scope when calling with an API key.

Path parameters

idstringrequired

Canonical work-item ID

Example: work_01k2...

Request body

start_datestringoptional

YYYY-MM-DD or null

due_datestringoptional

YYYY-MM-DD or null

target_datestringoptional

YYYY-MM-DD or null

sprint_idstringoptional

Sprint ID or null

expected_versionnumberoptional

Optimistic work-item version guard

confirmbooleanrequired

Must be true

Example request

{
  "due_date": "2026-07-24",
  "expected_version": 10,
  "confirm": true
}

Request

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

curl -X POST "https://www.digitalstack360.com/api/v1/work-items/work_01k2.../dates" \
  -H "Authorization: Bearer $DS_API_KEY" \
  -H "Idempotency-Key: work-42-due-date-v1" \
  -H "Content-Type: application/json" \
  -d '{"due_date":"2026-07-24","expected_version":10,"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...",
      "due_date": "2026-07-24",
      "version": 11
    },
    "changed_fields": [
      "due_date"
    ]
  }
}

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:schedule scope

400

empty_dates_update

No date or placement fields supplied

409

provider_field_mapping_required

Provider-backed date writeback requires a field mapping