Rename or archive a knowledge collection
Rename, re-describe, archive or restore a collection. Sending null for a field is refused rather than treated as clearing it; send an empty string to clear one.
PATCH
Every field is optional, and a field you leave out stays unchanged. A body that contains none of
name, description or archived is refused with 400. Sending null for a field is also refused with 400 rather than clearing it: to clear the description, send "".
Archiving retires a collection without deleting anything. An archived collection refuses new ingestion, and its documents stay searchable, so assistants that already use it keep answering from it. Send "archived": false to restore it. Archiving an archived collection succeeds. There is no endpoint that deletes a collection.
The embedding cannot be changed. A body that includes embedding_model or embedding_dimensions is refused with 400, even when the value matches the current one.
Renaming onto a name your organization already uses returns 409. Updating a collection requires a role that can manage knowledge. A read-only member receives 403. An unknown ID, a malformed ID, or another organization’s collection returns 404.
string
required
Collection ID (a UUID).
string
New display name, at most 200 characters. It is trimmed, and a name that is empty after trimming
is refused.
string
New description. Requests over 4,000 characters are refused. The stored value is trimmed and
truncated to 1,000 characters.
boolean
true to archive the collection, false to restore it.Response
Returns200 with the updated collection.
string
required
Collection ID (a UUID).
string
required
Display name.
string
required
Description.
string
required
active or archived.string
required
Embedding model. Unchanged.
integer
required
Vector width. Unchanged.
string
required
ISO 8601 timestamp, in UTC.
string
required
ISO 8601 timestamp, in UTC.
Last modified on September 26, 2026