К содержанию
TelegaFirst

Для AI-агентов: markdown этой страницы — /docs/api-op-updatemessagechain.mdиндекс документации — /llms.txt

updateMessageChain

Обновлено

PATCH /api/v1/tools/chains

Update a chain shell by 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["chains:write"]

Параметры запроса

ПолеЗначение
0.in"header"
0.name"Idempotency-Key"
0.requiredfalse
0.schema0.schema

Тело запроса

ПолеЗначение
content.application/json.schemaMessageChainUpdateRequest
requiredtrue

Ответы

ПолеЗначение
200.content.application/json.schemaMessageChain
200.description"Updated chain projection"
200.headers.X-Bot-Username.description"Active public bot username when present"
200.headers.X-Bot-Username.schema200.headers.X-Bot-Username.schema
200.headers.X-Client-Slug.description"Active tenant slug when present in authenticated metadata"
200.headers.X-Client-Slug.schema200.headers.X-Client-Slug.schema
200.headers.X-RateLimit-Limit.description"Effective request budget"
200.headers.X-RateLimit-Limit.schema200.headers.X-RateLimit-Limit.schema
200.headers.X-RateLimit-Remaining.description"Remaining budget, or unknown"
200.headers.X-RateLimit-Remaining.schema200.headers.X-RateLimit-Remaining.schema
200.headers.X-RateLimit-Reset.description"Window reset epoch seconds"
200.headers.X-RateLimit-Reset.schema200.headers.X-RateLimit-Reset.schema

Ошибки

ПолеЗначение
400.content.application/problem+json.schemaProblemDetails
400.description"Invalid body"
400.x-error-codes["VALIDATION_ERROR"]
401.content.application/problem+json.schemaProblemDetails
401.description"Missing, invalid, revoked or conflicting credentials"
401.x-error-codes["INVALID_API_KEY"]
403.content.application/problem+json.schemaProblemDetails
403.description"Missing scope, publishable key or no active tenant"
403.x-error-codes["INSUFFICIENT_SCOPE","PUBLISHABLE_KEY_NOT_ALLOWED","NO_ACTIVE_BOT"]
404.content.application/problem+json.schemaProblemDetails
404.description"Chain sequence absent in this tenant"
404.x-error-codes["NOT_FOUND"]
409.content.application/problem+json.schemaProblemDetails
409.description"Same-key command is already processing"
409.x-error-codes["CONFLICT"]
413.content.application/problem+json.schemaProblemDetails
413.description"Per-tool resource cap"
413.x-error-codes["PAYLOAD_TOO_LARGE","ITEM_COUNT_EXCEEDED"]
422.content.application/problem+json.schemaProblemDetails
422.description"Same key reused with a different request"
422.x-error-codes["IDEMPOTENCY_KEY_MISMATCH"]
429.content.application/problem+json.schemaProblemDetails
429.description"Per-tool quota exceeded or unavailable (fail closed)"
429.headers.Retry-After.description"Retry delay when supplied by resource decision"
429.headers.Retry-After.schema429.headers.Retry-After.schema
429.x-error-codes["RATE_LIMIT_EXCEEDED","RATE_LIMIT_UNAVAILABLE"]
500.content.application/problem+json.schemaProblemDetails
500.description"Unexpected failure; private cause is withheld"
500.x-error-codes["INTERNAL_ERROR"]

Дополнительные условия

ПолеЗначение
operationId"updateMessageChain"
summary"Update a chain shell by tenant sequence"
tags["chains"]
x-idempotency-boundary.conflictStatus422
x-idempotency-boundary.implementation"generic-v2"
x-idempotency-boundary.requiredfalse
x-idempotency-boundary.scope["client","credential","controller","handler"]
x-idempotency-boundary.ttlSeconds86400
x-pagination.supportedfalse