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 API
    3. Source groups API
    4. Metrics API
    5. Dashboards API
    6. Explorations API
    7. Exploration groups API
    8. Alerts API
      1. List alerts in exploration GET
      2. Get a single alert GET
      3. Create an alert POST
      4. Update an alert PATCH
      5. Remove an alert DELETE
    9. Connections API
    10. Collectors API
    11. Query API ↗
  7. Alternative to
    1. Lightstep

Get a single alert

Retrieves a single alert by its ID, scoped to a specific exploration.

GET https://telemetry.betterstack.com/api/v2/explorations/{exploration_id}/alerts/{id}

URL parameters

exploration_id
required integer

The unique identifier of the exploration.

id
required integer

The unique identifier of the alert.

Headers

Authorization
required string

Bearer $TOKEN

200

The details of the specified alert.

Response body

{
  "data": {
    "id": 789,
    "type": "alert",
    "attributes": {
      "name": "High Error Rate Alert",
      "alert_type": "threshold",
      "operator": "higher_than",
      "value": 100.0,
      "string_value": null,
      "query_period": 300,
      "confirmation_period": 0,
      "recovery_period": 300,
      "aggregation_interval": 60,
      "check_period": 60,
      "series_names": [
        "error"
      ],
      "source_variable": "source",
      "source_mode": "source_variable",
      "source_platforms": [],
      "incident_cause": "Error rate exceeded threshold",
      "incident_per_series": false,
      "escalation_target": {
        "policy_id": 123,
        "policy_name": "Critical Alerts Policy"
      },
      "metadata": {
        "environment": "production",
        "runbook": "https://wiki.example.com/runbooks/error-rate"
      },
      "paused": false,
      "paused_reason": null,
      "created_at": "2026-02-20T10:00:00Z",
      "updated_at": "2026-02-23T14:30:00Z"
    }
  }
}
404

The specified exploration or alert was not found.

Example request

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


The fields returned in the response depend on the alert_type and escalation_target. - operator, value, string_value, and check_period are only returned for threshold and relative alerts. - anomaly_sensitivity and anomaly_trigger are only returned for anomaly_rrcf alerts. - Notification channels (call, sms, etc.) are omitted if the escalation_target is a policy.

Previous article

List alerts in exploration

Next article

Create an alert