---
title: "Update Lead Settings"
method: PUT
path: "/settings/leads"
tags: ["Settings"]
---

# Update Lead Settings

`PUT /settings/leads`

## Request

- Base URL: `https://api.openintake.ai` (the document declares no server; this is the origin it was published from)
- URL: `https://api.openintake.ai/settings/leads`
- Auth: none declared

Update lead notification settings for the customer.

Allows updating dry run mode and notification email recipients.

## Request body

- UpdateLeadSettingsRequest: Update lead notification settings request model
  - `email_notifications_enabled` boolean, nullable: Whether automatic lead notification emails are enabled
  - `dry_run` boolean, nullable: Whether lead notification emails require manual sending
  - `notification_email_recipients` string[], nullable: List of email addresses to receive lead notification emails
  - `sms_notifications_enabled` boolean, nullable: Whether automatic lead notification SMS are enabled
  - `notification_sms_recipients` string[], nullable: List of phone numbers (E.164 format) to receive lead notification SMS
  - `lead_scoring_context` string, nullable: Criteria for scoring leads as low, medium, or high value
  - `lead_scoring_mode` 'low_medium_high' | 'custom_prompt', nullable: Which lead scoring strategy to use
  - `lead_scoring_custom_prompt` string, nullable: Free-text scoring instructions used when lead_scoring_mode is 'custom_prompt'
  - `lead_scoring_custom_schema` object, nullable: JSON Schema (draft-7 object) describing the custom scoring output when lead_scoring_mode is 'custom_prompt'
  - `test_notifications_enabled` boolean, nullable: Whether notifications are sent for test calls and chats
  - `lead_source_enabled` boolean, nullable: Whether lead source extraction is enabled for calls and chats
  - `lead_generation_context` string, nullable: General context to guide lead classification and extraction behavior
  - `urgency_enabled` boolean, nullable: Assess urgency for leads and inquiries from calls and chats
  - `urgency_prompt` string, nullable: Custom urgency criteria; send null to reset to the default
  - `info_request_forces_lead` boolean, nullable: Whether sending an info request SMS during a call forces the call to be classified as a lead
  - `lead_notification_template` 'default' | 'legal_pocket' | 'credit_hound', nullable: Which SES email template variant to use for lead notifications
  - `lead_value_label` 'lead_value' | 'lead_priority' | 'lead_score', nullable: Which label to display for the lead score metric (app UI, emails, SMS)

## Response `200`

Successful Response

- LeadSettingsResponse: Lead notification settings response model
  - `email_notifications_enabled` boolean, required: Whether automatic lead notification emails are enabled
  - `dry_run` boolean, required: Whether lead notification emails require manual sending
  - `notification_email_recipients` string[]: List of email addresses to receive lead notification emails
  - `sms_notifications_enabled` boolean, required: Whether automatic lead notification SMS are enabled
  - `notification_sms_recipients` string[]: List of phone numbers (E.164 format) to receive lead notification SMS
  - `lead_scoring_context` string, nullable: Criteria for scoring leads as low, medium, or high value
  - `lead_scoring_mode` 'low_medium_high' | 'custom_prompt': Which lead scoring strategy to use
  - `lead_scoring_custom_prompt` string, nullable: Free-text scoring instructions used when lead_scoring_mode is 'custom_prompt'
  - `lead_scoring_custom_schema` object, nullable: JSON Schema (draft-7 object) describing the custom scoring output when lead_scoring_mode is 'custom_prompt'
  - `test_notifications_enabled` boolean, required: Whether notifications are sent for test calls and chats
  - `lead_source_enabled` boolean, required: Whether lead source extraction is enabled for calls and chats
  - `lead_generation_context` string, nullable: General context to guide lead classification and extraction behavior
  - `urgency_enabled` boolean: Assess urgency for leads and inquiries from calls and chats
  - `urgency_prompt` string, nullable: Custom urgency criteria; null uses the default
  - `urgency_default_prompt` string, required: Built-in urgency criteria (read-only)
  - `info_request_forces_lead` boolean, required: Whether sending an info request SMS during a call forces the call to be classified as a lead
  - `lead_notification_template` 'default' | 'legal_pocket' | 'credit_hound': Which SES email template variant to use for lead notifications
  - `lead_value_label` 'lead_value' | 'lead_priority' | 'lead_score': Which label to display for the lead score metric (app UI, emails, SMS)

## Other responses

- `422`: Validation Error

## Changes

- **2026-09-15** `a208ca0461de`: 5 info
  - added the new optional request property `urgency_enabled`
  - added the new optional request property `urgency_prompt`
  - added the optional property `urgency_enabled` to the response with the `200` status
  - added the optional property `urgency_prompt` to the response with the `200` status
  - …1 more

[Operation history](https://skmtc.dev/openintake/apis/openintake-api/changes/settings/leads/put.md)

---

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