---
title: "List incident types"
method: GET
path: "/incidents/types"
tags: ["Incident Types"]
---

# List incident types

`GET /incidents/types`

List the available incident types

Incident Types are a feature which will allow customers to categorize incidents, such as a security incident, a major incident, or a fraud incident.
These can be filtered by enabled or disabled types.

For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#incidentType)

Scoped OAuth requires: `incident_types.read`

## Query parameters

- `filter` 'enabled' | 'disabled' | 'all'

## Headers

- `Accept` string, required
- `Content-Type` 'application/json', required

## Response `200`

An array of all types for the account. The default incident type will automatically return on this list.

- object
  - `incident_types` IncidentType[], required
    - `enabled` boolean — State of this Incident Type object.
    - `id` string
    - `name` string — The name of the Incident Type.
    - `parent` object — The parent Incident Type (id/name). If omitted, type is created under top level (incident_default)
      - `id` string
      - `type` string
    - `type` string — A string that determines the schema of the object. This must be the standard name for the entity, suffixed by `_reference` if the object is a reference.
    - `description` string — A succinct description of the Incident Type.
    - `created_at` string, date-time — The time the Incident Type was created.
    - `updated_at` string, date-time — The time the Incident Type was last modified.
    - `display_name` string — The display name of the Incident Type. The first character must be alphanumeric. Max length: 50, Min Length : 1. The `display_name` for a Field must be unique.

## Other responses

- `400` — Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work.
- `401` — Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed.
- `402` — Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account.
- `403` — Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action.
- `404` — The requested resource was not found.
- `500` — Internal Server Error the PagerDuty server experienced an error.

---

[API](https://skmtc.dev/pagerduty/apis/rest-api.md) · [All operations](https://skmtc.dev/pagerduty/apis/rest-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/pagerduty/rest-api/revisions/b679a8f3f02c/schema)