---
title: "List Alert Event Types"
method: GET
path: "/api/v2/alert-event-types"
tags: ["Alerts", "Enterprise"]
---

# List Alert Event Types

`GET /api/v2/alert-event-types`

Returns the list of alert event types registered with the system along with
the payload schema versions supported for each type. The response is not
paginated or filtered.

## Response `200`

OK

- object
  - `data` object
    - `event_types` ModelAlertEventType[]
      - `type` string — Event type identifier. A concrete dotted leaf, e.g. `client.status.offline`; interior segments never carry events.
      - `namespace` string — First segment of the type identifier, e.g. `client`.
      - `category` string, nullable — Second segment of the type identifier, e.g. `error`. `null` for two-segment types such as `client.created`.
      - `name` string — Human-readable name, e.g. `Client Offline`.
      - `description` string
      - `severity` 'info' | 'warning' | 'critical'
      - `versions` object[] — Payload data versions supported for this event type.
        - `data_version` integer — Payload data version. Bare integer; rendering such as `v1` is presentation-only.
        - `data_example` object — Example instance of the event `data` payload for this version. Not a JSON Schema and not the delivery envelope.
        - `created_at` string, date-time
        - `deprecated_at` string, date-time, nullable — Timestamp at which this data version was deprecated. `null` while the version is current. Deprecation does not invalidate existing subscription pins.

## Other responses

- `401` — **Unauthorized** This endpoint failed an authentication requirement. Either the client tried to access a protected endpoint without being authenticated, or an auth validation failed (ex- invalid credentials or expired token).
- `403` — **Forbidden** This is most commonly caused by an authenticated client trying to access a resource that it does not have permission for.
- `429` — **Too Many Requests** The client has sent too many requests within a certain time window and tripped the rate limiting middleware.
- `500` — **Internal Server Error** This is usually the result of either an unexpected database or application error. The client may try modifying or resending the request, but the error is likely not related to the client doing something wrong.

---

[API](https://skmtc.net/specterops/apis/bloodhound-api.md) · [All operations](https://skmtc.net/specterops/apis/bloodhound-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/specterops/bloodhound-api/revisions/e0b866156902/schema)