Creating incidents
You can create incidents through the Batida web application, API, or integrations such as Slack and PagerDuty. This page covers the manual creation flow and the API reference.
Creating via the web UI
- Navigate to Incidents in the sidebar.
- Click the New Incident button in the top-right corner.
- Fill in the required fields:
- Title -- a short, descriptive summary of the problem.
- Severity -- choose P1 through P4. When in doubt, start higher and downgrade as you learn more.
- Type -- select the category: technical, security, legal, compliance, PR, or executive.
- Optionally add an initial description and assign a Commander.
- Click Create.
TIP
Use the /incident slash command in Slack to create incidents without leaving your chat. Batida will post a link to the new incident in the channel.
Required fields
| Field | Description | Example |
|---|---|---|
| Title | Concise summary of the disruption | Payment gateway returning 500 errors |
| Severity | Priority level (P1--P4) | P2 |
| Type | Incident category | Technical |
Incident types
Choose the type that best describes the situation:
- Technical -- service outages, degraded performance, infrastructure failures.
- Security -- potential breaches, vulnerabilities, unauthorized access.
- Legal -- legal requests, regulatory notices, compliance obligations.
- Compliance -- policy violations, audit findings, regulatory gaps.
- PR -- public perception issues, social media incidents, press inquiries.
- Executive -- escalated customer issues, VIP escalations, strategic concerns.
API reference
Create an incident
bash
POST /api/v1/incidents
Authorization: Bearer <token>
Content-Type: application/jsonRequest body:
json
{
"title": "Database connection pool exhausted",
"severity": "P2",
"type": "technical",
"description": "Primary DB connections are at 100% capacity. New connections are timing out.",
"commander_id": "usr_abc123"
}Response (201 Created):
json
{
"id": "inc_xyz789",
"title": "Database connection pool exhausted",
"status": "investigating",
"severity": "P2",
"type": "technical",
"commander_id": "usr_abc123",
"created_at": "2026-04-20T14:30:00Z",
"url": "https://app.batida.io/incidents/inc_xyz789"
}Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
title | string | yes | Incident title |
severity | string | yes | P1, P2, P3, or P4 |
type | string | yes | Incident category |
description | string | no | Initial notes |
commander_id | string | no | ID of the Commander |
For information on severity definitions, see Severity levels. For automated incident creation via alerting systems, see Alert webhooks.