> ## Documentation Index
> Fetch the complete documentation index at: https://docs.scaling.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# List Incident Updates

> Returns every update posted on an incident — both internal and public — in chronological order.

Returns every update posted on an incident — both `internal` and `public` — ordered by `postedAt` ascending. Redacted updates are included with `body` set to `null` and `redactedAt` / `redactedBy` populated; the row is never removed.

## Path parameters

<ParamField path="id" type="string" required>
  The UUID of the incident.
</ParamField>

## Response

<ResponseField name="data" type="object" required>
  <Expandable title="properties" defaultOpen>
    <ResponseField name="updates" type="array of object" required>
      All updates on this incident, oldest first. Each entry has the same shape as the response of [Post Incident Update](./updates-put).
    </ResponseField>
  </Expandable>
</ResponseField>

## Error responses

| Status | Code             | Description                                                |
| ------ | ---------------- | ---------------------------------------------------------- |
| `401`  | `not_authorized` | Missing or invalid credentials.                            |
| `404`  | `not_found`      | No incident with the given ID exists in your organization. |
| `500`  | `server_error`   | An unexpected error occurred on our side.                  |

<RequestExample>
  ```bash List updates theme={null}
  curl --request GET \
    --url "https://api.scaling.cloud/v1/incidents/YOUR_INCIDENT_ID/updates" \
    --header "Authorization: Bearer YOUR_API_KEY"
  ```
</RequestExample>

<ResponseExample>
  ```json 200 theme={null}
  {
    "data": {
      "updates": [
        {
          "id": "0193e1a2-3b4c-7890-aaaa-000000000001",
          "incidentId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
          "body": "We are investigating elevated error rates on the Payments API.",
          "statusChange": null,
          "visibility": "public",
          "postedBy": { "id": "user_2b9a3d4e5f6g7h8j", "name": "Alice Chen" },
          "postedAt": "2025-04-07T08:25:00.000Z",
          "redactedAt": null,
          "redactedBy": null
        },
        {
          "id": "0193e1a2-3b4c-7890-aaaa-000000000002",
          "incidentId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
          "body": "Rolled back deploy v3.14.2. Error rates back to baseline.",
          "statusChange": "resolved",
          "visibility": "public",
          "postedBy": { "id": "user_2b9a3d4e5f6g7h8j", "name": "Alice Chen" },
          "postedAt": "2025-04-07T09:14:00.000Z",
          "redactedAt": null,
          "redactedBy": null
        }
      ]
    }
  }
  ```

  ```json 404 theme={null}
  {
    "statusCode": 404,
    "type": "invalid_request_error",
    "code": "not_found",
    "requestId": "d3e4f5a6-b7c8-9012-defa-bc1234567890"
  }
  ```
</ResponseExample>

<Note>
  This endpoint currently returns every update on the incident in one response. Pagination will be introduced once the volume of updates per incident makes a single response inconvenient. Callers should treat the response as the full set, not a page.
</Note>