---
title: "List the components attached to a stack"
method: GET
path: "/v1/stacks/{stack_id}/components"
tags: ["Stacks"]
---

# List the components attached to a stack

`GET /v1/stacks/{stack_id}/components`

## Request

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

Each component carries its `placement` on the stack, and `status` honours the stack's
active status overrides. A source's catch-all default component is not listed; the
source itself is listed by `/v1/stacks/{stack_id}/sources`.

## Response `200`

Attached components

- object
  - `data` StackComponent[]
    - `id` string, uuid
    - `name` string
    - `description` string, nullable
    - `source_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.
    - `group_name` string, nullable: Name of the component group this component sits in, or null for an ungrouped component. Present when the endpoint loads groups (the `/v1/sources` endpoints do; `affected_components` on incidents does not).
    - `created_at` string, date-time
    - `updated_at` string, date-time
    - `placement` StackComponentPlacement: Where an attached component sits on the stack. Carried on the stack/component pivot.
      - `sort_order` integer
      - `is_critical` boolean
      - `custom_label` string, nullable

## 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 stack, or the addressed source is not attached to it. Unlike the operations that use `StackNotFound`, these controllers authorize through the policy alone without the scope guard, so an existing stack belonging to another team returns 403 here, not a concealed 404.
- `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)
