Skip to main content
POST
Bind work items to a post-mortem

Restrictions

Usage

  • Requires the On-call Pro license.
  • Binds every item of the incident that was converted from an action and is not yet bound to any post-mortem.
  • The caller needs edit access to the post-mortem, and incident_id must be linked to it.
  • items holds the items bound by this call and may be empty; next_cursor is not set and has_more is false.
  • Retrying with the same idempotency_key returns the items bound earlier with idempotent_replay: true.
  • 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 bulk-binding an incident's unbound follow-ups to a post-mortem.

post_mortem_id
string
required

Post-mortem ID (32-character hex string) to bind the follow-ups to.

incident_id
string
required

Incident ID (MongoDB ObjectID) whose converted, unbound items are bound. It must be linked to post_mortem_id.

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_\-.:]+$

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

Cursor-paginated list of work items.