Документация / Как начать / Работа с MCP / Идентификаторы и страницы результатов / REST: catalog / updateCatalogGroup Для AI-агентов: markdown этой страницы — /docs/api-op-updatecataloggroup.md · индекс документации — /llms.txt
updateCatalogGroup Обновлено 10 октября 2026 г.
PATCH /api/v1/tools/catalog-groups/{seqNum}
Update a catalog group
# Авторизация и права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 ["catalog:write"]
# Параметры запросаПоле Значение 0.description "The ETag (the group updated_at, verbatim) returned by the last read or write" 0.in "header" 0.name "If-Match" 0.required true 0.schema 0.schema 1.description "Tenant, credential and handler-bound byte-shape replay key" 1.in "header" 1.name "Idempotency-Key" 1.required false 1.schema 1.schema 2.in "path" 2.name "seqNum" 2.required true 2.schema 2.schema
# Тело запроса# Ответы# ОшибкиПоле Значение 400.content.application/problem+json.schema ProblemDetails 400.description "Invalid address, strict group fields or If-Match timestamp" 400.x-error-codes ["VALIDATION_ERROR"] 401.content.application/problem+json.schema ProblemDetails 401.description "Missing, invalid, revoked or conflicting credential; surface JWT is refused" 401.x-error-codes ["INVALID_API_KEY"] 403.content.application/problem+json.schema ProblemDetails 403.description "Missing scope, prohibited publishable credential or absent active bot" 403.x-error-codes ["INSUFFICIENT_SCOPE","PUBLISHABLE_KEY_NOT_ALLOWED","NO_ACTIVE_BOT"] 404.content.application/problem+json.schema ProblemDetails 404.description "No catalog group with this seq_num for the tenant" 404.x-error-codes ["NOT_FOUND"] 409.content.application/problem+json.schema ProblemDetails 409.description "The group changed since the If-Match version, or a request with this replay key is in flight" 409.x-error-codes ["CONFLICT"] 413.content.application/problem+json.schema ProblemDetails 413.description "Resource policy size or item-count limit exceeded" 413.x-error-codes ["PAYLOAD_TOO_LARGE","ITEM_COUNT_EXCEEDED"] 422.content.application/problem+json.schema ProblemDetails 422.description "Replay key reused for different input" 422.x-error-codes ["IDEMPOTENCY_KEY_MISMATCH"] 428.content.application/problem+json.schema ProblemDetails 428.description "If-Match header is required" 428.x-error-codes ["PRECONDITION_REQUIRED"] 429.content.application/problem+json.schema ProblemDetails 429.description "Resource rate budget exceeded or unavailable" 429.headers.Retry-After.description "Retry delay in seconds, when supplied by the limiter" 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 "catalog:write. Partial update by tenant seq_num. If-Match takes the ETag of the last GET, POST or PATCH of this group, which is its updated_at (ISO timestamp) sent verbatim; a group changed since then answers 409 STALE_VERSION. The response carries the new ETag. Idempotency-Key is optional for PATCH." operationId "updateCatalogGroup" summary "Update a catalog group" tags ["catalog"] x-idempotency.conflictStatus 422 x-idempotency.implementation "global-cache" x-idempotency.replayStatus 200 x-idempotency.required false x-idempotency.scope ["client","credential","controller-handler","key"] x-idempotency.ttlSeconds 86400 x-pagination.queryParameters [] x-pagination.supported false x-scope-semantics "ALL"