LinkedIn API
Browse all Linkedin APIs★ Only Publicly Available OpenAPI DocumentSocial MediaSocial Publishingbearer, oauth215 EndpointsREST
For Agents
Retrieve member profiles, publish posts and shares, manage company pages, and track social engagement on LinkedIn. Covers 15 endpoints for professional content and networking.
Use for: I need to post an article to a LinkedIn company page, Retrieve my LinkedIn profile information including email, I want to share a URL with commentary to my LinkedIn feed, Get the follower count for a specific LinkedIn organization
Not supported: Does not handle LinkedIn Ads, Recruiter features, or Learning platform content — use for member profiles, organic posting, and organization page management only.
Jentic publishes the only available OpenAPI specification for LinkedIn API, keeping it validated and agent-ready. Access member profiles, company pages, UGC posts, shares, and social interactions through 15 endpoints on LinkedIn's v2 REST API. Supports OAuth 2.0 authentication with granular scopes for profile reads, content publishing, and organization management using the Rest.li protocol.
Install Jentic One Beta
Connect the LinkedIn API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the LinkedIn API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with LinkedIn API.
Retrieve authenticated member profiles including headline, positions, and email address
Publish UGC posts and shares to personal profiles and company pages
Fetch organization details and page statistics including follower counts
Post comments and likes on activities as social engagement actions
Look up member profiles by person ID with field projection for selective data retrieval
Query organization access control lists to verify page admin permissions
Access OpenID Connect userinfo for identity verification and SSO
Use Cases
Patterns agents use LinkedIn API for, with concrete tasks.
★ AI Agent Content Publishing
An AI agent publishes professional content to LinkedIn by posting UGC (User Generated Content) via POST /ugcPosts with article, image, or text share types. Through Jentic, the agent discovers the publishing operation by searching 'post to linkedin', loads the UGC schema with author URN and share commentary fields, and executes without manual LinkedIn developer portal setup. Supports targeting by seniority, industry, and geography for organization posts.
Create a UGC post via POST /ugcPosts with shareCommentary 'Excited to announce our new product launch' and visibility set to PUBLIC for the authenticated member
Organization Page Management
Retrieve company page details via GET /organizations/{organizationId} including name, description, logo URL, and industry. Access page statistics through GET /organizationPageStatistics for follower counts, page views, and content engagement metrics. Verify page admin permissions using GET /organizationalEntityAcls before attempting publish operations.
Retrieve organization details for organizationId 12345 via GET /organizations/12345 and then fetch page statistics via GET /organizationPageStatistics?q=organization&organization=urn:li:organization:12345
Member Profile Retrieval
Access the authenticated member's profile through GET /me with field projection for selecting specific fields like firstName, lastName, headline, and profilePicture. Look up other members via GET /people/(id:{personId}) when appropriate connection permissions exist. Retrieve email addresses through the dedicated GET /emailAddress endpoint with the r_emailaddress scope.
Retrieve the authenticated member's profile via GET /me and email via GET /emailAddress?q=members&projection=(elements*(handle~)) and combine into a contact record
Social Engagement Automation
Post comments on LinkedIn activities via POST /socialActions/{activityUrn}/comments and register likes via POST /socialActions/{activityUrn}/likes. Enables engagement automation workflows for brand accounts that respond to mentions, acknowledge shares, and maintain active presence on the platform.
Post a comment 'Great insights, thanks for sharing!' on activity urn:li:activity:12345 via POST /socialActions/urn:li:activity:12345/comments
Key Endpoints
15 endpoints — jentic publishes the only available openapi specification for linkedin api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/me
Retrieve authenticated member's profile
POST
/ugcPosts
Publish a UGC post to LinkedIn
GET
/organizations/{organizationId}
Get organization page details
GET
/organizationPageStatistics
Retrieve page follower and engagement stats
POST
/socialActions/{activityUrn}/comments
Post a comment on an activity
POST
/socialActions/{activityUrn}/likes
Like an activity
GET
/emailAddress
Retrieve member's email address
GET
/me
Retrieve authenticated member's profile
POST
/ugcPosts
Publish a UGC post to LinkedIn
GET
/organizations/{organizationId}
Get organization page details
GET
/organizationPageStatistics
Retrieve page follower and engagement stats
POST
/socialActions/{activityUrn}/comments
Post a comment on an activity
POST
/socialActions/{activityUrn}/likes
Like an activity
GET
/emailAddress
Retrieve member's email address
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
LinkedIn OAuth 2.0 tokens with specific scopes (r_liteprofile, w_member_social, rw_organization_admin) are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped tokens — raw client secrets and refresh tokens never enter the agent's context.
Intent-based discovery
Agents search by intent (e.g., 'post an article to linkedin') and Jentic returns the matching POST /ugcPosts operation with the full Rest.li request schema including author URN format, so the agent can publish without navigating LinkedIn's developer documentation.
Time to first call
Direct LinkedIn API integration: 5-10 days for OAuth app approval, scope verification, and Rest.li protocol handling. Through Jentic: under 1 hour — search for the operation, load the schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using LinkedIn API through Jentic.
Why is there no official OpenAPI spec for LinkedIn API?
LinkedIn does not publish an OpenAPI specification for their REST API. Jentic generates and maintains this spec so that AI agents and developers can call LinkedIn API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the LinkedIn API use?
The LinkedIn API uses OAuth 2.0 authorization code flow with specific permission scopes. Common scopes include r_liteprofile (basic profile), r_emailaddress (email), w_member_social (post/comment/like), and rw_organization_admin (company page management). Bearer tokens are passed in the Authorization header. Through Jentic, these tokens are stored encrypted in the MAXsystem vault — agents receive scoped tokens without handling raw client credentials.
Can I publish posts to LinkedIn through this API?
Yes. Use POST /ugcPosts with the w_member_social scope to publish text, articles, or image shares. The request body requires an author URN (urn:li:person:{id}), lifecycleState set to PUBLISHED, shareCommentary text, and visibility settings. For organization posts, use the organization URN as the author with appropriate rw_organization_admin permissions.
What are the rate limits for the LinkedIn API?
LinkedIn enforces application-level throttling at 100 requests per day for most endpoints on standard developer apps. Partner-level apps receive higher limits. The /ugcPosts endpoint allows up to 25 posts per day per member. Rate limit status is returned via X-Li-Response-Throttled headers when approaching limits.
How do I post to a company page through Jentic?
Install the Jentic SDK with pip install jentic, then search for 'publish post to linkedin company page'. Jentic returns the POST /ugcPosts operation with the full request schema showing the organization author URN format, share commentary structure, and required visibility fields. Verify admin access first by loading the GET /organizationalEntityAcls operation. Sign up at https://app.jentic.com/sign-up.
Can I retrieve engagement metrics for LinkedIn company pages?
Yes. Use GET /organizationPageStatistics with the organization URN as a query parameter to retrieve follower counts, page views, and content engagement data. The endpoint requires the rw_organization_admin scope and returns time-bound statistics with breakdowns by visitor demographics.
Does the LinkedIn API support commenting on posts?
Yes. Use POST /socialActions/{activityUrn}/comments to add a comment on any LinkedIn activity. The request body requires the actor URN and message text. Retrieve existing comments with GET /socialActions/{activityUrn}/comments. Both endpoints require the w_member_social scope.
GET STARTED