Call the getContent MCP tool
Read the visitor's LinkedIn content. Call with a view: 'pipeline' for status counts and what's waiting/upcoming; 'review' for every draft/approved post awaiting a human, FULL body, oldest first ("what needs my approval"); 'failed' for posts that failed to publish; 'ideas' for recent EXISTING ideas (full hooks; rank 'meh' is default for never-ranked, not a judgment); 'posts' for recent posts with a body preview (optional status filter); 'plan' for the active content plan and cadence; 'brand' for the active brand profile.
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/getContent
- 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.