Skip to main content
POST
List post-mortems

Restrictions

Usage

  • Account owners and admins see all post-mortems; other members see public ones plus private ones that belong to their own teams.
  • Results are sorted by order_by (default created_at_seconds), descending unless asc is true.
  • Items carry metadata only; fetch the full report with GET /incident/post-mortem/info.

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

Filters for the post-mortem report list.

status
enum<string>

Optional status filter: drafting returns only drafts, published returns only published post-mortems. When omitted, post-mortems in all statuses are returned.

Available options:
drafting,
published
team_ids
integer<int64>[]

Team IDs to restrict the query to.

channel_ids
integer<int64>[]

Channel IDs to restrict the query to.

created_at_start_seconds
integer<int64>

Lower bound of post-mortem creation time (Unix timestamp in seconds).

Required range: x >= 0
created_at_end_seconds
integer<int64>

Upper bound of post-mortem creation time (Unix timestamp in seconds).

Required range: x >= 0
order_by
enum<string>
default:created_at_seconds

Sort field: created_at_seconds creation time, updated_at_seconds last update time.

Available options:
created_at_seconds,
updated_at_seconds
asc
boolean

Ascending order when true.

p
integer<int64>

Page number starting at 1.

Required range: x >= 0
limit
integer<int64>
default:20

Page size, at most 100. With page-number paging, p × limit may not exceed 10,000.

Required range: 0 <= x <= 100
search_after_ctx
string

Cursor from a previous response for forward pagination.

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

Paginated list of post-mortem reports.