---
title: "User Change Matched Case"
method: POST
path: "/calls/{call_id}/user-change-matched-case"
tags: ["Calls"]
---

# User Change Matched Case

`POST /calls/{call_id}/user-change-matched-case`

Change the matched case for a call (end-user).

Requires the case_match_corrections_enabled feature flag (developers
bypass via the developer endpoint). Deletes the old note (if we posted
it), regenerates the note against the new case's context, and posts it
to the new case.

## Path parameters

- `call_id` string, uuid, required

## Request body

- ChangeMatchedCaseRequest — Request to change the matched case (and safely delete old note if posted). Cross-provider changes are not supported. Provide `case_provider` + `case_local_id` (preferred) or legacy `new_smartadvocate_case_id`.
  - `case_provider` string, nullable — 'smartadvocate' or 'filevine'
  - `case_local_id` string, uuid, nullable — PK in the provider's local table
  - `new_smartadvocate_case_id` string, uuid, nullable — Legacy SA-only field

## Response `200`

Successful Response

- ChangeMatchedCaseResponse — Response from changing the matched case.
  - `success` boolean, required — Whether the operation was successful
  - `old_note_deleted` boolean — Whether the old note was deleted
  - `new_note_posted` boolean — Whether a new note was posted
  - `matched_case_number` string, nullable — New case number
  - `matched_case_name` string, nullable — New case name
  - `message` string, required — Status message

## 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)