---
title: "Get component status history"
method: GET
path: "/v1/components/{component_id}/history"
---

# Get component status history

`GET /v1/components/{component_id}/history`

## Request

- Base URL: `https://statusstack.com/api`
- URL: `https://statusstack.com/api/v1/components/{component_id}/history`
- Auth: HTTP bearer

Status history is a change log: each entry is a change of the component's
status (plus a daily reconciliation entry where the recorded status had
drifted), not a periodic sample. A component that held one status for the
whole `from`/`to` range has no entry inside it. Newest `recorded_at` first; always
paginated.

## Query parameters

- `from` string, date
- `to` string, date
- `page` integer
- `per_page` integer

## Response `200`

Component history

- object
  - `data` ComponentHistory[]
    - `id` string, uuid
    - `component_id` string, uuid
    - `status` 'operational' | 'degraded' | 'degraded_performance' | 'partial_outage' | 'major_outage' | 'maintenance' | 'unknown': The status vocabulary every v1 component surface speaks (`App\Support\ComponentWireStatus`), not the stored value. `degraded_performance` is echoed back in its stored spelling; every other degraded state maps to `degraded`. A status the alias table cannot place, or a component never checked, is `unknown` rather than being reported as healthy.
    - `recorded_at` string, date-time: When this status was observed.
    - `created_at` string, date-time: When the entry was written, which can trail `recorded_at`.
  - `links` PaginationLinks
    - `first` string, uri
    - `last` string, uri
    - `prev` string, uri, nullable
    - `next` string, uri, nullable
  - `meta` PaginationMeta: Laravel paginator metadata, present on every paginated v1 list.
    - `current_page` integer
    - `from` integer, nullable
    - `to` integer, nullable
    - `last_page` integer
    - `per_page` integer
    - `total` integer
    - `path` string, uri

## Other responses

- `401`: No bearer credentials, or credentials that do not resolve to an API key or Sanctum token. Produced by `ApiAuthentication` ahead of the route, so every operation in the v1 group can return it.
- `403`: The API key lacks the required permission, or a policy denied the action. The two come from different layers and return different bodies, so this is a union rather than one shape.
- `404`: No such component
- `422`: The request body failed validation, or the write would exceed the organization's quota — `CheckQuota` also answers 422, with its own body.
- `429`: The `v1-api` rate limit (120 requests per minute) was exceeded. Applies to every operation in the v1 group.

---

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