Call the attachResourceToPost MCP tool
Attach a published Reachium document to one of this workspace's LinkedIn posts as a lead-magnet resource. Inputs: post_id (from getContent or getScheduledPosts), document_id (a PUBLIC document from getDocuments), and the comment keyword that will trigger delivery. It updates the post record only: it sets the document, marks the post as a lead magnet, and stores the keyword. It does not publish anything, send any message, or create a campaign, so a post bound this way delivers nothing until a lead-magnet campaign references it; use createLeadMagnetCampaign to build that funnel. Refuses private or admin-only documents and posts outside this workspace. Returns the post_id, document_id and keyword that were saved.
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/attachResourceToPost
- 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.