> ## 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. # Create a status page incident > Publish an incident on the public page. first_update is the opening note customers read, and it is part of the incident rather than a follow-up: every incident the page opens posts one. An incident of major, critical or maintenance impact also emails this organization's own notification recipients, which is the page's rule and not a second one. scheduled_for and scheduled_until describe a maintenance window; both are ISO 8601 timestamps carrying an offset, not the page's local time. ## OpenAPI ````yaml /api-reference/openapi.json post /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: post: tags: - status_page_incidents summary: Create a status page incident description: >- Publish an incident on the public page. first_update is the opening note customers read, and it is part of the incident rather than a follow-up: every incident the page opens posts one. An incident of major, critical or maintenance impact also emails this organization's own notification recipients, which is the page's rule and not a second one. scheduled_for and scheduled_until describe a maintenance window; both are ISO 8601 timestamps carrying an offset, not the page's local time. operationId: create_status_page_incident parameters: [] requestBody: content: application/json: schema: properties: component_ids: description: >- The components this incident affects, which is what the page colours. get_status_page answers the ids. An id this organization does not own, or one that has been archived off the page, refuses the whole call rather than being dropped from the list. items: type: string type: array first_update: description: >- The opening note, 1 to 2000 characters. It becomes the first entry in the timeline, recorded under the phase the incident opens at. type: string impact: description: >- The headline severity the page shows, and what it colours the named components with: none, minor, major, critical, maintenance. Defaults to minor. major, critical and maintenance also email this organization's notification recipients; none and minor are a line on the page and nothing more. maintenance marks planned work rather than a fault. type: string scheduled_for: description: >- When a maintenance window starts, as an ISO 8601 timestamp with an offset (2026-10-01T01:00:00Z). The page's form takes its own configured time zone; this argument does not, so the value is unambiguous whoever sends it. type: string scheduled_until: description: >- When that window ends, same format, and it has to be after scheduled_for. type: string status: description: >- The phase: investigating, identified, monitoring, resolved. Defaults to investigating, which is what the page's form opens on. Opening straight at resolved is allowed and stamps the resolution time. type: string title: description: >- The incident's heading, as customers read it, up to 200 characters. type: string required: - title - first_update type: object required: true responses: '201': description: Created. '409': description: A row already matches this resource's natural key. '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.