--- title: "List Incidents V1" method: GET path: "/v1/incidents" tags: ["Incidents V1"] --- # List Incidents V1 `GET /v1/incidents` List all incidents for an organisation. ## Query parameters - `page_size` integer - `after` string - `status` string[] ## Response `200` OK response. - IncidentsV1ListResponseBody - `incidents` IncidentV1[], required - `call_url` string — The call URL attached to this incident - `created_at` string, date-time, required — When the incident was created - `creator` ActorV1, required - `api_key` APIKeyV1 - `id` string, required — Unique identifier for this API key - `name` string, required — The name of the API key, for the user's reference - `user` UserV1 - `email` string — Email address of the user. - `id` string, required — Unique identifier of the user - `name` string, required — Name of the user - `role` 'viewer' | 'responder' | 'administrator' | 'owner' | 'unset', required — DEPRECATED: Role of the user as of March 9th 2023, this value is no longer updated. - `slack_user_id` string — Slack ID of the user - `custom_field_entries` CustomFieldEntryV1[], required — Custom field entries for this incident - `custom_field` CustomFieldTypeInfoV1, required - `description` string, required — Description of the custom field - `field_type` 'single_select' | 'multi_select' | 'text' | 'link' | 'numeric', required — Type of custom field - `id` string, required — Unique identifier for the custom field - `name` string, required — Human readable name for the custom field - `options` CustomFieldOptionV1[], required — What options are available for this custom field, if this field has options - `custom_field_id` string, required — ID of the custom field this option belongs to - `id` string, required — Unique identifier for the custom field option - `sort_key` integer, required — Sort key used to order the custom field options correctly - `value` string, required — Human readable name for the custom field option - `values` CustomFieldValueV1[], required — List of custom field values set on this entry - `value_catalog_entry` EmbeddedCatalogEntryV1 - `aliases` string[] — Optional aliases that can be used to reference this entry - `external_id` string — An optional alternative ID for this entry, which is ensured to be unique for the type - `id` string, required — ID of this catalog entry - `name` string, required — Name is the human readable name of this entry - `value_link` string — If the custom field type is 'link', this will contain the value assigned. - `value_numeric` string — If the custom field type is 'numeric', this will contain the value assigned. - `value_option` CustomFieldOptionV1 - `custom_field_id` string, required — ID of the custom field this option belongs to - `id` string, required — Unique identifier for the custom field option - `sort_key` integer, required — Sort key used to order the custom field options correctly - `value` string, required — Human readable name for the custom field option - `value_text` string — If the custom field type is 'text', this will contain the value assigned. - `id` string, required — Unique identifier for the incident - `incident_role_assignments` IncidentRoleAssignmentV1[], required — A list of who is assigned to each role for this incident - `assignee` UserV1 - `email` string — Email address of the user. - `id` string, required — Unique identifier of the user - `name` string, required — Name of the user - `role` 'viewer' | 'responder' | 'administrator' | 'owner' | 'unset', required — DEPRECATED: Role of the user as of March 9th 2023, this value is no longer updated. - `slack_user_id` string — Slack ID of the user - `role` IncidentRoleV1, required - `created_at` string, date-time, required — When the role was created - `description` string, required — Describes the purpose of the role - `id` string, required — Unique identifier for the role - `instructions` string, required — Provided to whoever is nominated for the role. Note that this will be empty for the 'reporter' role. - `name` string, required — Human readable name of the incident role - `required` boolean — DEPRECATED: this will always be false. - `role_type` 'lead' | 'reporter' | 'custom', required — Type of incident role - `shortform` string, required — Short human readable name for Slack. Note that this will be empty for the 'reporter' role. - `updated_at` string, date-time, required — When the role was last updated - `incident_type` IncidentTypeV1 - `create_in_triage` 'always' | 'optional', required — Whether incidents of this must always, or can optionally, be created in triage - `created_at` string, date-time, required — When this resource was created - `description` string, required — What is this incident type for? - `id` string, required — Unique identifier for this Incident Type - `is_default` boolean, required — The default Incident Type is used when no other type is explicitly specified - `name` string, required — The name of this Incident Type - `private_incidents_only` boolean, required — Should all incidents created with this Incident Type be private? - `updated_at` string, date-time, required — When this resource was last updated - `mode` 'real' | 'test' | 'tutorial', required — Whether the incident is real, a test, a tutorial, or importing as a retrospective incident - `name` string, required — Explanation of the incident - `permalink` string — A permanent link to the homepage for this incident - `postmortem_document_url` string — Description of the incident - `reference` string, required — Reference to this incident, as displayed across the product - `severity` SeverityV1 - `created_at` string, date-time, required — When the action was created - `description` string, required — Description of the severity - `id` string, required — Unique identifier of the severity - `name` string, required — Human readable name of the severity - `rank` integer, required — Rank to help sort severities (lower numbers are less severe) - `updated_at` string, date-time, required — When the action was last updated - `slack_channel_id` string, required — ID of the Slack channel in the organisation Slack workspace. Note that the channel is sometimes created asynchronously, so may not be present when the incident is just created. - `slack_channel_name` string — Name of the slack channel - `slack_team_id` string, required — ID of the Slack team / workspace. This is only required if you are using a Slack Enterprise Grid with multiple teams. - `status` 'triage' | 'investigating' | 'fixing' | 'monitoring' | 'closed' | 'declined', required — Current status of the incident - `summary` string — Detailed description of the incident - `timestamps` IncidentTimestampV1[] — Incident lifecycle events and when they last occurred - `last_occurred_at` string, date-time — When this last occurred, if it did - `name` string, required — Name of the lifecycle event - `updated_at` string, date-time, required — When the incident was last updated - `visibility` 'public' | 'private', required — Whether the incident should be open to anyone in your Slack workspace (public), or invite-only (private). For more information on Private Incidents see our [help centre](https://help.incident.io/articles/5905558102-can-we-mark-incidents-as-sensitive-and-restrict-access). - `pagination_meta` PaginationMetaResultWithTotal - `after` string — If provided, pass this as the 'after' param to load the next page - `page_size` integer, required — What was the maximum number of results requested - `total_record_count` integer — How many matching records were there in total, if known --- [API](https://skmtc.net/incident/apis/incident-io.md) · [All operations](https://skmtc.net/incident/apis/incident-io/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/incident/incident-io/revisions/602fc25ddd76/schema)