---
title: "Rename Deal"
method: POST
path: "/api/prospecting/deals/{deal_id}/rename"
tags: ["prospecting"]
---

# Rename Deal

`POST /api/prospecting/deals/{deal_id}/rename`

Rename the display fields of one deal.

Mirrors the chat agent's `rename_pipeline_deal` tool so both surfaces write
the same two columns and nothing else.

## Query parameters

- `user_id` string, nullable
- `org_id` string, nullable

## Request body

- RenameDealRequest — Display-only rename. Deliberately carries NO contact/client field. `target_name` / `target_company_name` are a display snapshot on the deal row, not a join to the linked contact — so this changes the board label and nothing else. Re-pointing a deal at a different person is NOT exposed here: `dedupe_key` is `manual:<contact_id>` and the suppression/identity checks run against that contact at creation, so swapping it without recomputing both could mint a second live deal for one human. That repair is archive + re-add, which recomputes everything.
  - `target_name` string, nullable
  - `target_company_name` string, nullable

## Response `200`

Successful Response

- unknown

## Other responses

- `422` — Validation Error

---

[API](https://skmtc.net/every/apis/every-api.md) · [All operations](https://skmtc.net/every/apis/every-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/every/every-api/revisions/292f0c9a098f/schema)