Документация / Как начать / Работа с MCP / Идентификаторы и страницы результатов / REST: booking / connectMeetingProvider Для AI-агентов: markdown этой страницы — /docs/api-op-connectmeetingprovider.md · индекс документации — /llms.txt
connectMeetingProvider Обновлено 10 октября 2026 г.
POST /api/v1/booking/meeting-providers/{provider}/connect
connectMeetingProvider
# Авторизация и права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 ["booking:write"]
# Параметры запросаПоле Значение 0.description "Optional: a sent key makes a retry replay the first answer from the 24-hour global cache." 0.in "header" 0.name "Idempotency-Key" 0.required false 0.schema 0.schema 1.in "path" 1.name "provider" 1.required true 1.schema 1.schema
# Тело запросаПоле Значение Тело запроса null
# Ответы# ОшибкиПоле Значение 400.content.application/problem+json.schema ProblemDetails 400.description "Actual body/param/query pipe rejects the request, or global Idempotency-Key is absent" 401.content.application/problem+json.schema ProblemDetails 401.description "Missing, invalid, expired or revoked authentication" 403.content.application/problem+json.schema ProblemDetails 403.description "Required ALL scopes, plan or resource policy refused the caller" 409.content.application/problem+json.schema ProblemDetails 409.description "Control-plane conflict, stale resource/schedule version, invalid schedule cursor or global request already processing" 413.content.application/problem+json.schema ProblemDetails 413.description "Per-tool payload size or item count exceeded" 422.content.application/problem+json.schema ProblemDetails 422.description "MEETING_PROVIDER_UNAVAILABLE: the provider is not enabled on this platform installation; IDEMPOTENCY_KEY_MISMATCH: the key was reused with a different body" 429.content.application/problem+json.schema ProblemDetails 429.description "Per-tool rate limit exceeded or unavailable" 429.headers.Retry-After.description "Resource guard retry delay when supplied by the limiter" 429.headers.Retry-After.schema 429.headers.Retry-After.schema 500.content.application/problem+json.schema ProblemDetails 500.description "Unexpected failure reaches the canonical Problem Details filter"
# Дополнительные условияПоле Значение operationId "connectMeetingProvider" tags ["booking"] x-idempotency "http-cache" x-pagination null