---
title: "Call the updateClaim MCP tool"
method: POST
path: "/api/v1/actions/updateClaim"
tags: ["Actions"]
---

# Call the updateClaim MCP tool

`POST /api/v1/actions/updateClaim`

## Request

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

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.

## Headers

- `Idempotency-Key` string

## Request body

- object
  - `id` union, required
    - string, uuid
    - string
  - `approved` boolean
  - `statement` string
  - `value` string
  - `evidence_url` string
  - `valid_until` string

## Response `200`

The result of calling this tool.

- object
  - `data` unknown, required
  - `error` unknown, required

## Other responses

- `400`: The request body was not a JSON object (code invalid_request), or Idempotency-Key is malformed (code invalid_idempotency_key).
- `401`: Missing or invalid API key. Send `Authorization: Bearer rmcp_...` (code unauthorized).
- `403`: This tool is out of the key’s granted scope (code insufficient_scope).
- `409`: This Idempotency-Key has an unresolved in-flight or ambiguous result (code request_in_flight). Reconcile before using a new key.
- `422`: This Idempotency-Key was already used with a different request body (code idempotency_key_reuse).
- `429`: Rate limited: shared `mcp:ip:{ip}` (600/60s) or `mcp:key:{keyId}` (120/60s) bucket, the SAME buckets the MCP endpoint uses (code rate_limited).
- `500`: Unhandled server error (code internal_error).

## Changes

- **2026-10-20** `11682826692b`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/reachium/apis/reachium-api/changes/api/v1/actions/updateClaim/post.md)

---

[API](https://skmtc.dev/reachium/apis/reachium-api.md) · [All operations](https://skmtc.dev/reachium/apis/reachium-api/llms.txt) · [OpenAPI document](https://skmtc.dev/reachium/apis/reachium-api/revisions/30c16b30b499?raw)