Skip to main content
PATCH
Update Knowledge Base
Changes state - verify before retry Update a knowledge base. Today this changes its name. The new name must be unique within your workspace.

When to use this

  • Renaming: keep knowledge base names aligned with the product line or customer they cover as those names change on your side.
  • Naming conventions: bring older knowledge bases in line with a naming scheme so pickers stay readable.
Renaming does not affect the agents that reference the knowledge base; they keep working with the same id. A 400 Bad Request means the new name is invalid or already taken. See API errors for the standard error format.
Fetch the same kb_ ID after the update and confirm the name changed. If the request timed out, read the resource before retrying.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

id
string
required

Body

application/json
name
string

Knowledge base name. Must not be blank when provided.

Pattern: \S
Example:

"Updated Product Documentation"

Response

Knowledge base updated successfully.

success
enum<boolean>
required
Available options:
true
error
enum<boolean>
required
Available options:
false
statusCode
integer
required
Example:

200

message
string
required
Example:

"Success"

data
object
required
timestamp
string<date-time>
required