> ## 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.

# Update a status page incident

> Add a line to an incident that is already published. message is what customers read. Passing status moves the incident to that phase; omitting it, or passing the phase it is already in, posts the note and leaves the phase where it is. That difference is load-bearing: moving an incident to resolved stamps the resolution time customers see and sends the all-clear, so a follow-up note on a resolved incident must not be sent as a phase change. An archived incident is refused: it is off the public page, and the way back is Restore on the status page itself.



## OpenAPI

````yaml /api-reference/openapi.json put /status_page_incidents/{id}
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/{id}:
    put:
      tags:
        - status_page_incidents
      summary: Update a status page incident
      description: >-
        Add a line to an incident that is already published. message is what
        customers read. Passing status moves the incident to that phase;
        omitting it, or passing the phase it is already in, posts the note and
        leaves the phase where it is. That difference is load-bearing: moving an
        incident to resolved stamps the resolution time customers see and sends
        the all-clear, so a follow-up note on a resolved incident must not be
        sent as a phase change. An archived incident is refused: it is off the
        public page, and the way back is Restore on the status page itself.
      operationId: update_status_page_incident
      parameters:
        - description: The resource's id.
          in: path
          name: id
          required: true
          schema:
            type: string
      requestBody:
        content:
          application/json:
            schema:
              properties:
                message:
                  description: >-
                    The line customers read, 1 to 2000 characters. It is added
                    to the timeline under the phase the incident is in after
                    this call.
                  type: string
                status:
                  description: >-
                    The phase to move to: investigating, identified, monitoring,
                    resolved. Omit it to post a note without moving the
                    incident.
                  type: string
              required:
                - message
              type: object
        required: false
      responses:
        '200':
          description: Updated.
        '201':
          description: Created (an upsert resource's PUT on a missing row).
        '404':
          description: No such resource.
        '412':
          description: If-Match named a version of the row that is no longer current.
        '422':
          description: The tool refused the request's shape or content.
        default:
          description: The request failed.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  schemas:
    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.