Call the updateArtifact MCP tool
Apply a revision to an EDITABLE artifact (campaign_copy, content_copy, brand_profile, lead_filter_picker) by id. Pass the full new content object in the shape getArtifact returned, plus the version you read: a stale version is refused with current_version so an edit made meanwhile is never overwritten. Where a card is shown, it updates in place; for content_copy the post body is written through while the post is a draft, planned or approved. A scheduled or published post is refused (wrong_status): edit it with updateDraftPost. Use it to revise copy you already produced instead of creating a new artifact.
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/updateArtifact
- 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.