Call the sendMessage MCP tool
Send a LinkedIn direct message to a lead who is already a 1st-degree connection of one of this workspace's LinkedIn accounts, starting a new conversation if none exists. Use sendReply instead when you already have a chat_id. Refuses non-connections (it can never cold-DM). LAUNCH action, two-step: first call returns a preview and confirm_token; re-send with the same lead_id and text plus confirm_token to send. Draws from the same daily per-account message budget as campaigns. If the workspace has several accounts and none has a chat or invite history with the lead, pass linkedin_account_id (from getLinkedInAccounts).
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/sendMessage
- 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.