Call the addSearchToLeadList MCP tool
Export people matching a Reachium database search into a lead list. CHARGES CREDITS per lead actually added. Two-step: the FIRST call (no confirm_token) returns a preview (match count, cost, balance) and a confirm_token, charging nothing; call again with confirm_token to execute. Filters match searchDatabase (refine there first, free); pass the filters_used echoed by your last searchDatabase verbatim, so the exported set is EXACTLY the one previewed. Target exactly one of target_list_id or new_list_name. Leads already in the workspace are merged, not duplicated.
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/addSearchToLeadList
- 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 3 revisions of this API.