Skip to main content
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. 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 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. One shared with you for campaigns only answers 403 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.
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.
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

GET /business/linkedin/connections lists your accounts’ 1st-degree connections, with search to match a name.
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.
GET /business/linkedin/chats/{chatId} reads one conversation, oldest message first. direction says whether your account sent the message or the other person did.
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 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 or the MCP server. To write each contact’s LinkedIn status onto HubSpot contacts, see LinkedIn status on contacts.