---
title: "Reply to a conversation"
method: POST
path: "/conversation/{conversation_id}/reply"
tags: ["Conversations"]
---

# Reply to a conversation

`POST /conversation/{conversation_id}/reply`

## Request

- Base URL: `https://api.thrivedesk.com/v1`
- URL: `https://api.thrivedesk.com/v1/conversation/{conversation_id}/reply`
- Auth: HTTP bearer

Reply to a conversation.

## Path parameters

- `conversation_id` string, required

## Request body

- ReplyBody: Sending a reply dispatches the authenticated user's current draft on the conversation. The message content itself is not part of this body. The request fails with 404 if no draft exists. Required custom fields on the inbox must also be supplied, keyed by their field key.
  - `status` 'Active' | 'Pending' | 'Closed', required: Conversation status to set after sending.
  - `assign_to` string, nullable: Agent ID to assign after sending.
  - `action` 'send_and_next_active' | 'send_and_back_to_folder' | 'send_and_stay_on_page': UI follow-up action recorded with the reply.
  - `intended_inbox_address_id` string, nullable: Email alias ID to send from.
  - `cc` string[]
  - `bcc` string[]

## Response `200`

Success.

- object
  - `message` string

## Other responses

- `401`: Missing or invalid bearer token.
- `403`: Token is valid but does not include a required scope, or the user does not have access to the resource.
- `404`: Resource not found.
- `422`: Request body failed validation.
- `429`: Rate limit exceeded. The `Retry-After` header indicates how long to wait before retrying. See [Pagination and rate limits](/get-started/pagination) for the full rate-limit policy.
- `500`: Unexpected server error.

---

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