---
title: "Call the sendReply MCP tool"
method: POST
path: "/api/v1/actions/sendReply"
tags: ["Actions"]
---

# Call the sendReply MCP tool

`POST /api/v1/actions/sendReply`

## Request

- Base URL: `https://app.reachium.io`
- URL: `https://app.reachium.io/api/v1/actions/sendReply`
- Auth: HTTP bearer

Send a text reply into an existing LinkedIn conversation that belongs to this workspace (pass chat_id from getConversations). The reply posts to LinkedIn from the account that owns the chat, so this is a LAUNCH action. Two-step: the first call, without confirm_token, returns a preview of the exact text plus a confirm_token and sends nothing; after the user approves, call again with the same chat_id and text plus the confirm_token to send. Each account has a daily reply cap; when it is reached the call refuses and returns when it resets. This tool only replies inside a chat that already exists: it refuses chat_ids outside the workspace and cannot open a new conversation or message a non-connection. To start a conversation with a 1st-degree connection use sendMessage. Invitation management is not available over MCP. See getPlaybook("campaigns", "reply-handling") for the house reply motion before drafting the text.

Called through the Actions bridge: the response is that tool's own result, wrapped as `{ data: <tool result> }` under HTTP 200. Billing, daily-cap, and confirm-step outcomes are embedded INSIDE `data`, never remapped to an HTTP status (see the templated `/api/v1/actions/{toolName}` operation above for the full protocol, and `x-mcp-actions` for this tool's machine-readable scope/cap/confirm_behavior fields). Authentication, request-shape, and optional idempotency-protocol failures still use their documented non-200 statuses.

## Headers

- `Idempotency-Key` string

## Request body

- object
  - `operation_id` string: Unique logical send ID. Reuse for retries; use a NEW ID only for an intentional new reply, including identical text. Without it, auto-confirm deduplicates identical text indefinitely.
  - `chat_id` string, required: The conversation to reply to (from getConversations).
  - `text` string, required: The reply text to send. No em dashes (arrows are fine).
  - `confirm_token` string: From the preview response. Re-send with the same chat_id and text to execute.

## Response `200`

The result of calling this tool.

- object
  - `data` unknown, required
  - `error` unknown, required

## Other responses

- `400`: The request body was not a JSON object (code invalid_request), or Idempotency-Key is malformed (code invalid_idempotency_key).
- `401`: Missing or invalid API key. Send `Authorization: Bearer rmcp_...` (code unauthorized).
- `403`: This tool is out of the key’s granted scope (code insufficient_scope).
- `409`: This Idempotency-Key has an unresolved in-flight or ambiguous result (code request_in_flight). Reconcile before using a new key.
- `422`: This Idempotency-Key was already used with a different request body (code idempotency_key_reuse).
- `429`: Rate limited: shared `mcp:ip:{ip}` (600/60s) or `mcp:key:{keyId}` (120/60s) bucket, the SAME buckets the MCP endpoint uses (code rate_limited).
- `500`: Unhandled server error (code internal_error).

---

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