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

# Call the connectLinkedInAccount MCP tool

`POST /api/v1/actions/connectLinkedInAccount`

## Request

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

Connect a brand-new LinkedIn account, or reconnect an existing disconnected one, by minting a Unipile hosted-auth link. mode "connect" (no account_id) mints a link for a NEW account, gated by the workspace's paid seat limit (refuses with reason "no_seats" when the plan is full). mode "reconnect" (account_id required, from getLinkedInAccounts) re-links an EXISTING account: refuses with "not_found" if the account is not in this workspace, "not_disconnected" if it is currently healthy (nothing to reconnect), or "no_unipile_id" if it has never completed a first connection. Neither mode performs any LinkedIn action by itself: nothing changes in this workspace until a human opens the returned hosted_auth_url and completes the sign-in it walks through. Give that URL ONLY to the intended account owner (whoever holds it can link a LinkedIn login into this workspace) and tell them it expires in about 24 hours.

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
  - `mode` 'connect' | 'reconnect', required: "connect" mints a link for a brand-new account (account_id must be omitted). "reconnect" re-links an existing disconnected account (account_id required).
  - `account_id` string, uuid: Required when mode is "reconnect" (an existing, disconnected account from getLinkedInAccounts). Omit for mode "connect".

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