---
title: "Choose whether this deployment dials its own outbound calls"
method: PATCH
path: "/v1/gateway-deployments/{gateway_id}/outbound-execution-mode"
---

# Choose whether this deployment dials its own outbound calls

`PATCH /v1/gateway-deployments/{gateway_id}/outbound-execution-mode`

## Request

- Base URL: `https://api.skysay.ai`
- URL: `https://api.skysay.ai/v1/gateway-deployments/{gateway_id}/outbound-execution-mode`
- Auth: none declared

Sets outbound_execution_mode to 'queue' (the default: admission enqueues a call.outbound_originate job an organization-scoped worker claims) or 'local' (the deployment asks for admission and dials itself, so no organization-scoped credential is needed on that box). Only a self-hosted deployment may be 'local'. The switch is refused in either direction while calls are still in flight -- going local while outbound jobs are still queued would strand them, and going back to queue while the deployment is still dialing locally would abandon those calls. Once the organization has a local-mode deployment and no queue-mode deployment left, a remote POST /v1/calls for its numbers fails closed rather than enqueueing a job nothing would claim.

## Request body

- GatewayOutboundExecutionMode
  - `outbound_execution_mode` 'queue' | 'local', required

## Response `200`

Updated gateway deployment

---

[API](https://skmtc.dev/skysay/apis/skysay-api.md) · [All operations](https://skmtc.dev/skysay/apis/skysay-api/llms.txt) · [OpenAPI document](https://skmtc.dev/skysay/apis/skysay-api/revisions/148c7e111260?raw)