Explore documentation
  1. Welcome to Telemetry 👋
  2. Quick start guide
  3. Wide events vs. metrics
  4. Ingesting data
    1. Better Stack collector
    2. Vector
    3. OpenTelemetry
    4. Ingesting via HTTP API
    5. Ingesting metrics
    6. Ingesting logs
    7. Migrating to Better Stack
  5. Using the product
    1. AI SRE ↗
    2. MCP server ↗
    3. Transforming ingested data
    4. Querying data
    5. Tracing
    6. Alerts
  6. Telemetry API
    1. Getting an API token
    2. Sources & collectors
    3. Dashboards
    4. Explorations
    5. Alerts API
      1. List all alerts GET
      2. Get a single alert GET
      3. Update an alert PATCH
      4. Remove an alert DELETE
      5. Create a dashboard alert ↗
      6. Create an exploration alert ↗
    6. Connections API
    7. Query API ↗
  7. Alternative to
    1. Lightstep

List all alerts

Returns a paginated list of all alerts accessible by the user, across all dashboards and explorations.

GET https://telemetry.betterstack.com/api/v2/alerts

Query parameters

page
integer

Page number for pagination.

per_page
integer

Number of items per page (max 250).

Headers

Authorization
required string

Bearer $TOKEN

200

A paginated list of all alerts.

Response body

{
  "data": [
    {
      "id": "789",
      "type": "alert",
      "attributes": {
        "dashboard_id": 123,
        "chart_id": 456,
        "name": "High Error Rate Alert",
        "alert_type": "threshold",
        "operator": "higher_than",
        "value": 100.0,
        "paused": false,
        "created_at": "2026-02-20T10:00:00Z",
        "updated_at": "2026-02-23T14:30:00Z"
      }
    },
    {
      "id": "790",
      "type": "alert",
      "attributes": {
        "exploration_id": 789,
        "name": "Anomalous CPU Usage",
        "alert_type": "anomaly_rrcf",
        "paused": false,
        "created_at": "2026-02-21T11:00:00Z",
        "updated_at": "2026-02-22T15:30:00Z"
      }
    }
  ],
  "pagination": {
    "first": "https://telemetry.betterstack.com/api/v2/alerts?page=1&per_page=2",
    "last": "https://telemetry.betterstack.com/api/v2/alerts?page=5&per_page=2",
    "prev": null,
    "next": "https://telemetry.betterstack.com/api/v2/alerts?page=2&per_page=2"
  }
}

Example request

cURL
curl --request GET \
     --url "https://telemetry.betterstack.com/api/v2/alerts" \
     --header "Authorization: Bearer $TOKEN"


Alert context

Each alert in the response includes context attributes to identify its source: - dashboard_id and chart_id for alerts on a dashboard chart. - exploration_id for alerts on an exploration.

The shape of the attributes object varies depending on the alert_type. For example, anomaly_rrcf alerts will include anomaly_sensitivity and anomaly_trigger instead of operator and value.

Previous article

List explorations in a group

Next article

Get a single alert