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

# Resolve Status Page Incident

> Mark an incident as resolved with a closing message

## Overview

Posts a `resolved` update to the incident timeline, sets the incident status to `resolved` and records the resolution time. It is equivalent to [Add Incident Update](/api-reference/status-pages/add-incident-update) with `status: "resolved"`.

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

## 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. No `X-Project-ID` header is needed.

## Path parameters

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

## Request body

Send a JSON body; an empty object is fine.

| Field | Type | Required | Description |
| - | - | - | - |
| `message` | string | No | Closing message shown on the timeline. Defaults to `This incident has been resolved.` |

## Response

### 200 OK

```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": "resolved",
      "affected_monitor_ids": ["a3f1c2d4-5b6e-4f70-8a91-b2c3d4e5f607"],
      "published_at": "2026-09-30T12:00:00.000Z",
      "updated_at": "2026-09-30T12:40:00.000Z",
      "resolved_at": "2026-09-30T12:40:00.000Z",
      "auto_published": false
    }
  }
}
```

## Errors

| Status | Code | Cause |
| - | - | - |
| 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 or incident does not exist, or the incident belongs to a different status page |

## 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/YOUR_INCIDENT_ID/resolve \
    -H "X-API-Key: YOUR_API_KEY" \
    -H "Content-Type: application/json" \
    -d '{ "message": "The fix is deployed and error rates are back to normal." }'
  ```

  ```javascript JavaScript theme={null}
  const base = 'https://api.uptimeio.com/api/projects/YOUR_PROJECT_ID/status-pages/YOUR_STATUS_PAGE_ID';

  const response = await fetch(`${base}/incidents/YOUR_INCIDENT_ID/resolve`, {
    method: 'POST',
    headers: {
      'X-API-Key': process.env.UPTIMEIO_API_KEY,
      'Content-Type': 'application/json',
    },
    body: JSON.stringify({ message: 'The fix is deployed.' }),
  });

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


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