---
title: "Update Case Notes Settings"
method: PATCH
path: "/developer/case-notes-settings"
tags: ["Developer", "Developer - Settings"]
---

# Update Case Notes Settings

`PATCH /developer/case-notes-settings`

## 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/developer/case-notes-settings`
- Auth: none declared

Update the case notes settings for the current customer.

This endpoint is restricted to developer users only.

- **case_notes_enabled**: Set to true to enable case notes for this customer
- **dry_run_case_matching**: Set to true to enable dry-run mode for case matching
- **note_generation_context**: Context to include in LLM prompt for case note generation

When case_notes_enabled is false:
- The case matching pipeline step is skipped entirely
- No case notes will be generated or posted

When dry-run mode is enabled:
- Case matching still runs automatically
- Matches are flagged as "pending approval" instead of being finalized
- Developers can review and approve/reject matches in the call detail view
- Case notes are only posted after manual approval

The note_generation_context can include:
- Firm-specific preferences for note formatting
- Important information about the firm
- Instructions for how case notes should be generated
- Any other context that should influence note generation

## Request body

- UpdateCaseNotesSettingsRequest: Request to update customer's case notes settings
  - `case_notes_enabled` boolean, nullable: Set to true to enable case notes for this customer
  - `dry_run_case_matching` boolean, nullable: Set to true to enable dry-run mode for case matching
  - `note_generation_context` string, nullable: Context to include in LLM prompt for case note generation (can be multiple lines)
  - `substantive_conversation_criteria` string, nullable: Custom criteria for determining if a call has substantive conversation (can be multiple lines)
  - `include_transcript_in_note` boolean, nullable: Set to true to include call details and the full transcript in SmartAdvocate case notes

## Response `200`

Successful Response

- CaseNotesSettingsResponse: Response with customer's case notes settings
  - `customer_id` string, uuid, required: The customer ID
  - `case_notes_enabled` boolean, required: Whether case notes feature is enabled for this customer
  - `dry_run_case_matching` boolean, required: Whether case matching is in dry-run mode (requires manual approval)
  - `note_generation_context` string, nullable: Optional context to include in LLM prompt for case note generation
  - `substantive_conversation_criteria` string, nullable: Custom criteria for determining if a call has substantive conversation
  - `include_transcript_in_note` boolean: Whether SmartAdvocate case notes include call details and the full transcript below the summary

## Other responses

- `422`: Validation Error

## Changes

- **2026-10-08** `376869b909f7`: 2 info
  - added the new optional request property `include_transcript_in_note`
  - added the optional property `include_transcript_in_note` to the response with the `200` status

[Operation history](https://skmtc.dev/openintake/apis/openintake-api/changes/developer/case-notes-settings/patch.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)