---
title: "Get SSH Monitor Incident History"
description: "Returns incidents for a single SSH monitor (latest 100), including a computed duration."
---

`GET /api/ssh-monitors/:sshMonitorPublicId/incident-history`

## Authentication

Requires a valid session.

- Header: `Authorization: Bearer <token>`

## Parameters

- `sshMonitorPublicId` (Path, required): SSH monitor public UUID.

## Example (cURL)

```bash
BASE_URL="https://uptimeify.io"
TOKEN="<your-api-token>"

curl -X GET "$BASE_URL/api/ssh-monitors/11111111-1111-4111-8111-111111111111/incident-history" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Accept: application/json"
```

## Example Response

```json
{
  "incidents": [
    {
      "id": 123,
      "type": "downtime",
      "status": "resolved",
      "startedAt": "Feb 26, 2026, 12:10:00",
      "endedAt": "Feb 26, 2026, 12:12:30",
      "duration": "2m 30s"
    }
  ],
  "total": 1
}
```

`type` reflects the failure category for this monitor; `status` is `active` (ongoing) or `resolved`. Ongoing incidents have a `null` `endedAt`.

## Common Errors

- `400 SSH monitor public ID (UUID) required` if `:sshMonitorPublicId` is invalid
- `401 Unauthorized` if you are not authenticated
- `403 Forbidden` if you do not have access to the monitor