Skip to main content
POST
/
incident
/
post-mortem
/
follow-ups
/
reset
Update post-mortem follow-ups
curl --request POST \
  --url 'https://api.flashcat.cloud/incident/post-mortem/follow-ups/reset?app_key=' \
  --header 'Content-Type: application/json' \
  --data '
{
  "post_mortem_id": "8104935102bf89dc01ac638a5261fe7e",
  "follow_ups": "- Add database saturation alert\n- Review cache TTL rollout"
}
'
{
  "request_id": "01HK8XQE3Z7JM2NTFQ5YJ8P9R4",
  "data": {}
}

​
Restrictions

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

​
Usage

  • Every call is recorded in the account audit log. Don’t put secrets in request fields.

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

Parameters for replacing post-mortem follow-up action items.

​
post_mortem_id
string
required

Post-mortem ID.

​
follow_ups
string

Follow-up action items as free text.

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

Empty response body. The server returns data: null on success.