> For the complete documentation index, see [llms.txt](https://docs.visualsentinel.com/llms.txt)

# IncidentResolveOptions data model

The ways an incident can be closed. Every incident can be resolved. Some kinds also offer a new limit, turning the check off for the site, or pausing the site. An outage never offers stop_alerting, and neither does possible malware.

## Fields

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `incidentId` | string (uuid) | No |   |
| `kind` | string | No | One of: `down`, `slow`, `ssl`, `performance`, `visual`, `content`, `other_address`, `domain`, `security`, `server`, `reported`, `other`. |
| `open` | boolean | No | false once the incident is resolved. A resolved incident still accepts change_limit and stop_alerting. |
| `monitorId` | string or null | No |   |
| `monitorName` | string or null | No |   |
| `actions` | array of string | No | The actions POST accepts for this incident now. Items are one of: `resolve`, `change_limit`, `stop_alerting`, `pause_monitor`. |
| `changeLimit` | null or object | No |   |
| `stopAlerting` | null or object | No |   |
| `pauseMonitor` | null or object | No |   |
| `notOffered` | object | No | Why change_limit or stop_alerting is not offered, when a person might expect it. |
| `notOffered.change_limit` | string | No |   |
| `notOffered.stop_alerting` | string | No |   |

## Used by

- [Ways to resolve an incident](https://docs.visualsentinel.com/reference/incidents.md#get-incident-resolve-options): `GET /api/incidents/{id}/resolve`

Generated from the OpenAPI 3.1 specification at [https://docs.visualsentinel.com/openapi.json](https://docs.visualsentinel.com/openapi.json).