---
title: "Update Knowledge Entry"
method: PATCH
path: "/api/v1/internal/knowledge/{entry_id}"
tags: ["internal", "internal-knowledge"]
---

# Update Knowledge Entry

`PATCH /api/v1/internal/knowledge/{entry_id}`

Replace any entry's title + content (admin override).

## Path parameters

- `entry_id` string, uuid, required

## Request body

- AdminKnowledgeUpdateRequest — Replace an entry's title + content.
  - `title` string, required
  - `content` string, required

## Response `200`

Successful Response

- KnowledgeEntryResponse — A titled knowledge entry as returned to clients.
  - `id` string, uuid, required
  - `scope` 'user' | 'workspace' | 'project', required — Tier a knowledge entry applies to. Resolution is additive and ordered ``user -> workspace -> project`` — precedence is ordering only, not override (no shadowing in v1). "System" knowledge is the agent's existing system prompt — a separate, pre-existing mechanism that does not live in this table — so there is no ``system`` scope here. Project scope (MAIA-2547) is ambient: paths never name a project; the run's project id scopes reads and writes.
  - `user_id` string, uuid, nullable
  - `workspace_id` string, uuid, nullable
  - `project_id` string, uuid, nullable
  - `title` string, required
  - `content` string, required
  - `created_at` string, date-time, required
  - `updated_at` string, date-time, required
  - `is_core` boolean, required — Whether this is the reserved always-injected core entry (MAIA-2833).

## Other responses

- `422` — Validation Error

---

[API](https://skmtc.net/maia-analytics/apis/maia-api.md) · [All operations](https://skmtc.net/maia-analytics/apis/maia-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/maia-analytics/maia-api/versions/c5094ff58a23/schema)