Get incident timeline
Retrieve the timeline feed for a specific incident, including state changes, comments and system events.
Restrictions
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 the incident timeline query.
Incident ID (MongoDB ObjectID).
^[0-9a-fA-F]{24}$Page number starting at 1.
x >= 1Page size, at most 100.
1 <= x <= 100Ascending chronological order when true.
Optional filter restricting the returned entries to specific types.
Incident timeline entry type. Each value identifies one lifecycle event; the matching detail payload shape is determined by this field. Incident types are prefixed with i_.
i_new, i_assign, i_a_rspd, i_notify, i_storm, i_snooze, i_wake, i_ack, i_unack, i_comm, i_rslv, i_reopen, i_merge, i_r_title, i_r_desc, i_r_impact, i_r_rc, i_r_rsltn, i_r_severity, i_r_field, i_m_flapping, i_m_reply, i_custom, i_wr_create, i_wr_delete, i_auto_refresh, a_merge 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.