Edit a knowledge case
Rewrite a knowledge case’s title and text at the version you read. Requires knowledge:manage.
v2 compatibility notes
POST /api/v2/knowledge/cases/update rewrites a case’s title and Markdown content, as a person does from the Console. It needs knowledge:manage. The body is { entryId, expectedVersion, title, content, artifactKind? }, with the same bounds as create. expectedVersion is the version from Get a knowledge case: a case that has moved on since answers 409 conflict, and nothing is written.
403). A pending revision’s id, or an entry that is not a keyed case, answers 400. A case synced from a knowledge source answers 409 conflict: edit it in its source. A malformed, missing, deleted, unreadable or source-restricted case answers 404 resource_missing. An edit never marks a case as an External App’s own.
Send an Idempotency-Key to retry safely; see Knowledge curation replay.
A Personal MCP key addressing a Customer case by entryId revalidates the case’s Customer namespace, current Gloo-root authority and credential scopes. Keep the stable case key across SOP versions; use the returned version as expectedVersion. An update does not move the case between namespaces. If an edit is held as pending_review, the live case still contains its prior approved text.Authorizations
Headers
1–255 printable ASCII characters. A repeat with the same key and request never runs the write again, a 5xx included. It returns the first response (Idempotency-Replayed: true) only when the route's current authorization policy permits disclosure; otherwise 409 idempotency_result_unavailable. Honoured for External App JWTs and platform and MCP keys; an External App's static companion key is not protected.
1 - 255Body
A case's new title and Markdown content. expectedVersion is the case version the edit was based on: a case that has moved on answers 409.
Response
What the edit did

