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

# Call the getCampaignLeads MCP tool

`POST /api/v1/actions/getCampaignLeads`

## Request

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

Per-lead progress for ONE campaign: who accepted, replied, booked, failed (with fail_reason), or is still pending, plus each lead state. Use after getCampaigns (for the campaign_id) when the user asks how a campaign is doing lead by lead. Paginated with limit/offset; the response includes total. Aggregate numbers live in getCampaignStats and getCampaignFunnel.

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
  - `campaign_id` string, uuid, required: Campaign id from getCampaigns.
  - `status` 'accepted' | 'replied' | 'booked' | 'pending_invite' | 'in_progress' | 'failed' | 'completed': Optional filter: accepted | replied | booked | pending_invite | in_progress | failed | completed. Omit for all leads.
  - `limit` integer: Rows per page (default 50, max 100).
  - `offset` integer: Pagination offset (default 0).

## 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).

---

[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/11682826692b?raw)