> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fuseai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# LinkedIn connections and messages

> Check whether someone is connected to your LinkedIn accounts, list pending invitations and connections, and read your LinkedIn conversations

These endpoints read what the LinkedIn accounts connected to Fuse hold: who they are connected to, which invitations are pending, and their conversations. They need a key with the `linkedin` [scope](https://docs.fuseai.com/concepts/scopes.md).

They read Fuse's stored copy of each account, not LinkedIn itself, so calling them uses none of your LinkedIn accounts' own limits and puts nothing at risk on LinkedIn. See [How fresh the data is](#how-fresh-the-data-is) for how far behind LinkedIn that copy can be.

## Which accounts are read

Each endpoint covers every LinkedIn account you own and every account a teammate shared with you with inbox access. Every row carries the `accountId` it came from. To read one account, pass its `accountId`: your own accounts are listed by `GET /business/accounts?channel=linkedin`.

An `accountId` that is not yours or shared with you answers [`404 LINKEDIN_ACCOUNT_NOT_FOUND`](https://docs.fuseai.com/concepts/errors#linkedin_account_not_found). One shared with you for campaigns only answers [`403 LINKEDIN_PERMISSION_DENIED`](https://docs.fuseai.com/concepts/errors#linkedin_permission_denied): reading it needs inbox access, which the account's owner grants in the app.

## Check one person

`GET /business/linkedin/connection-status` takes the person's LinkedIn profile URL and answers whether any of your accounts is connected to them, and which invitations are pending between you.

```bash theme={null}
curl -G https://api.tryfuse.ai/api/v1/business/linkedin/connection-status \
  --data-urlencode "linkedinUrl=https://www.linkedin.com/in/jane-doe" \
  -u "$FUSE_API_KEY:"
```

```json theme={null}
{
  "publicIdentifier": "jane-doe",
  "status": "invitation_sent",
  "connectedAccountIds": [],
  "sentInvitations": [
    { "accountId": "t5XY4yQzR9WVrln3bvG3Jw", "invitationId": "7392847562918374512", "invitedAt": "2026-10-28T00:00:00.000Z" }
  ],
  "receivedInvitations": []
}
```

| `status` | Meaning |
| - | - |
| `connected` | At least one of your accounts is connected to the person; `connectedAccountIds` names them. |
| `invitation_sent` | None is connected, and an invitation one of your accounts sent them is still pending. |
| `not_connected` | Neither. An invitation the person sent you is listed in `receivedInvitations` and leaves the status here. |

The URL can come in any common form: with or without `https://` and `www`, with a trailing slash or a query string. A profile with accented letters matches whether you send it percent-encoded (`/in/jos%C3%A9-l`) or not. This check also covers accounts shared with you for campaigns only.

## Pending invitations

`GET /business/linkedin/invitations` lists the invitations still waiting: `type=sent` for the ones your accounts sent, `type=received` for the ones sent to them, or both when `type` is left out.

```bash theme={null}
curl -G https://api.tryfuse.ai/api/v1/business/linkedin/invitations \
  --data-urlencode "type=sent" \
  --data-urlencode "limit=100" \
  -u "$FUSE_API_KEY:"
```

```json theme={null}
{
  "invitations": [
    {
      "invitationId": "7392847562918374512",
      "accountId": "t5XY4yQzR9WVrln3bvG3Jw",
      "type": "sent",
      "name": "Jane Doe",
      "headline": "VP Sales at Acme",
      "publicIdentifier": "jane-doe",
      "linkedinUrl": "https://www.linkedin.com/in/jane-doe",
      "invitedAt": "2026-10-28T00:00:00.000Z"
    }
  ],
  "pagination": { "page": 1, "pageSize": 100, "total": 1, "totalPages": 1 }
}
```

`name`, `headline` and `publicIdentifier` always describe the other person: the one invited for a sent invitation, the sender for a received one. Add `linkedinUrl` together with `type` to look for one person. An accepted invitation leaves this list and the person appears under [connections](#connections).

## Connections

`GET /business/linkedin/connections` lists your accounts' 1st-degree connections, with `search` to match a name.

```bash theme={null}
curl -G https://api.tryfuse.ai/api/v1/business/linkedin/connections \
  --data-urlencode "search=Lee" \
  -u "$FUSE_API_KEY:"
```

```json theme={null}
{
  "connections": [
    {
      "accountId": "t5XY4yQzR9WVrln3bvG3Jw",
      "firstName": "Lee",
      "lastName": "Park",
      "headline": "Head of Growth at Northwind",
      "publicIdentifier": "lee-park",
      "linkedinUrl": "https://www.linkedin.com/in/lee-park"
    }
  ],
  "pagination": { "page": 1, "pageSize": 25, "total": 1, "totalPages": 1 }
}
```

A person connected to two of your accounts is listed once for each. The order stays the same from page to page, so walking every page visits each connection once; it is not the order they connected in.

## Conversations

`GET /business/linkedin/chats` lists your accounts' LinkedIn conversations, messages and InMail alike, newest last message first. `campaignId` keeps the ones a Fuse campaign started, `since` and `to` keep the ones with a message in that window, and `search` matches the other person's name.

```bash theme={null}
curl -G https://api.tryfuse.ai/api/v1/business/linkedin/chats \
  --data-urlencode "since=2026-11-01T00:00:00.000Z" \
  -u "$FUSE_API_KEY:"
```

```json theme={null}
{
  "chats": [
    {
      "chatId": "Xk3bQ8sLR2iT0aVw9yZp4A",
      "accountId": "t5XY4yQzR9WVrln3bvG3Jw",
      "campaignId": "6a01f3c2e4b0a1d2c3e4f5a6",
      "participants": [{ "name": "Jane Doe", "linkedinUrl": "https://www.linkedin.com/in/jane-doe" }],
      "lastMessage": { "text": "Thanks, Thursday works for me.", "subject": null, "sentAt": "2026-11-03T14:12:09.000Z" },
      "unreadCount": 1
    }
  ],
  "pagination": { "page": 1, "pageSize": 25, "total": 1, "totalPages": 1 }
}
```

`GET /business/linkedin/chats/{chatId}` reads one conversation, oldest message first. `direction` says whether your account sent the message or the other person did.

```bash theme={null}
curl https://api.tryfuse.ai/api/v1/business/linkedin/chats/$CHAT_ID \
  -u "$FUSE_API_KEY:"
```

```json theme={null}
{
  "chatId": "Xk3bQ8sLR2iT0aVw9yZp4A",
  "messages": [
    {
      "text": "Hi Jane, saw your post on outbound. Open to a quick chat next week?",
      "sentAt": "2026-11-02T09:30:00.000Z",
      "direction": "sent",
      "sender": { "name": "Sam Seller", "linkedinUrl": "https://www.linkedin.com/in/sam-seller" }
    },
    {
      "text": "Thanks, Thursday works for me.",
      "sentAt": "2026-11-03T14:12:09.000Z",
      "direction": "received",
      "sender": { "name": "Jane Doe", "linkedinUrl": "https://www.linkedin.com/in/jane-doe" }
    }
  ]
}
```

> [!NOTE]
>
> When **Contact Visibility** in the app's LinkedIn inbox settings is **Show only campaign contacts**, the conversation list holds only conversations that belong to a campaign, as the app's inbox does. A participant's `linkedinUrl` is the one LinkedIn gives in the conversation and may be the member-id form (`linkedin.com/in/ACoAA...`) rather than the profile's public URL, so match people against the profile URLs your other calls return with care.

## How fresh the data is

* **Connections** are stored when LinkedIn reports a new one, and a full resync of every account runs every 6 hours. A just-accepted invitation can read as `invitation_sent` until the connection is stored; once it is, `connected` wins.
* **Pending invitations** are stored when one of your accounts sends one through Fuse, and the pending lists are resynced every 6 hours. An invitation sent from LinkedIn itself appears at the next resync.
* **Declined invitations** are not reported by LinkedIn. An invitation stays pending until it is accepted or withdrawn, or until it drops out of LinkedIn's pending list at a resync.
* **Messages** arrive as LinkedIn delivers them to Fuse.

So to learn when invitations are accepted, check `connection-status` for the people you invited, or walk `connections`, every few minutes at most: anything faster sees the same answers.

## Limits

The LinkedIn endpoints share one [rate limit](https://docs.fuseai.com/concepts/rate-limits.md) of 120 requests a minute and 10,000 a day. Your user's LinkedIn reads are also capped at 300 a minute and 20,000 a day, which counts what the Fuse app and your campaigns read for you too; past it, these endpoints answer `429 RATE_LIMITED` without a `Retry-After` header, so wait a minute.

These endpoints only read. To send invitations or messages, use a [campaign](https://docs.fuseai.com/guides/campaigns.md) or the [MCP server](https://docs.fuseai.com/mcp/tools.md). To write each contact's LinkedIn status onto HubSpot contacts, see [LinkedIn status on contacts](https://docs.fuseai.com/crm/linkedin-status.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.