---
title: "List Alert Events"
method: GET
path: "/v2/alerts"
---

# List Alert Events

`GET /v2/alerts`

## Request

- Base URL: `https://api.traversal.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.traversal.com/v2/alerts`
- Auth: none declared

List alert events with pagination and filtering.

This endpoint returns AlertEvents (one per alert firing) from the new alert system.
Events are ordered by fired_at descending (most recent first).

Args:
    authorized_user: Authorized user with organization context
    start_time: Optional start time filter (ISO 8601 format)
    end_time: Optional end time filter (ISO 8601 format)
    status: Optional filter by derived status
    search_query: Optional full-text search over alert name and description
    page: Page number for pagination (default: 1)
    limit: Number of events per page (default: 50)

Returns:
    ListAlertEventsResponse containing events and pagination metadata

## Query parameters

- `start_time` string, nullable: Start time filter (ISO 8601 with zero offset)
- `end_time` string, nullable: End time filter (ISO 8601 with zero offset)
- `status` 'escalated' | 'anomalous' | 'dismissed': Derived status for an alert event based on escalation and anomaly detection.
- `search_query` string, nullable: Full-text search over alert name and description
- `page` integer: Page number for pagination (default: 1)
- `limit` integer: Number of alerts per page (default: 50, max: 1000)

## Response `200`

Successful Response

- ListAlertEventsResponse: Response model for listing alert events with pagination.
  - `events` AlertEventResponse[], required: List of alert events
    - `id` string, required: Alert event ID
    - `alert_instance_id` string, nullable: Associated alert instance ID
    - `alert_name` string, nullable: Alert name
    - `title` string, required: Alert monitor name, or alert name if monitor name is unavailable
    - `description` string, nullable: Alert description
    - `fired_at` string, date-time, nullable: When the alert fired
    - `severity` string, nullable: Alert severity level
    - `session_id` string, nullable: Associated triage session ID
    - `assistant_chat_id` string, nullable: Chat message ID from which the markdown summary was extracted
    - `source_integration` string, nullable: Source integration
    - `markdown_summary` string: Markdown summary from the investigation's RCA content
    - `status` 'escalated' | 'anomalous' | 'dismissed': Derived status for an alert event based on escalation and anomaly detection.
    - `instance_group_variables` object: Parsed instance group variables (e.g., environment, kube_cluster_name)
    - `alert_instance` AlertInstanceData: Nested alert instance data.
      - `id` string, required: Alert instance ID
      - `instance_hash` string, nullable: Instance hash for grouping events
      - `monitor_id` string, nullable: Monitor ID from source integration
      - `team` string, nullable: Team owning this alert
      - `tags` object, nullable: Tags associated with this alert instance
      - `source_integration` string, nullable: Source integration (e.g., DATADOG)
  - `count` integer, required: Number of events in current page
  - `total` integer, required: Total number of events across all pages
  - `prev_page` integer, nullable: Previous page number
  - `next_page` integer, nullable: Next page number

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/traversal/apis/traversal-api.md) - [All operations](https://skmtc.dev/traversal/apis/traversal-api/llms.txt) - [OpenAPI document](https://skmtc.dev/traversal/apis/traversal-api/revisions/31e1a8b7cf89?raw)