Skip to main content
GET
Get Approval
string
required
Approval request name (e.g., approval-payment-service-oom-kill-1773933600-plan-1)
string
Kubernetes namespace. When omitted, every namespace is searched and the first request with that name is returned.
spec and status carry the same flat approval item described in List Approvals; resourceMeta carries the Kubernetes metadata. The item includes requiredApprovers and the recorded decisions. The item also carries the request’s annotations, where the blast radius prediction lives (platform.chatcli.io/blast-radius, platform.chatcli.io/blast-risk-level). The AI evidence and timeoutMinutes are not exposed here — use kubectl get approvalrequest <name> -o yaml.

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

ApprovalRequest name.

Example:

"payment-oom-plan-1-approval"

Query Parameters

namespace
string

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

Response

Approval details

apiVersion
string
Example:

"v1"

kind
string
Example:

"ApprovalRequest"

spec
object
status
object

The same approval object as spec.

resourceMeta
object