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

# List status page incidents

> What this organization's public status page is telling customers: the unresolved incidents first, then the resolved ones still inside the page's history window, newest first. Each carries its phase, its impact, the components it names and its whole timeline of updates. Archived incidents are left out, as they are on the page.



## OpenAPI

````yaml /api-reference/openapi.json get /status_page_incidents
openapi: 3.1.0
info:
  description: >-
    A resource-shaped endpoint onto the same tool surface the MCP server
    (/api/mcp) reaches. Every gate, refusal and audit row a caller sees here is
    the exact one the MCP endpoint answers for the same tool. Authenticated with
    an API key holding the api:admin scope, or the read-only api:config_read
    scope for GET alone.
  title: SRE Agent configuration API
  version: 1.0.0
servers:
  - url: https://sreagent.app/api/v1/config
security:
  - apiKey: []
tags:
  - name: ai_providers
  - name: ai_settings
  - name: alert_mutes
  - name: alert_routes
  - name: aws_external_id
  - name: certificate_monitors
  - name: change_notifications
  - name: compliance_periods
  - name: connectors
  - name: data_sources
  - name: deploy_policies
  - name: export
  - name: github_settings
  - name: image_targets
  - name: notification_settings
  - name: organization_settings
  - name: outbound_configs
  - name: outbound_rules
  - name: overseer_settings
  - name: prompt_templates
  - name: repo_settings
  - name: service_bindings
  - name: slack
  - name: slis
  - name: slos
  - name: status_page_components
  - name: status_page_incidents
  - name: status_page_settings
  - name: synthetic_checks
  - name: team_members
  - name: teams
  - name: ticket_import_rules
  - name: ticket_integrations
paths:
  /status_page_incidents:
    get:
      tags:
        - status_page_incidents
      summary: List status page incidents
      description: >-
        What this organization's public status page is telling customers: the
        unresolved incidents first, then the resolved ones still inside the
        page's history window, newest first. Each carries its phase, its impact,
        the components it names and its whole timeline of updates. Archived
        incidents are left out, as they are on the page.
      operationId: list_status_page_incidents
      parameters: []
      responses:
        '200':
          content:
            application/json:
              schema:
                properties:
                  data:
                    items:
                      $ref: '#/components/schemas/status_page_incidents_row'
                    type: array
                  organization:
                    type: object
                  truncated:
                    type: boolean
                type: object
          description: The organization's rows.
        default:
          description: The request failed.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  schemas:
    status_page_incidents_row:
      properties:
        archived_at:
          type:
            - string
            - 'null'
        component_ids:
          items:
            type: string
          type:
            - array
            - 'null'
        id:
          type: string
        impact:
          type:
            - string
            - 'null'
        resolved_at:
          type:
            - string
            - 'null'
        scheduled_for:
          type:
            - string
            - 'null'
        scheduled_until:
          type:
            - string
            - 'null'
        started_at:
          type:
            - string
            - 'null'
        status:
          type:
            - string
            - 'null'
        title:
          type: string
        updated_at:
          type: string
        updates:
          type: array
      required:
        - title
        - status
        - impact
        - scheduled_for
        - scheduled_until
        - component_ids
        - archived_at
        - id
        - resolved_at
        - started_at
        - updated_at
        - updates
      type: object
    Error:
      type: object
      description: The body of every failed request.
      properties:
        error:
          type: string
          description: >-
            A short machine-readable code such as forbidden, conflict or
            read_only_key.
        message:
          type: string
          description: A sentence that says what to change.
      required:
        - error
        - message
      additionalProperties: true
  securitySchemes:
    apiKey:
      description: >-
        An sre_ak_* API key holding the api:admin scope (or api:config_read,
        which every write refuses with read_only_key).
      scheme: bearer
      type: http

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.