Skip to main content
POST
/
incident
/
feed
Get incident timeline
curl --request POST \
  --url 'https://api.flashcat.cloud/incident/feed?app_key=' \
  --header 'Content-Type: application/json' \
  --data '
{
  "incident_id": "69da451ef77b1b51f40e83ee",
  "p": 1,
  "limit": 20
}
'
{
  "request_id": "01HK8XQE3Z7JM2NTFQ5YJ8P9R4",
  "data": {
    "has_next_page": true,
    "items": [
      {
        "ref_id": "69da451ef77b1b51f40e83ee",
        "type": "i_new",
        "detail": {
          "severity": "Critical",
          "title": "CPU usage high - web-server-01"
        },
        "account_id": 2451002751131,
        "creator_id": 0,
        "created_at": 1775912222661,
        "updated_at": 1775912222661
      },
      {
        "ref_id": "69da451ef77b1b51f40e83ee",
        "type": "i_notify",
        "detail": {
          "rid": "5e9ccfabcd154b41a0005fd0f52b674b",
          "msg_id": "naFudJYCawBWsChdV6ErPH",
          "fire_type": "fire",
          "escalate_rule_id": "000000000000000000000000",
          "layer_idx": 0,
          "by": "email",
          "persons": [
            {
              "person_id": 2476444212131
            }
          ]
        },
        "account_id": 2451002751131,
        "creator_id": 0,
        "created_at": 1775972130174,
        "updated_at": 1775972130174
      }
    ]
  }
}

Documentation Index

Fetch the complete documentation index at: https://docs.flashcat.cloud/llms.txt

Use this file to discover all available pages before exploring further.

​
Restrictions

AspectValue
Rate limits1,000 requests/minute; 50 requests/second per account
PermissionsIncidents Read (on-call)

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 the incident timeline query.

​
incident_id
string
required

Incident ID (MongoDB ObjectID).

Pattern: ^[0-9a-fA-F]{24}$
​
p
integer<int64>

Page number starting at 1.

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

Page size, at most 100.

Required range: 1 <= x <= 100
​
asc
boolean

Ascending chronological order when true.

​
types
enum<string>[]

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_.

TypeMeaning
i_newIncident Created: A new incident was created automatically or manually.
i_assignAssigned: Incident was assigned to responders.
i_a_rspdResponder Added: Additional responders joined the incident.
i_notifyNotification dispatched through a channel at a specific escalation level.
i_stormAlert storm threshold reached on the incident.
i_snoozeNotifications snoozed for a given duration.
i_wakeSnooze cancelled and notifications resumed.
i_ackAcknowledged: Responder confirmed they are working on the incident.
i_unackAcknowledgement removed.
i_commComment: Responder logged progress or key information.
i_rslvResolved: Incident was marked as resolved.
i_reopenReopened: Resolved incident was reopened, possibly due to recurrence.
i_mergeMerged: Multiple related incidents were merged into one.
i_r_titleTitle updated.
i_r_descDescription updated.
i_r_impactImpact updated.
i_r_rcRoot cause updated.
i_r_rsltnResolution updated.
i_r_severitySeverity Changed: Incident severity level was adjusted.
i_r_fieldCustom field value updated.
i_m_flappingIncident muted by flapping detection.
i_m_replyMute reply marker on a comment.
i_customAction: Automated action or script was triggered.
i_wr_createWar Room Created: Chat group was created for collaborative response.
i_wr_deleteWar room chat group deleted.
i_auto_refreshCard auto-refresh event posted back to the timeline.
a_mergeAlert Merged: An alert was merged into an existing incident.
Available options:
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.

​
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

Page of incident timeline entries.