Документация / Как начать / Работа с MCP / Идентификаторы и страницы результатов / REST: kb / updateKnowledge Для AI-агентов: markdown этой страницы — /docs/api-op-updateknowledge.md · индекс документации — /llms.txt
updateKnowledge Обновлено 10 октября 2026 г.
PATCH /api/v1/tools/kb
Edit tenant knowledge by board and tenant sequence
# Авторизация и праваScopes: ALL. Auth alternatives: OR; scopes внутри альтернативы: ALL.
Поле Значение security.0.hubApiKey [] security.1.hubBearer [] securitySchemes.hubApiKey.in "header" securitySchemes.hubApiKey.name "X-Api-Key" securitySchemes.hubApiKey.type "apiKey" securitySchemes.hubBearer.scheme "bearer" securitySchemes.hubBearer.type "http" x-required-scopes ["kb:write"]
# Параметры запросаПоле Значение 0.description "Replay the same tenant, credential, route and request for 24 hours." 0.in "header" 0.name "Idempotency-Key" 0.required false 0.schema 0.schema
# Тело запроса# Ответы# ОшибкиПоле Значение 400.content.application/problem+json.schema ProblemDetails 400.description "Strict request validation failed." 400.x-error-codes ["VALIDATION_ERROR"] 401.content.application/problem+json.schema ProblemDetails 401.description "Missing, invalid, revoked or expired API credential. Surface-session JWTs are not accepted." 401.x-error-codes ["INVALID_API_KEY"] 403.content.application/problem+json.schema ProblemDetails 403.description "Missing effective scope, forbidden publishable key, inaccessible tenant or no active bot." 403.x-error-codes ["INSUFFICIENT_SCOPE","PUBLISHABLE_KEY_NOT_ALLOWED","FORBIDDEN","NO_ACTIVE_BOT"] 404.content.application/problem+json.schema ProblemDetails 404.description "No live knowledge entry with this tenant, board and sequence." 404.x-error-codes ["NOT_FOUND"] 409.content.application/problem+json.schema ProblemDetails 409.description "The entry changed while it was being written, or a request with this key is still processing." 409.x-error-codes ["CONFLICT"] 413.content.application/problem+json.schema ProblemDetails 413.description "Per-tool payload size or item-count limit exceeded before validation." 413.x-error-codes ["PAYLOAD_TOO_LARGE","ITEM_COUNT_EXCEEDED"] 422.content.application/problem+json.schema ProblemDetails 422.description "Idempotency-Key reused with different inputs." 422.x-error-codes ["IDEMPOTENCY_KEY_MISMATCH"] 429.content.application/problem+json.schema ProblemDetails 429.description "Per-tool rate limit exceeded or unavailable; fail closed." 429.headers.Retry-After.required false 429.headers.Retry-After.schema 429.headers.Retry-After.schema 429.x-error-codes ["RATE_LIMIT_EXCEEDED","RATE_LIMIT_UNAVAILABLE"] 500.content.application/problem+json.schema ProblemDetails 500.description "Unexpected internal failure." 500.x-error-codes ["INTERNAL_ERROR"]
# Дополнительные условияПоле Значение description "kb_type plus numeric positive-int4 seq_num (1–2147483647) addresses the entry inside the authenticated tenant. patch carries at least one of title (1–200), content (1–4000), tags, prepared_step_seq_nums ([] clears binding), is_active, is_public. A text change or switching the entry back on queues re-indexing and returns status indexing; switching it off takes it out of the agent search and returns status pending with null graph statistics. Idempotency-Key is optional on PATCH. 409 CONFLICT means the entry changed while it was being written (for example the indexer finished): read it again and retry. No If-Match or ETag contract." operationId "updateKnowledge" summary "Edit tenant knowledge by board and tenant sequence" tags ["kb"] x-idempotency.mismatchStatus 422 x-idempotency.required false x-idempotency.ttlSeconds 86400 x-pagination.kind "none"