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

# incident.io

> Track active incidents, view severity breakdowns, and link security findings to incident response from Tierity.

## Overview

The incident.io integration brings your active incident feed into Tierity's Security Workbench. You can monitor incident severity and status, create new incidents from findings, and link open incidents back to the security work that triggered them — without switching tools.

## Prerequisites

* An incident.io account
* Manage access (or higher) in Tierity

## Setup

**1. Generate an API key**

1. In incident.io, go to **Settings → API keys**.
2. Click **Create API key**, give it a name like "Tierity", and copy the key.

**2. Configure in Tierity**

1. Go to **Config → Integrations → incident.io**.
2. Paste your **API Key**.
3. Click **Save & Test** — Tierity will verify the key by listing your severity levels.

## What's available

Once connected, incident.io appears as a card in your Security Workbench and as a full-page view in the sidebar.

| Feature | Description |
| - | - |
| **Active incidents** | Count of incidents not in a closed state, broken out by severity |
| **Incident list** | Filterable table of incidents with status, severity, and creation time |
| **Incident detail** | Direct link to incident in incident.io for full context and timeline |
| **Create incident** | Push a finding or threat to incident.io as a new incident |

## Workbench card

The incident.io card on your Security Workbench shows:

* The 3 most recently created active incidents with severity and relative time
* Active incident count and total incident count
* A **View all** button that opens the full incident list in a side sheet

## Severity mapping

incident.io uses its own severity scale (configured per workspace). The card and list view display severity names exactly as configured in your incident.io workspace, so they'll match what your team already uses.

## API reference

The integration proxies these incident.io v2 endpoints:

| Tierity route | incident.io endpoint |
| - | - |
| `GET /api/organizations/:id/incidentio/incidents` | `GET /v2/incidents` |
| `GET /api/organizations/:id/incidentio/incidents/:id` | `GET /v2/incidents/:id` |
| `POST /api/organizations/:id/incidentio/incidents` | `POST /v2/incidents` |
| `PATCH /api/organizations/:id/incidentio/incidents/:id` | `PATCH /v2/incidents/:id` |
| `GET /api/organizations/:id/incidentio/severities` | `GET /v2/severities` |


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