Документация / Как начать / Работа с MCP / Идентификаторы и страницы результатов / REST: team / updateTeamMember Для AI-агентов: markdown этой страницы — /docs/api-op-updateteammember.md · индекс документации — /llms.txt
updateTeamMember Обновлено 4 октября 2026 г.
PATCH /api/v1/tools/team
Update tenant team member status or permissions
# Авторизация и права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 ["team:write"]
# Параметры запросаПоле Значение 0.description "Tenant, credential and handler-bound replay key; byte-shape request conflict returns 422" 0.in "header" 0.name "Idempotency-Key" 0.required false 0.schema 0.schema
# Тело запроса# Ответы# ОшибкиПоле Значение 400.content.application/problem+json.schema ProblemDetails 400.description "Invalid strict body or sequence" 400.x-error-codes ["VALIDATION_ERROR"] 401.content.application/problem+json.schema ProblemDetails 401.description "Missing, invalid, revoked, expired or conflicting API-key credentials; surface JWT is not accepted" 401.x-error-codes ["INVALID_API_KEY"] 403.content.application/problem+json.schema ProblemDetails 403.description "Missing live owner scope, prohibited publishable key, or OAuth connection without an 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 team member with this sequence in the authenticated tenant" 404.x-error-codes ["NOT_FOUND"] 409.content.application/problem+json.schema ProblemDetails 409.description "Request with the same key is in flight, or a typed domain conflict" 409.x-error-codes ["CONFLICT"] 413.content.application/problem+json.schema ProblemDetails 413.description "Per-tool 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 "Same idempotency key reused with a different request" 422.x-error-codes ["IDEMPOTENCY_KEY_MISMATCH"] 429.content.application/problem+json.schema ProblemDetails 429.description "Per-tool rate limit exceeded or limiter 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 "Owner-only live team:write scope. Addresses a positive int4 seq_num within the authenticated tenant; status and capability flags are optional. Identity fields cannot be updated. Permission/status writes await tenant credential-cache purge before success. Idempotency-Key is optional for PATCH." operationId "updateTeamMember" summary "Update tenant team member status or permissions" tags ["team"] 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