Actions V1

Manage incident actions.

These endpoints have been deprecated in favour of Actions V2 and Follow-ups V2, as these concepts have become increasingly separate.

Incidents have two types of actions associated to them:

  • Actions, used during an incident response as ephemeral todo lists
  • Follow-ups, actions which are for after the incident and can be exported to external issue trackers

You can manage actions in the incident Slack channel with /incident actions, or on the incident homepage.

Exporting follow-ups to external issue trackers can be done in the incident homepage.

List Actions V1Deprecated

List all actions for an organisation.

Request
query Parameters
incident_id
string

Find actions related to this incident

Example: incident_id=01FCNDV6P870EA6S7TK1DSYDG0
is_follow_up
boolean

Filter to actions marked as being follow up actions

Example: is_follow_up=true
incident_mode
string

Filter to actions from incidents of the given mode. If not set, only actions from real incidents are returned

Enum: "real" "test" "tutorial" Examples:
incident_mode=real
Responses
200

OK response.

get/v1/actions
Request samples 
Response samples 
application/json
{
  • "actions": [
    ]
}
Show Actions V1Deprecated
Get a single incident action.


Request 
path Parameters
id
required
string
Unique identifier for the action


 
 Example:  01FCNDV6P870EA6S7TK1DSYDG0
Responses 
200
OK response.


get/v1/actions/{id}
Request samples 
Response samples 
application/json
{
  • "action": {
    }
}
➔ Next to Actions V2