Документация / Как начать / Работа с MCP / Идентификаторы и страницы результатов / REST: site / setSiteEgressOrigins Для AI-агентов: markdown этой страницы — /docs/api-op-setsiteegressorigins.md · индекс документации — /llms.txt
setSiteEgressOrigins Обновлено 15 октября 2026 г.
PUT /api/v1/tools/site/egress-origins
Replace the exact origins form destinations may be sent to
# Авторизация и права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 ["site:write"]
# Параметры запросаПоле Значение 0.description "Tenant, credential and handler-bound byte-shape replay key" 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" 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"] 409.content.application/problem+json.schema ProblemDetails 409.description "Typed domain conflict or request 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; an origin is not an exact https origin of a public DNS host; or a declared form still sends to an origin the set would drop" 422.x-error-codes ["IDEMPOTENCY_KEY_MISMATCH","INVALID_INPUT","FAILED_PRECONDITION"] 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 "Owner-only site:write. The complete set, not a patch: the stored set becomes exactly the listed origins (at most 50), canonicalised (lower case, IDN to punycode, :443 dropped). Each origin is https:// plus a public DNS host, with no other port and no user, wildcard, path, query or fragment. Removing an origin a declared form still sends to is refused; redeclare that form first. site_form_declare refuses a destination whose origin is not in the set. The response is the stored set plus missingOrigins, as for GET. No secret approval gate. Idempotency-Key is optional for PUT." operationId "setSiteEgressOrigins" summary "Replace the exact origins form destinations may be sent to" tags ["site"] 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"