---
title: "List alarm trigger history"
method: GET
path: "/projects/{project_id}/alarms/{alarm_id}/history"
tags: ["Alarms"]
---

# List alarm trigger history

`GET /projects/{project_id}/alarms/{alarm_id}/history`

## Request

- Base URL: `https://app.honeybadger.io/v3`
- URL: `https://app.honeybadger.io/v3/projects/{project_id}/alarms/{alarm_id}/history`
- Auth: HTTP bearer
- TypeScript: <https://skmtc.dev/honeybadger/apis/honeybadger-api/docs/projects/:project_id/alarms/:alarm_id/history/get.ts> (a function with typed inputs; its response is checked against the schema)

Returns an alarm's trigger history, newest first, 25 per page.

## Path parameters

- `project_id` string, required
- `alarm_id` string, required

## Query parameters

- `page` integer

## Response `200`

Success

- object
  - `data` AlarmHistoryEntry[], required
    - `id` string, required
    - `alarm_id` string, required: The alarm's ID
    - `alarm_version_id` string, required: The version of the alarm that was evaluated. Editing an alarm creates a new version, and history spans every version.
    - `status` 'alarm' | 'ok' | 'null', nullable, required: The state the alarm entered
    - `created_at` string, date-time, required: When the change was recorded
    - `evaluation_started_at` string, date-time, required: Start of the window whose evaluation caused the change
    - `evaluation_result` number, double, nullable, required: The value the trigger compared against its threshold
  - `pagination` Pagination: Offset-based pagination information
    - `page` integer, required: Current page number
    - `per_page` integer, required: Items per page
  - `links` OffsetLinks: Navigation links for a numbered-page collection. Each link is a root-relative path (`/v3/...`); resolve it against the API host.
    - `self` string, uri-reference, required: This page
    - `first` string, uri-reference: First page
    - `prev` string, nullable: Previous page, or null on the first page
    - `next` string, nullable: Next page, or null on the last page
  - `meta` ResponseMeta
    - `request_id` string: Unique identifier for the request, for correlating with support

## Other responses

- `401`: The credential is missing, invalid, expired or revoked (`unauthorized`), or was sent in a way v3 doesn't accept (see the examples).
- `403`: The credential isn't allowed to do this. `error.code` says why. An account or project the credential doesn't cover is 404 `not_found`, not 403.
- `404`: Resource not found
- `422`: No path names the account, so the API token has to. This is returned when the token covers more than one account and the account a request applies to cannot be determined. Use a token bound to a single account.
- `503`: Alarms are temporarily unavailable. Retry later.

---

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