---
title: "One component of a status page"
method: GET
path: "/status-pages/{id}/components/{componentId}"
tags: ["Status Pages"]
---

# One component of a status page

`GET /status-pages/{id}/components/{componentId}`

## Request

- Base URL: `https://realuptime.io/api/v1`
- URL: `https://realuptime.io/api/v1/status-pages/{id}/components/{componentId}`
- Auth: HTTP bearer

## Path parameters

- `id` string, uuid, required
- `componentId` string, uuid, required

## Response `200`

The component.

- object
  - `component` object, required
    - `id` string, required
    - `status_page_id` string, required
    - `check_id` string, required
    - `display_name` string, required
    - `description` string, nullable, required
    - `sort_order` number, required
    - `group_id` string, nullable, required

## Other responses

- `401`: Missing, invalid, or revoked API key. - `RU-1001` Missing API credentials: https://realuptime.io/kb/errors/ru-1001 - `RU-1002` Invalid or revoked API key: https://realuptime.io/kb/errors/ru-1002
- `403`: This key is IP-restricted and the request came from outside its allowlist. - `RU-1007` API key is restricted to an IP allowlist: https://realuptime.io/kb/errors/ru-1007
- `404`: No such status page or component on this account. - `RU-5009` Status page or component not found: https://realuptime.io/kb/errors/ru-5009
- `429`: Per-key rate limit exceeded, a Free account's per-account request budget exceeded, or too many failed authentication attempts. - `RU-2002` API read rate limit exceeded: https://realuptime.io/kb/errors/ru-2002 - `RU-2001` Too many failed authentication attempts: https://realuptime.io/kb/errors/ru-2001

---

[API](https://skmtc.dev/realuptime/apis/realuptime-api-v1.md) · [All operations](https://skmtc.dev/realuptime/apis/realuptime-api-v1/llms.txt) · [OpenAPI document](https://skmtc.dev/realuptime/apis/realuptime-api-v1/revisions/51e481084700?raw)