---
title: "Update conversation"
method: PATCH
path: "/conversations/{conversation_id}"
tags: ["Conversations"]
---

# Update conversation

`PATCH /conversations/{conversation_id}`

Update a conversation.

Required scope: `conversations:write`

## Path parameters

- `conversation_id` string, required

## Request body

- UpdateConversation
  - `assignee_id` string — ID of the teammate to assign the conversation to. Set it to null to unassign.
  - `inbox_id` string — ID of the inbox to move the conversation to.
  - `status` 'archived' | 'open' | 'deleted' | 'spam' — New status of the conversation
  - `status_id` string — Unique identifier of the status to set the conversation to. Only one of status and status_id should be provided. Ticketing must be enabled for the company to use this field.
  - `tag_ids` ResourceID[] — List of all the tag IDs replacing the old conversation tags
  - `description` string, nullable — Description of the task. Only allowed on task conversations. Set to null to clear.
  - `due_at` number, nullable — Unix timestamp in seconds when the task is due. Must be in the future and within 50 years. Only allowed on task conversations. Set to null to clear.
  - `custom_fields` CustomFieldParameter — An object whose key is the `name` property defined for the custom field in the Front UI. The value of the key must use the same `type` specified for the custom field, as described in https://dev.frontapp.com/reference/custom-fields

## Response `204`

No content

## Other responses

- `301` — If the conversation has been merged, the response redirects you to the merged conversation.
- `400` — Invalid input, such as invalid custom fields

---

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