---
title: "Get Alert Event"
method: GET
path: "/api/v2/alert-events/{alert_event_id}"
tags: ["Alerts", "Enterprise"]
---

# Get Alert Event

`GET /api/v2/alert-events/{alert_event_id}`

Returns a single alert event by ID.

## Response `200`

OK

- object
  - `data` object
    - `event` ModelAlertEvent — Alert event resource. Events are system-generated source signals that fan out into per-channel delivery attempts. The API exposes events as read-only; they are not mutable through this API surface.
      - `id` string, uuid
      - `type` string — Event type identifier, e.g. an alert kind name.
      - `message` string
      - `data` object — Event payload (`JSONB`); shape varies per event type.
      - `created_at` string, date-time
      - `attempts_queued_at` string, date-time, nullable — Timestamp at which delivery attempts were queued for this event. `null` when the event has not yet been dispatched (matches the `delivered` filter on the list endpoint).

## Other responses

- `400` — **Bad Request** This could be due to one of the following reasons: - JSON payload is missing or malformed - Path or query parameters are missing or invalid/malformed - The data sent is not valid (ex- sending a `string` in an `integer` field)
- `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.
- `404` — **Not Found** This error typically comes from operations where a valid ID was passed to the request to look up an entity but the entity could not be found.
- `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)