---
title: "Update Outbound Developer Settings"
method: PATCH
path: "/developer/outbound-developer-settings"
tags: ["Developer", "Developer - Settings"]
---

# Update Outbound Developer Settings

`PATCH /developer/outbound-developer-settings`

Update the developer-only outbound settings for the current customer.

This endpoint is restricted to developer users only. Customers can read
some of these settings via their own outbound-settings endpoint (they
drive copy and which parts of the Outbound page apply) but not change them.

## Request body

- UpdateOutboundDeveloperSettingsRequest — Request to update customer's developer-only outbound settings
  - `extended_calling_window_enabled` boolean, nullable — Set to true to relax the outbound calling window bounds for this customer from 12:00-18:00 ET to 08:00-20:00 ET
  - `trigger_fields` TriggerFieldConfig[], nullable — Replaces the full list of fields an outbound call trigger supplies for this customer. Customers cannot edit their own trigger contract.
    - `key` string, required — Key under which the resolved value is stored in trigger_metadata
    - `label` string, required — Human label shown in the UI
    - `type` string, required — Control type: "select", "text" or "qa_list"
    - `options` TriggerFieldOption[] — Allowed values; required for type=select, ignored for type=text and type=qa_list
      - `value` string, required — Value stored in OutboundLead.trigger_metadata
      - `label` string, required — Human label; this is what gets injected into the prompt
  - `call_pacing_enabled` boolean, nullable — Set to false to drain the whole outbound queue per run and dial immediately on enqueue instead of one call per 10 minutes
  - `max_calls_per_number_per_day` integer, nullable — Per-phone-number daily outbound call limit. Send 0 for no limit (stored as null). Omit to leave unchanged.
  - `outbound_leads_enabled` boolean, nullable — Set to false when this customer's leads come from a trigger: hides their lead list, CSV import and manual call queueing, and rejects the lead-writing endpoints

## Response `200`

Successful Response

- OutboundDeveloperSettingsResponse — Response with customer's developer-only outbound settings (stored on settings_outbound)
  - `customer_id` string, uuid, required — The customer ID
  - `extended_calling_window_enabled` boolean, required — Whether this customer may set an outbound calling window wider than 12:00-18:00 ET (relaxes the bounds to 08:00-20:00 ET)
  - `trigger_fields` TriggerFieldConfig[] — Fields an outbound call trigger supplies for this customer (from their CRM or a Meta lead-ad automation)
    - `key` string, required — Key under which the resolved value is stored in trigger_metadata
    - `label` string, required — Human label shown in the UI
    - `type` string, required — Control type: "select", "text" or "qa_list"
    - `options` TriggerFieldOption[] — Allowed values; required for type=select, ignored for type=text and type=qa_list
      - `value` string, required — Value stored in OutboundLead.trigger_metadata
      - `label` string, required — Human label; this is what gets injected into the prompt
  - `call_pacing_enabled` boolean, required — Whether outbound calls are paced at one per customer per 10 minutes. When false, the whole queue drains in one run and enqueueing dials immediately.
  - `max_calls_per_number_per_day` integer, nullable — Per-phone-number daily outbound call limit. Null means no limit.
  - `outbound_leads_enabled` boolean, required — Whether this customer curates an outbound lead list. When false their leads come from a trigger, so the lead list, CSV import and manual call queueing are hidden and the lead-writing endpoints reject.

## Other responses

- `422` — Validation Error

---

[API](https://skmtc.dev/openintake/apis/fastapi.md) · [All operations](https://skmtc.dev/openintake/apis/fastapi/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/openintake/fastapi/revisions/4a81645b59f6/schema)