Документация / Как начать / Работа с MCP / Идентификаторы и страницы результатов / REST: chains / createChainStep Для AI-агентов: markdown этой страницы — /docs/api-op-createchainstep.md · индекс документации — /llms.txt
createChainStep Обновлено 10 октября 2026 г.
POST /api/v1/tools/chains/steps
Add a step with its message to a chain
# Авторизация и права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.required true 0.schema 0.schema
# Тело запроса# Ответы# ОшибкиПоле Значение 400.content.application/problem+json.schema ProblemDetails 400.description "Invalid step, empty content or a chain_seq_num past int4, or missing POST idempotency key" 400.x-error-codes ["VALIDATION_ERROR","IDEMPOTENCY_KEY_REQUIRED"] 401.content.application/problem+json.schema ProblemDetails 401.description "Missing, invalid, revoked or conflicting credentials" 401.x-error-codes ["INVALID_API_KEY"] 403.content.application/problem+json.schema ProblemDetails 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.schema ProblemDetails 404.description "Chain sequence absent in this tenant" 404.x-error-codes ["NOT_FOUND"] 409.content.application/problem+json.schema ProblemDetails 409.description "Same-key command is already processing, or the tenant is archived" 409.x-error-codes ["CONFLICT","TENANT_ARCHIVED"] 413.content.application/problem+json.schema ProblemDetails 413.description "Per-tool resource cap" 413.x-error-codes ["PAYLOAD_TOO_LARGE","ITEM_COUNT_EXCEEDED"] 422.content.application/problem+json.schema ProblemDetails 422.description "Same key reused with a different request" 422.x-error-codes ["IDEMPOTENCY_KEY_MISMATCH"] 429.content.application/problem+json.schema ProblemDetails 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.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 failure; private cause is withheld" 500.x-error-codes ["INTERNAL_ERROR"]
# Дополнительные условияПоле Значение description "The step message is posted through the same content pipeline as POST /api/v1/content/publish; content is required (text and/or mediaRefs from media finalize), title and delay_minutes are optional. The first step of a chain becomes its entry point. stepSeqNum is null when waitTimedOut is true: find the step with GET /api/v1/tools/chains/steps. Configure buttons, timeouts and entry state with PATCH /api/v1/tools/chains/steps." operationId "createChainStep" summary "Add a step with its message to a chain" tags ["chains"] x-idempotency-boundary.conflictStatus 422 x-idempotency-boundary.implementation "generic-v2" x-idempotency-boundary.required true x-idempotency-boundary.scope ["client","credential","controller","handler"] x-idempotency-boundary.ttlSeconds 86400 x-pagination.supported false