Skip to main content
GET
Get Incident
string
required
Name of the Issue resource (e.g., payment-service-oom-kill-1773933600). The short INC-YYYYMMDD-NNN id is only the platform.chatcli.io/inc-id label, not the name.
string
Namespace of the incident. When omitted, every namespace is searched and the first incident with that name is returned.
spec and status carry the same incident object (the fields of List Incidents); resourceMeta carries the Kubernetes metadata, including annotations. The AI analysis is not embedded — fetch it with Get AI Insight (<name>-insight).

Authorizations

X-API-Key
string
header
required

API key sent in the X-API-Key header. Keys are read from the Secret chatcli-operator-secrets, key api-keys (fallback: ConfigMap chatcli-operator-config, key api-keys) in the operator namespace, as a YAML list of {key, role, name, description} (name is the identity recorded on approval decisions); the operator chart creates it only with apiKeys.create: true. Roles: viewer < operator < admin — any other role string is denied everywhere. Changes are picked up within about 30 seconds; deleting both the Secret and the ConfigMap revokes every key. With no keys configured every /api/ call returns 401, unless CHATCLI_OPERATOR_DEV_MODE=true, which grants admin without a key (development only).

Path Parameters

name
string
required

Issue name.

Example:

"payment-service-oom-1710860400"

Query Parameters

namespace
string

Namespace of the object. When omitted, all namespaces are searched and the first object with this name is used.

Response

Incident details

apiVersion
string
Example:

"v1"

kind
string
Example:

"Incident"

spec
object
status
object
resourceMeta
object