Update a knowledge base
Change a knowledge base’s name, description, language or type.
PATCH applies only the fields you send. Anything you omit keeps its current value, so send just
what is changing:
kb_type in particular changes how the agent retrieves from
this knowledge base, so include it only when you mean to change it.language is english or multilingual, and
kb_type is deterministic or non_deterministic. Documents are not affected - editing the
knowledge base does not re-run ingestion.Authorizations
Your API key as a Bearer token, e.g. Authorization: Bearer vk_….
Path Parameters
The knowledge base's id, from POST/GET /v1/knowledge-bases.
Body
What to call this knowledge base.
1 - 255Your own note about what is in it.
english or multilingual, matching the content you will upload.
^(english|multilingual)$non_deterministic composes an answer from matching passages; deterministic answers only on a near-exact match and returns the stored text verbatim — which suits pricing, policy and legal copy that must not be paraphrased.
^(deterministic|non_deterministic)$Response
The updated knowledge base.
One knowledge base.
language and kb_type are both growing enums — match on the values you know and fall through on the rest, rather than switching exhaustively.
documents is returned by get-by-id and is null in the list, the same convention as transcript on a call.
The knowledge base's id. List it in an agent's knowledge_base_ids to attach it.
What it is called.
Your own note about what is in it.
The language its content is in.
How answers are produced: non_deterministic composes an answer from matching passages, deterministic answers only on a near-exact match and returns the stored text verbatim — which suits pricing, policy and legal copy that must not be paraphrased.
How many documents it holds.
When it was created (UTC, ISO 8601).
When it last changed (UTC, ISO 8601).
The documents themselves, with their ingestion status.