List work items
List incident work items (actions and post-mortem follow-ups) with cursor pagination.
Restrictions
Usage
- At least one of
incident_id,post_mortem_id, orassignee_idis required. - Cursor pagination sorted by
updated_at_secondsdescending — pass the previous response’snext_cursorascursoruntilhas_moreis false. - Listing by
incident_idalso includes follow-ups anchored on the incident’s post-mortem. - Listing by
assignee_idalone requires being that assignee or an account admin.
Authorizations
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
Filters for listing work items. At least one of incident_id, post_mortem_id, or assignee_id is required.
Incident ID (MongoDB ObjectID). Also returns follow-ups anchored on the incident's post-mortem.
^[0-9a-fA-F]{24}$Post-mortem ID (32-character hex string). Returns follow-ups bound to this post-mortem.
Filter by work item type: action action item, follow_up post-mortem follow-up.
action, follow_up Restrict results to items assigned to this member ID. Listing by assignee alone requires being that assignee or an account admin.
Pagination cursor from a previous response's next_cursor.
Page size, at most 200. Defaults to 50.
1 <= x <= 200Response
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.