Skip to main content
POST
Delete a work item

Restrictions

Usage

  • Requires the On-call Pro license.
  • Soft delete — the item no longer appears in listings but is retained; its create idempotency_key cannot be reused.
  • Optimistic locking — version must equal the item’s current version; a mismatch returns RequestLocked (HTTP 423). Re-read the item and retry.
  • The caller needs edit access to the item’s anchor: the post-mortem when the item is bound to one, otherwise the incident.
  • A follow_up item can be changed only while its incident is closed.
  • On success data is an empty object.
  • Every call is recorded in the account audit log. Don’t put secrets in request fields.

Authorizations

app_key
string
query
required

APP Key created in the Flashduty console under My → APP Key. Send it as the app_key query parameter or in the Fd-App-Key request header. Its effective access is the intersection of the key's permission scope and the creator's current role permissions. Keep it secret.

Body

application/json

Parameters for soft-deleting a work item.

work_item_id
string
required

Work item ID (opaque string, max 128 characters).

Maximum string length: 128
version
integer<int64>
required

The item's current version (≥ 1) for optimistic locking.

Response

Success

Success response envelope. On every 2xx response, request_id identifies the call (also mirrored in the Flashcat-Request-Id header) and data holds the endpoint-specific payload. Failure responses use a different shape — see ErrorResponse.

request_id
string
required

Unique ID for this request. Mirrored in the Flashcat-Request-Id response header. Include it when reporting issues.

Example:

"01HK8XQE3Z7JM2NTFQ5YJ8P9R4"

data
object

Result of mutating a work item. item is absent for delete.