linkedin. A member profile publishes text, image, video, multi-image, and link posts as the person, replies to, likes, and deletes comments, and returns insights. A company Page publishes as the Page, returns insights, and adds comment listing, mentions, and the Page’s posts made outside SocialAPI. SocialAPI’s own LinkedIn app connects both, so you register nothing: see Platform apps.
At a glance
Capabilities
An unsupported call returns501 resource.not_supported.
The cross-platform matrix is on Platforms.
Connect an account
Connect withPOST /v1/accounts/connect and "platform": "linkedin". One LinkedIn authorization offers the member profile of the person who signs in and every company Page that person administers. The shared flow, request fields, and result are in Connect accounts, and the redirect parameters are in Redirect parameters.
- One account per connect. When the authorization offers exactly 1 account, it connects at once with
status=success. When it offers more than 1, the redirect carriesstatus=selection_requiredand you choose one, as described in Choose a LinkedIn profile or Page. Connect the others from the same login with the login endpoints, with no new consent screen. - Narrow the connect with
metadata.connection_type."profile"requests the member profile scopes only and offers the member profile only."organization"requests the company Page scopes only and offers the member’s company Pages only. Withoutconnection_type, the connect requests both sets and offers both. Any other value returns400 validation.connection_type_invalid. - No company Page. A connect with
"organization"by a member who administers no company Page ends withstatus=erroranderror=platform.linkedin.no_pageson yourredirect_uri. - The account.
GET /v1/accountsreturns every LinkedIn account withplatform: "linkedin"andconnection_type:profilefor a member profile,organizationfor a company Page. In the selection candidates, the login’s profile list, and the assign response,platform_account_idis LinkedIn’s URN:urn:li:person:...for a member profile,urn:li:organization:...for a company Page. - More than 1 LinkedIn account per brand. A brand can hold more than 1 LinkedIn account, for example a member profile and the company Pages that member administers. Every other platform holds 1 account per brand. Each LinkedIn account belongs to 1 brand.
- Reconnect. Send the same connect request with
"platform": "linkedin"and the account’sbrand_id, and choose the same profile or Page if asked. A reconnect that grants every scope the account’s login holds renews that login: each other LinkedIn account with the samelogin_idthat istoken_expiredreturns toactivetoo. A reconnect that grants fewer scopes than the login holds renews only the account you reconnect, and removes itslogin_id. For example, a"profile"or"organization"reconnect of an account whose login was authorized withoutconnection_type, or a reconnect with a shorterpermissionslist. See Reconnect an account. - Token lifetime. LinkedIn access tokens last 60 days and cannot be refreshed. When LinkedIn reports that the token is invalid, expired, or revoked, the call returns
401 platform.linkedin.authand the account is markedtoken_expired. Every later call that acts on the account returns403 account.reconnection_requireduntil you reconnect it. A401that does not name the token returns401 platform.linkedin.unauthorizedand the account stays usable: see Account status. - Disconnect. LinkedIn offers apps no way to end an authorization. Disconnecting an account removes it from SocialAPI, and the person removes SocialAPI’s app in their LinkedIn settings.
POST /v1/accounts/connect and POST /v1/invites return 400 validation.platform_invalid for platform: "linkedin_page".
Connect more profiles and Pages from a login
A login is one LinkedIn member’s authorization. Every LinkedIn account connected through it carries the samelogin_id in GET /v1/accounts. Use it to connect the member profile or another company Page of that member to any of your brands, with no new consent screen.
GET /v1/platforms/linkedin/logins/{login_id}/profiles includes company Pages the member started administering after the authorization. A login authorized with connection_type: "profile" lists no company Page. The list leaves out the member profile when the login cannot publish as the member: a login authorized with "organization", or with a permissions list that leaves out posts.write.
POST /v1/platforms/linkedin/logins/{login_id}/profiles/{profile_id}/assign connects one of them to a brand. {profile_id} is the platform_account_id, sent as it is or URL-encoded.
account.connected. The rules:
- One brand per LinkedIn account. Assigning an account that another of your brands holds returns
400 validation.profile_already_assigned, withmeta.brand_idnaming that brand. Assigning it to the brand that already holds it returns HTTP 201 with the sameaccount_id. - The login must still reach the account. A company Page the login’s member does not administer, any company Page when the login was authorized with
connection_type: "profile", or a member profile other than that member’s own, returns400 validation.profile_not_granted, with the URN inmeta.platform_account_id. - The brand must be yours. A missing
brand_idreturns400 validation.field_required. A brand that is not yours, or that is outside your brand-restricted key’s brands, returns404 brand.not_found. - The login must be yours. An unknown
{login_id}returns404 resource.not_foundon both endpoints. - The request must be well formed. A body that is not valid JSON returns
400 validation.body_invalid, and a{profile_id}with broken URL encoding returns400 validation.invalid_profile_id. - The login must still be authorized. When LinkedIn refuses the login, both endpoints return
401 platform.linkedin.author401 platform.linkedin.unauthorized: reconnect an account of that member with every scope the login holds. LinkedIn’s own rate limit returns429 platform.linkedin.rate_limit, and other refusals by LinkedIn return a platform error. These errors do not change the status of any account. - A login ends with its last account. Disconnecting the last LinkedIn account on a login removes the login: both endpoints then return
404 resource.not_foundfor itslogin_id. - Cost. Listing and assigning cost no credits.
- Scopes. Listing needs the
accounts:readscope, and assigning needsaccounts:manage. - AI agents. No MCP tool covers the login endpoints. Call them through the REST API.
login_id in two cases:
- The connect granted fewer scopes than the member’s login holds. The login holds the scopes of the connect that gave that member’s other LinkedIn accounts their
login_id. For example, a"profile"connect when the login was authorized withoutconnection_type, an"organization"connect when it was authorized with"profile", or a shorterpermissionslist. Use thelogin_idof that member’s other LinkedIn accounts instead, or reconnect the account with the sameconnection_typeandpermissionsas the connect that authorized the login. - The account was connected before 2026-11-05. Reconnect it to get a
login_id. The first case applies to that reconnect too. See the changelog.
Comments
A company Page lists, replies to, likes, and deletes the comments on its posts, and a member profile replies to, likes, and deletes comments but cannot list them: see LinkedIn comments.Insights
GET /v1/platforms/linkedin/insights?account_id={account_id} returns the follower count and per-post counts for a company Page or a member profile. kind tells them apart: member for a member profile, organization for a company Page. On a Page, posts covers the Page’s 50 most recent posts.
- On a member profile,
postscovers the 5 most recent posts published to the profile through SocialAPI. It is an empty array until you publish one, andfollower_countis returned either way. - Each member profile post returns
impressions,unique_views,likes,comments, andshares.clicksandengagement_rateare always 0 for a member profile. - A count LinkedIn cannot return for a post is 0.
- The route requires the
analytics.readpermission.
Webhook events
Every event is described in Webhook events.
Limits
Scopes
SocialAPI’s LinkedIn app requests these scopes at connect. You apply for no app review. Each scope belongs to the account permissions in the last column, and the consent screen asks for the scopes of the permissions you selected. A connect withoutconnection_type requests the scopes of both tables, "profile" the member profile table only, and "organization" the company Page table only.
Member profile scopes:
Company Page scopes:
Related
- LinkedIn publishing: fields, media rules, text formatting, and quirks for publishing
- LinkedIn comments: list, reply to, like, and delete comments on company Page and member profile posts
- Connect accounts: the shared connect flow and the profile or Page choice
- Platforms: the capability matrix
- Errors: every error code