Skip to main content
POST
Create a work item

Restrictions

Usage

  • Requires the On-call Pro license.
  • An action anchors to an active incident and must NOT set post_mortem_id; a follow_up REQUIRES the post_mortem_id of a post-mortem linked to incident_id.
  • Assignees must be active members who can already read the anchor incident or post-mortem — assignment never grants access.
  • Newly added assignees are notified.
  • Retrying with the same (creator, idempotency_key) replays the original item with idempotent_replay: true instead of creating a duplicate.
  • Audited — changes are recorded in the audit log.

Authorizations

app_key
string
query
required

App key issued from the Flashduty console under Account → APP Keys. Required on every public API call. Keep it secret — it grants the same access as the owning account.

Body

application/json

Parameters for creating an incident work item.

item_type
enum<string>
required

action anchors to an active incident and must not set post_mortem_id; follow_up requires post_mortem_id.

Available options:
action,
follow_up
title
string
required

Item title (max 512 characters).

Maximum string length: 512
incident_id
string
required

Incident ID (MongoDB ObjectID) the item is anchored to.

Pattern: ^[0-9a-fA-F]{24}$
idempotency_key
string
required

Client-generated idempotency key (max 128 characters; letters, digits, _, -, ., : only).

Maximum string length: 128
Pattern: ^[A-Za-z0-9_\-.:]+$
description
string

Optional longer description (max 65,535 characters).

Maximum string length: 65535
status
string

Optional client-defined initial status (max 64 characters).

Maximum string length: 64
priority
string

Optional client-defined priority (max 64 characters).

Maximum string length: 64
post_mortem_id
string

Post-mortem ID (32-character hex string). Required for follow_up, forbidden for action. The post-mortem must be linked to incident_id.

assignee_ids
integer<int64>[]

Initial assignee member IDs. Assignees must be active members who can already read the anchor; assignment never grants access.

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
required

Result of creating a work item.