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

# Create Status Page Incident

> Post an incident announcement to a status page

## Overview

Posts an incident to a status page so visitors and subscribers can follow it. These are communication posts you write yourself; they are separate from the incidents UptimeIO opens automatically for monitors (see the [Incidents API](/api-reference/incidents/introduction)). Posts are created with the status you choose and can then be progressed with [Add Incident Update](/api-reference/status-pages/add-incident-update) and [Resolve Status Page Incident](/api-reference/status-pages/resolve-incident).

`POST /api/projects/{projectId}/status-pages/{statusPageId}/incidents`

## Authentication

| Header | Required | Description |
| - | - | - |
| `X-API-Key` | Yes | Your API key (`Authorization: Bearer {jwt}` also works). API keys need the `read_write` scope. |
| `Content-Type` | Yes | `application/json` |

**Required access:** project admin. Unlike the core status page endpoints, no `X-Project-ID` header is needed.

## Path parameters

| Parameter | Type | Description |
| - | - | - |
| `projectId` | UUID | The project |
| `statusPageId` | UUID | The status page |

## Request body

| Field | Type | Required | Description |
| - | - | - | - |
| `title` | string | Yes | 1-200 characters |
| `message` | string | Yes | 1-5000 characters |
| `severity` | string | Yes | `minor`, `major` or `critical` |
| `status` | string | No | `investigating` (default), `identified`, `monitoring` or `resolved` |
| `affected_monitor_ids` | UUID\[] | Yes | At least one monitor, each already attached to this status page |

## Response

### 201 Created

```json theme={null}
{
  "success": true,
  "data": {
    "incident": {
      "id": "e1f2a3b4-c5d6-4e7f-8a9b-0c1d2e3f4a5b",
      "status_page_id": "0b7c3a52-7d57-4c35-9f0e-5a3b6f1f2a10",
      "incident_id": null,
      "title": "Elevated API error rates",
      "message": "We are investigating elevated error rates on the API.",
      "severity": "major",
      "status": "investigating",
      "affected_monitor_ids": ["a3f1c2d4-5b6e-4f70-8a91-b2c3d4e5f607"],
      "published_at": "2026-09-30T12:00:00.000Z",
      "updated_at": "2026-09-30T12:00:00.000Z",
      "resolved_at": null,
      "auto_published": false
    }
  }
}
```

### The incident object

| Field | Type | Description |
| - | - | - |
| `id` | UUID | Status page incident ID |
| `status_page_id` | UUID | The status page |
| `incident_id` | UUID \| null | The linked monitor incident, for incidents posted automatically. `null` for incidents you create. |
| `title`, `message` | string | Headline and current message |
| `severity` | string | `minor`, `major` or `critical` |
| `status` | string | `investigating`, `identified`, `monitoring` or `resolved` |
| `affected_monitor_ids` | UUID\[] | Monitors the incident affects |
| `published_at` | string | ISO 8601 timestamp the incident was posted |
| `updated_at` | string | ISO 8601 timestamp of the last change |
| `resolved_at` | string \| null | ISO 8601 timestamp when resolved |
| `auto_published` | boolean | `true` when UptimeIO posted it automatically |

## Errors

| Status | Code | Cause |
| - | - | - |
| 400 | `VALIDATION_ERROR` | Invalid body, or a monitor in `affected_monitor_ids` is not attached to this status page. The message names the offending IDs. |
| 401 | `AUTHENTICATION_REQUIRED` | Missing or invalid credentials, or the caller is not a project admin (message `Access denied`) |
| 403 | `API_KEY_ORGANIZATION_MISMATCH` | The API key belongs to a different organization than the project |
| 403 | `READ_ONLY_API_KEY` | The API key has the `read` scope |
| 404 | `RESOURCE_NOT_FOUND` | The status page does not exist in this project |

## Example

<CodeGroup>
  ```bash cURL theme={null}
  curl -X POST https://api.uptimeio.com/api/projects/YOUR_PROJECT_ID/status-pages/YOUR_STATUS_PAGE_ID/incidents \
    -H "X-API-Key: YOUR_API_KEY" \
    -H "Content-Type: application/json" \
    -d '{
      "title": "Elevated API error rates",
      "message": "We are investigating elevated error rates on the API.",
      "severity": "major",
      "affected_monitor_ids": ["YOUR_MONITOR_ID"]
    }'
  ```

  ```javascript JavaScript theme={null}
  const projectId = 'YOUR_PROJECT_ID';
  const statusPageId = 'YOUR_STATUS_PAGE_ID';

  const response = await fetch(
    `https://api.uptimeio.com/api/projects/${projectId}/status-pages/${statusPageId}/incidents`,
    {
      method: 'POST',
      headers: {
        'X-API-Key': process.env.UPTIMEIO_API_KEY,
        'Content-Type': 'application/json',
      },
      body: JSON.stringify({
        title: 'Elevated API error rates',
        message: 'We are investigating elevated error rates on the API.',
        severity: 'major',
        affected_monitor_ids: ['YOUR_MONITOR_ID'],
      }),
    }
  );

  const { data } = await response.json();
  console.log(data.incident.id);
  ```
</CodeGroup>


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