Call the getCampaignSequence MCP tool
Read ONE campaign's message sequence back in full: every step with its UNTRUNCATED copy (the create response previews cut copy at 280 characters; this does not), the attached sender accounts, and for a lead-magnet campaign the flat view the app shows (keyword, document, hook post, armed state, comment_reply, delivery_dm, followups with waits) plus sender_resolution: attached, attaches_on_publish (the hook post's account is attached when it publishes), or none (activation will refuse). Use it to verify a campaign before activating, or to read copy before editing with updateDraftCampaign / updateCampaign.
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/getCampaignSequence
- 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 2 revisions of this API.