Update Knowledge Document
Activates or deactivates a document. Deactivating keeps the document but stops it being attached to new calls. Only completed (READY) documents can be toggled.
Overview
Deactivating keeps the document and its stored file — it simply stops being attached to new calls. Use it to park seasonal or draft material you expect to bring back, instead of deleting and re-uploading. Calls already in progress are unaffected: a document is resolved when a call starts.Example
Pending Documents
Only completed (READY) documents can be toggled. Activating a document whose file never arrived would produce something that lists as usable and fails when a call tries to read it, so it is rejected with a 409 instead.
Error Scenarios
- 404 Not Found: No such document on that agent
- 409 Conflict: The document’s upload has not been completed yet
Related Resources
Authorizations
API key for authentication using Bearer scheme
Path Parameters
Agent the knowledge base belongs to.
Knowledge document id.
Query Parameters
Required for ATS API keys to specify which company to access. Ignored for standard company API keys.
Body
Whether the agent may consult this document during a call. Deactivating keeps the document — it simply stops being attached to new calls.
false
Response
Document updated
Document ID
"123e4567-e89b-12d3-a456-426614174000"
Human-readable label for the document
"Benefits and perks"
PENDING while waiting for the file to be uploaded to the presigned URL and the upload to be completed; READY once the file is confirmed stored. Only READY documents are attached to calls.
PENDING, READY "READY"
Whether the agent may consult this document during a call. Always false while the upload is PENDING.
true
When the document was created
"2026-08-08T10:15:00.000Z"
Original file name as uploaded
"benefits-and-perks.pdf"
MIME type of the stored file
"application/pdf"
Size of the stored file in bytes, as verified against storage. Absent until the upload is READY.
482133