Create incident

Create a manual incident from the dashboard or API.

POST /v1/incidents/chat

Create incident

cURL

curl --request POST \
  --url https://api.example.com/v1/incidents/chat \
  --header 'Content-Type: application/json' \
  --data '
{
  "title": "<string>",
  "description": "<string>"
}
'

Overview

Creates a new incident manually. Manual incidents enter the same AI investigation pipeline as automated alerts — they are triaged, assigned to specialist agents, and processed for root cause analysis.

Required role: admin, owner, or operator

Request body

title · string · required

A short, descriptive title for the incident. This appears in the incident list and notifications.

description · string · required

A detailed description of the incident. Must be between 10 and 4000 characters. Provide as much context as possible — more detail leads to better AI analysis.

Response

Returns 201 Created with the newly created incident.

{
  "incidentId": "inc_01HX9VTPQR3KF8MZWBYD5N6JCE",
  "title": "Checkout service returning 503 for EU customers",
  "severity": "medium",
  "status": "open",
  "source": "manual",
  "investigationsRemaining": 47,
  "eventsRemaining": 312
}

Field	Type	Description
incidentId	string	Unique identifier for the newly created incident
title	string	The incident title
severity	string	Default severity is medium. Triage may update this after classification.
status	string	Always open for newly created incidents
source	string	Always manual for incidents created via this endpoint
investigationsRemaining	integer	Number of investigations remaining on your plan this month
eventsRemaining	integer	Number of events remaining on your plan this month

Error responses

Status	Error code	Description
400	validation_error	title or description is missing or fails validation
429	event_quota_exceeded	Your plan’s monthly event quota has been reached

Manual incidents enter the same investigation pipeline as automated alerts. After creation, use POST /v1/investigation/ to start the AI investigation.

Examples

curl

curl https://api.causeflow.ai/v1/incidents/chat \
  -X POST \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json" \
  -d '{
    "title": "Checkout service returning 503 for EU customers",
    "description": "Since approximately 14:30 UTC, our checkout service has been returning HTTP 503 errors for all requests originating from EU data centers. Logs show connection timeouts to the payment processor gateway. Initial investigation suggests the issue started after the 14:25 UTC deployment of checkout-service v2.4.1."
  }'