Call the sendReply MCP tool
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.
Request
- Base URL: https://app.reachium.io
- URL: https://app.reachium.io/api/v1/actions/sendReply
- Auth: HTTP bearer
Headers
Optional caller-generated key (8-200 characters: letters, digits, dot, underscore, colon, or hyphen). A final tool result is replayed for the same key and body. An ambiguous result remains 409 under that key; reconcile external state before using a new key. Reuse with a different body returns 422.
Request body
Response
The result of calling this tool.
Changes
No recorded changes to this operation across all 1 revision of this API.