Skip to main content
POST
List work items

Restrictions

Usage

  • At least one of incident_id, post_mortem_id, or assignee_id is required.
  • Cursor pagination sorted by updated_at_seconds descending — pass the previous response’s next_cursor as cursor until has_more is false.
  • Listing by incident_id also includes follow-ups anchored on the incident’s post-mortem.
  • Listing by assignee_id alone requires being that assignee or an account admin.

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

Filters for listing work items. At least one of incident_id, post_mortem_id, or assignee_id is required.

incident_id
string

Incident ID (MongoDB ObjectID). Also returns follow-ups anchored on the incident's post-mortem.

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

Post-mortem ID (32-character hex string). Returns follow-ups bound to this post-mortem.

item_type
enum<string>

Filter by work item type: action action item, follow_up post-mortem follow-up.

Available options:
action,
follow_up
assignee_id
integer<int64>

Restrict results to items assigned to this member ID. Listing by assignee alone requires being that assignee or an account admin.

cursor
string

Pagination cursor from a previous response's next_cursor.

limit
integer<int64>
default:50

Page size, at most 200. Defaults to 50.

Required range: 1 <= x <= 200

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

Cursor-paginated list of work items.