---
title: "Reply to a conversation"
method: POST
path: "/v1/conversations/{id}/reply"
tags: ["messaging"]
---

# Reply to a conversation

`POST /v1/conversations/{id}/reply`

## Request

- Base URL: `https://api.botdog.co`
- URL: `https://api.botdog.co/v1/conversations/{id}/reply`
- Auth: API key in header `x-api-key`

Reply to a conversation by its id: the `chatId` returned by POST /v1/messages, GET /v1/leads/{id} or the LEAD_MESSAGE_REPLIED webhook, or the conversation id in the Botdog inbox URL. The conversation must be with one of your team’s leads. Rate-limited per sending account.

## Path parameters

- `id` string, required

## Request body

- ReplyDto
  - `text` string, required: The reply text

## Response `200`

- SendMessageResponseDto
  - `leadId` string: The lead that was messaged
  - `chatId` string, required: The conversation the message was sent to. Use it with POST /v1/conversations/{id}/reply.
  - `messageId` string, nullable, required: The provider message id, if returned

## Other responses

- `401`: Unauthorized. API key is missing or invalid.
- `403`: The key owner has no seat assigned (write endpoints only), the team is on Botdog Managed and so may only read (write endpoints only), or the subscription/plan does not permit this.
- `404`: Conversation not found, or not with one of your team’s leads
- `429`: Per-account send limit reached

---

[API](https://skmtc.dev/botdog/apis/botdog-api.md) · [All operations](https://skmtc.dev/botdog/apis/botdog-api/llms.txt) · [OpenAPI document](https://skmtc.dev/botdog/apis/botdog-api/revisions/6c0213d8a608?raw)