Actions

Call the updateClaim MCP tool

Changed on

Approve, retire or correct ONE claim (a marketing number such as "2.3x pipeline in 90 days") by id, from getBrandProfile sections claims. Only approved claims are ever used in copy, so set approved:true ONLY when the user explicitly confirms the number is right and current; set approved:false to retire a stale one. statement, value, evidence_url and valid_until (YYYY-MM-DD) correct the record.

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.

post/api/v1/actions/updateClaim

Request

  • Base URL: https://app.reachium.io
  • URL: https://app.reachium.io/api/v1/actions/updateClaim
  • Auth: HTTP bearer

Headers

Idempotency-Keystring

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

approvedboolean
statementstring
valuestring
evidence_urlstring
valid_untilstring

Response

The result of calling this tool.

dataunknown required
errorunknown required

Changes