Unlock the potential of the LinkedIn developer API with our comprehensive guide. Whether you're building tools for HR, SaaS, or dev-centric platforms, you'll find actionable insights and practical advantages. From understanding the core architecture of the LinkedIn API to deploying real-world use cases, this guide walks you through everything you need to know.
In this LinkedIn API guide, you'll learn:
const profile = await unipile.linkedin
.getProfile("user_id");
console.log(profile.name);
What is LinkedIn API?
Short answer
Yes, LinkedIn has an official REST API, organized into product families: Consumer, Marketing, Sales, Talent, Learning and Compliance. Sign In with LinkedIn and Share on LinkedIn are self-serve for any app, while messaging, connections and most profile data require LinkedIn's approval.
Source: LinkedIn API documentation (Microsoft Learn) and Getting access to LinkedIn APIs. Last verified: November 2026.
The LinkedIn API (Application Programming Interface) is the essential bridge between your application and LinkedIn, acting on behalf of your authenticated users. Whether you're building recruitment software, CRM systems, or workflow automation tools, understanding LinkedIn API integration is key to letting your users retrieve and interact with the professional and company information they have access to on LinkedIn.
Where the LinkedIn API stands in November 2026
Posts API: it replaces the UGC Posts API, which LinkedIn now lists as legacy.
Sign In: the legacy r_liteprofile and r_emailaddress scopes were retired on August 1, 2023, in favor of OpenID Connect (openid, profile, email).
Versions: versioned APIs are released monthly; the latest is 202611, and each version is supported for at least one year.
Closed programs: Sales Navigator (SNAP) and the Job Posting API do not accept new partners.
Sources: Posts API, Sign In with LinkedIn, Versioning, Sales and Job Posting API (Microsoft Learn). Last verified: November 2026.
Why do developers need LinkedIn API for their software?
The LinkedIn API is a set of programming interfaces that allows developers to integrate LinkedIn functionality into their applications. Think of the LinkedIn API as a secure gateway that lets your software communicate with LinkedIn's platform to:
Whether you're building a CRM, ATS, or an sales engagement platform, LinkedIn integration enhances your product's capabilities around talent acquisition, business connections, and targeted marketing.
LinkedIn API Integration Across Products
A key advantage of the LinkedIn API is its ability to work across LinkedIn's ecosystem:
This multi-product integration capability allows developers to build comprehensive solutions that leverage LinkedIn's full professional ecosystem, creating a unified experience for users across different LinkedIn environments.
LinkedIn API vs Web Scraping: What's the Difference?
Understanding why API access provides a more reliable, secure, and legally compliant solution for your LinkedIn integration needs.
For a closer look at compliant access through each user's own account versus third-party data brokers, read our guide to getting LinkedIn data into your software.
Unipile operates without its own profile database. No LinkedIn profile information is retained or indexed independently by the service. Data is fetched only when the authenticated user triggers a workflow through your application, and only in the volume strictly required to execute that workflow.
Official LinkedIn API Types: Which One Do You Need?
LinkedIn offers several official APIs: two are self-serve, the others go through its partner programs. Here's what each LinkedIn API endpoint provides:
LinkedIn Profile API
/v2/userinfoRetrieve user profile information to sync into your CRM and authenticate users.
LinkedIn Connections API
/v2/connections?q=viewerAccess user's professional network for analysis and connection recommendations.
LinkedIn Share API
/v2/ugcPostsWe just shipped our new onboarding flow.
Post content on behalf of users for social media management and automation.
LinkedIn Organization API
/rest/organizations?q=vanityNameManage company pages and data for profile management and employee insights.
LinkedIn Posts API
/rest/postsJoin our product webinar on Thursday.
Handle rich media content for advanced publishing and media management. The Posts API replaces the legacy UGC Posts API.
LinkedIn Compliance API
No new accessReport policy violations and content issues for moderation and compliance.
Access levels from Getting access to LinkedIn APIs and the Posts API documentation (Microsoft Learn). Last verified: November 2026.
Important Most LinkedIn APIs require LinkedIn's approval
Only Sign In with LinkedIn and Share on LinkedIn are self-serve. Everything else requires LinkedIn's approval, usually through a partner program. Here's what you need:
LinkedIn API Approval Process: What to Expect
Getting approved for LinkedIn's official API access is a rigorous process. Understanding the timeline and requirements helps you prepare a successful application.
LinkedIn publishes no average approval time and no approval rate: access is granted at its discretion. Source: LinkedIn API Partner Support guide. Last verified: November 2026.
Key Requirements
Skip the wait with Unipile: get instant LinkedIn API access without the lengthy approval process.
Common rejection reasons and what to do if rejected
LinkedIn's partner support guide describes these cases and the way out of each one.
Vetting survey not completed
If the survey is not started, not submitted, or a request for more information goes unanswered within 21 days, the request is marked Insufficient Details. A Reapply option then appears in the Developer Portal, so you can resubmit for the same product without creating a new app.
Denied at identity vetting
Submit a Vetting Appeal through LinkedIn's developer support contact form, with your app's Client ID and the API program you are appealing for. LinkedIn's help center lists the denial reasons.
Use case outside the program
Ads API tier upgrade requests made only for data or analytics use cases are rejected: the Standard tier is needed only to create ads for more than 5 ad accounts, shown in a demo video.
Request button disabled
The Community Management API must be the only product on its app. If other products are provisioned or pending, create a new app on the same company Page and request it there.
Source: LinkedIn API Partner Support guide. Last verified: November 2026.
LinkedIn API Access: Who Can Use It and How to Get Approved?
Any LinkedIn developer app can add two self-serve products: Sign In with LinkedIn using OpenID Connect (profile and email) and Share on LinkedIn (posting as the signed-in member). Everything else, from advertising and community management to messaging, connections and talent integrations, requires LinkedIn's approval, usually through one of the partner programs below.
Marketing Developer Program
For Marketing technology companiesSales Navigator Solutions
For Sales technology providersTalent Solutions Partnership
For HR technology and ATS providersLinkedIn Learning Partner Program
For Learning management system providersA Sales Navigator subscription does not give API access. The Sales Navigator seat your users pay for and the Sales Navigator Application Platform (SNAP) are two separate things, and SNAP is not currently accepting new partners.
Sources: Getting access to LinkedIn APIs, LinkedIn Sales Solutions. Last verified: November 2026.
What You Can and Can't Do with LinkedIn APIs: DIY Approach
The LinkedIn API allows you to access structured data, post content, and manage profiles, but it comes with restrictions. You may face rate limits, need user permissions, and only gain access to certain features if you're a partner. The approval process can be time-consuming and limit your ability to implement custom solutions without LinkedIn's authorization code.
What You Can Do
What You Can't Do
Need → available with the official API?
| Need | Official API | What it takes |
|---|---|---|
| Sign members in with LinkedIn | Self-serve | Sign In with LinkedIn using OpenID Connect (openid, profile, email) |
| Publish posts on behalf of a member | Self-serve | Share on LinkedIn (w_member_social) |
| Send messages | Approval | Messages API, approved partners only: first-degree connections, each message tied to a specific member action |
| Read a member's connections | Approval | Connections API, approved developers only, under the data restrictions of their agreement |
| Sales Navigator data | Closed | SNAP is not currently accepting new partners |
Sources: Getting access, Messages API, Connections API, Sales Solutions (Microsoft Learn). Last verified: November 2026.
3 Ways to Access LinkedIn Data: Official API vs Alternatives
Accessing LinkedIn data for your application can be challenging due to LinkedIn's restricted API access. There are several ways to access LinkedIn data to perform tasks such as searching for profiles, searching for companies, sending invitations, sending voice notes, or sending InMails. By comparing endpoints, effort, cost, and flexibility, this table helps you clearly evaluate what's best for your team.
Unipile API
All-in-one unified API
LinkedIn Partners
Official API through partnership
Do It Yourself
Build your own solution
Which route fits what you are building?
| You are building | Route | Why |
|---|---|---|
| CRM | Unipile | The official Messages API is limited to approved partners; Unipile syncs each connected user's own LinkedIn conversations and contacts. |
| ATS or recruiting tool | Partner program Unipile | Recruiter System Connect and Apply Connect need Talent partner approval; Unipile acts on behalf of each recruiter's own account, including Recruiter seats. |
| Prospecting or sales engagement tool | Unipile | SNAP is not accepting new partners; Unipile works with each user's own LinkedIn and Sales Navigator account. |
| AI agent | Unipile | The agent acts for one authenticated user, through the Unipile API or the LinkedIn MCP server. |
| Content publishing | Official API | Share on LinkedIn is self-serve for member posts; company Page posts need the Community Management API (approval). |
Unipile is not a LinkedIn product and holds no partnership with LinkedIn. Its role is to sit as an independent technical layer between your application and LinkedIn, executing each call on behalf of an end user who has personally connected their own account. Every request stays within the boundaries of that user’s own LinkedIn permissions. No elevated access, no other accounts, no action outside the workflow the user has explicitly started.
1. LinkedIn API by Unipile
A production-ready LinkedIn API that acts on behalf of each connected user without the complexity of the Partner Program.
Why Choose Unipile?
How It Works
Get Started in 5 Simple Steps
Create Your Unipile Account
Sign up in seconds and get immediate access to the Unipile Messaging API.
Access Your Dashboard
Manage all your connected accounts, webhooks, and API settings in one place.
Get your DSN
Copy your unique DSN endpoint to start making API calls.
Generate a Token
Configure scopes and permissions for secure API access.
Connect LinkedIn Account
Link your LinkedIn account using credentials or cookies method.
Now Integrate All the Features You Need
Access every LinkedIn functionality through our unified API. Choose the endpoints that match your use case.
Popular Endpoints
Video Guide: Build with LinkedIn API
In this video, learn how to connect a LinkedIn account and start syncing inboxes, retrieving profiles, and managing conversations from your app.
2. Official LinkedIn API
While LinkedIn's official API offers the most comprehensive and legally secure access to LinkedIn data, it comes with significant barriers to entry that make it unsuitable for most developers and businesses.
LinkedIn Official API: Developer Guide
LinkedIn's API offers powerful integration options but is tightly controlled. Any app can add two self-serve products, Sign In with LinkedIn using OpenID Connect and Share on LinkedIn; everything else is only available with LinkedIn's approval, usually through a partner program. Approved partners gain access to specific APIs, such as the Profile API, Connections API, and Posts API (which replaces the UGC Posts API), which allow for profile data access, content sharing on behalf of users, and network connections.
To build an application, developers must create a LinkedIn developer account. The complexity of using LinkedIn's APIs, which are constructed on the Rest.li framework, requires understanding the provided library that simplifies requests and handles authentication.
Two key OAuth methods include: Sign In with LinkedIn (requires user permission for profile data) and Profile API (reserved for approved partners with more extensive access).
OAuth Process for Access
Get Approved by LinkedIn
Obtain Access Tokens
Use your Client ID and Client Secret to request an access token for authenticated API calls.
const getAccessToken = async () => { const response = await axios.post( 'https://www.linkedin.com/oauth/v2/accessToken', { grant_type: 'client_credentials', client_id: 'your-client-id', client_secret: 'your-client-secret' } ); return response.data.access_token; };
Fetch Profile Data
Make API requests to retrieve profile data. Note: LinkedIn API requires a profile ID for data retrieval.
const getProfile = async (accessToken, profileId) => { const response = await axios.get( `https://api.linkedin.com/v2/people/${profileId}`, { headers: { 'Authorization': `Bearer ${accessToken}` } } ); return response.data; };
LinkedIn's official API only allows fetching profile data using a profile ID. If you only have a LinkedIn profile URL or slug, the official API won't be helpful. In such cases, using an unofficial API like Unipile can be a solution, as it enables the retrieval of LinkedIn data using both the profile ID and profile URL.
LinkedIn Official API Limitations
Major restrictions that make it impractical for most use cases:
Set up the official LinkedIn API step by step
- Create the app. In the LinkedIn Developer Portal, open My Apps, click Create App and fill in the app details.
- Associate a company Page and get it verified. The Page acts as the publisher of the app, and a super admin of that Page must approve the verification request sent from the app's Settings tab.
- Request products in the Products tab. Sign In with LinkedIn using OpenID Connect and Share on LinkedIn are added self-serve. Products that need vetting open a survey to submit within 21 days.
- Configure OAuth. The Auth tab shows your Client ID and Client Secret; add your HTTPS redirect URLs there.
- Make a first call. With a member access token, call
GET https://api.linkedin.com/v2/userinfoto read the signed-in member's name, picture and email.
How LinkedIn OAuth works
3-legged OAuth (member authorization)
The member approves your app on a LinkedIn consent screen. Your app exchanges the authorization code for an access token, then calls the API on that member's behalf.
2-legged OAuth (client credentials)
Your app authenticates as itself, for APIs that are not member specific. Your app cannot access these APIs by default: LinkedIn has to grant them.
- The authorization code lives 30 minutes and must be used immediately.
- Access tokens last 60 days (
expires_in: 5184000). - Programmatic refresh tokens exist only for a limited set of partners and last 365 days; everyone else sends the member through OAuth again.
- Requesting a different scope than the one previously granted invalidates all previous access tokens.
- Self-serve scopes:
openid,profileandemail(Sign In with LinkedIn using OpenID Connect),w_member_social(Share on LinkedIn). r_liteprofileandr_emailaddressbelonged to the legacy Sign In with LinkedIn, deprecated on August 1, 2023, and are replaced byopenid,profileandemail.
Versioning
Versioned APIs live under https://api.linkedin.com/rest/ and expect a Linkedin-Version header in YYYYMM format, for example Linkedin-Version: 202611. Each monthly version is supported for at least one year, the latest version is never applied by default, and a missing or sunset version header returns an error. The Posts API also requires X-Restli-Protocol-Version: 2.0.0.
Errors you will hit
| Code | What it means | What to do |
|---|---|---|
| 401 Unauthorized | The access token is missing, invalid, expired or revoked by the member. | Send Authorization: Bearer {token}; refresh an expired token or have the member authenticate again. |
| 403 Access denied | The token lacks the permission for that API. | Check the product shows Approved in the Products tab, request the right scopes, and confirm the member's role on the Page or ad account. |
| 429 Rate limit | The daily application or member limit for that resource is reached. | Cut redundant calls and review Usage & Limits in the Developer Portal; partners can contact LinkedIn about higher limits. |
Sources: Partner Support guide, Page verification, Authorization Code Flow, Client Credential Flow, Refresh tokens, Sign In with OpenID Connect, legacy Sign In, Versioning, Error handling, Rate limits. Last verified: November 2026.
How much does the LinkedIn API cost?
The self-serve products, Sign In with LinkedIn and Share on LinkedIn, cost nothing to use. Partner programs are granted case by case, and LinkedIn's developer documentation publishes no price list for them. A Sales Navigator subscription does not include API access. For the details, see how LinkedIn API pricing works and whether the LinkedIn API is free.
Before you go live
Plan for token expiry
Access tokens last 60 days, and refresh tokens are only offered to a limited group of partners. Ask members to reauthorize before expiry, and again after any scope change, which invalidates existing tokens.
Pin your API version
Send an explicit Linkedin-Version header and schedule upgrades: each monthly version is supported for at least one year, then calls to a sunset version fail.
Handle daily limits
Limits apply per application and per member and reset at midnight UTC. Treat a 429 response as a signal to back off, and spread calls over the day.
Keep only the data you need
LinkedIn's API Terms let you store member data only as long as needed to serve your users, and require deletion when a member asks or closes their account.
Sources: Authorization code flow, Versioning, Rate limits (Microsoft Learn) and the LinkedIn API Terms of Use, sections 4.1 and 4.4. Last verified: November 2026.
3. DIY LinkedIn Integration
If the official LinkedIn API doesn't meet your needs, particularly when you need to retrieve data using a LinkedIn profile URL or slug, unofficial APIs found on platforms like GitHub can serve as an alternative. These libraries allow you to interact with LinkedIn without the restrictions imposed by the official API.
Why DIY Integration Is Risky
These integrations are often long, complex, and unofficial, meaning there is no official support available. Developers should expect numerous iterations and challenges during implementation. Additionally, using LinkedIn as an OAuth provider has its limitations, as it does not supply the key data many applications need.
Common Challenges
Better Alternatives to DIY Integration
Instead of building your own LinkedIn integration, consider these production-ready solutions:
LinkedIn API Capabilities with Unipile
Access every LinkedIn endpoint through a single, unified API. From messaging to profiles, invitations to posts, build any LinkedIn integration your users need.
Account Connection
2 endpoints available
Messages
10 endpoints available
Users/Profiles
8 endpoints available
Posts/Comments
6 endpoints available
Specific
17 endpoints available
Webhooks
3 events available
Inboxes
4 inboxes available
LinkedIn API Python Integration: Quick Start
Integrate LinkedIn into your CRM, ATS, or sales engagement tool in minutes. Below is a Python example to list all connected LinkedIn accounts using the Unipile API. No SDK needed, just Python and requests.
import requests # Your Unipile API endpoint url = "https://api1.unipile.com:13111/api/v1/accounts" # Headers for authentication headers = { "accept": "application/json", "X-API-KEY": "your-api-key" } # Make the request response = requests.get(url, headers=headers) # Print all connected accounts print(response.json())
Key Features of LinkedIn API by Unipile
List All Chats
curl --request GET \ --url https://api1.unipile.com:13111/api/v1/chats \ --header 'X-API-KEY: {your_api_key}'
Retrieve all chat messages from a user's LinkedIn account. Filter conversations by chat partner, date, or keywords within the chat content.
Start New Chat
curl --request POST \ --url https://api1.unipile.com:13111/api/v1/chats \ --header 'X-API-KEY: {your_api_key}' \ --header 'Content-Type: application/json' \ --data '{"attendee_id": "...", "text": "..."}'
Initiate a new chat message within your application, providing the recipient, message content, and optional attachments if supported.
Retrieve a Profile
curl --request GET \ --url https://api1.unipile.com:13111/api/v1/users/{user_id} \ --header 'X-API-KEY: {your_api_key}'
This API function facilitates the retrieval of user profiles, enabling detailed access to user information. You can gather a wealth of public profile information, such as the user's email, job title, company, phone number, and address, whenever they are provided and publicly available.
How Can Developers Leverage LinkedIn API for Advanced Features?
Integrating advanced LinkedIn features into your applications is now a streamlined process with Unipile's ready-to-use code snippets. Developers can sidestep the complexities of building from the ground up, using these pre-crafted codes to access the full capabilities of the LinkedIn API.
Whether for streamlining profile data retrieval, analyzing network activities, or syncing with other systems, Unipile's robust code repository acts as a catalyst for quick and smooth integration.
Build LinkedIn Engagement Sequences in Your App
Enable your users to build engagement workflows with personalized LinkedIn invitations. Search for profiles using LinkedIn or Sales Navigator, apply filters, and let each user run the sequence from their authenticated account. The sequence is built inside your own application from Unipile calls (send an invitation, send a message, send a follow-up); it is not a ready-made module of the API.
Search and Retrieve Results
Leverage the advanced features of LinkedIn, LinkedIn Recruiter, and LinkedIn Sales Navigator to build custom search functionalities within your application, using the 'Get raw data' endpoint through each user's authenticated account.
Detecting Accepted Invitations
Track when your LinkedIn invitations are accepted to trigger follow-up actions without specific webhooks.
Voice Note Integration
Incorporating LinkedIn's voice note feature into your software can greatly enhance user interaction and engagement. This integration allows users to easily send and receive voice messages, offering a more personal and effective way to communicate.
With Unipile, your app sends a voice note on behalf of the connected user by attaching an audio file in the voice_message field of a new or existing chat. The note is sent from the user's own LinkedIn account and appears in the conversation like any other message. Parameters and setup are covered in our guide to sending LinkedIn voice notes through the API.
Get LinkedIn Posts
Access your users' latest LinkedIn posts directly in your app. Retrieve titles, timestamps, and content snippets to power real-time dashboards, CRM cards, or automated alerts.
Get LinkedIn PostsLinkedIn’s usage policies and rate thresholds evolve over time. Unipile surfaces the live platform signals your integration needs: usage headers, quota hints, error codes, so your workflows can slow down, back off, or re-schedule automatically. Responsibility for the overall cadence stays on the customer side. Each implementation must stay aligned with LinkedIn’s current terms and with what a single authenticated account can legitimately do.
LinkedIn API Use Cases: Unleashing the Potential
The LinkedIn API serves as a transformative tool, reshaping how individuals and organizations work across various industries. To recruit and sell faster, your users need to respond promptly to messages. With the API, each of your users can connect multiple LinkedIn accounts to support their workflows.
API for LinkedIn Recruiter
In the realm of recruitment, the Unipile's LinkedIn API is a transformative tool, reshaping the landscape for hiring professionals. The API for LinkedIn Recruiter and others streamlines candidate targeting, automates tedious tasks, and provides real-time insights.
API for LinkedIn Sales Navigator
Incorporating LinkedIn Sales Navigator into your CRM transforms sales strategies by providing direct access to valuable insights and connections. This fusion allows for personalized engagement, tailored to the unique needs of each prospect.
Benefits of LinkedIn API Integration
A production-ready SDK that handles the complexity of LinkedIn integration. RESTful endpoints, real-time webhooks, and automatic rate limiting, so you can focus on building, not maintaining.
Simple Integration
Search profiles, send invitations and messages with just a few lines of code. Our SDK handles authentication, rate limits, and error handling.
// Connect to LinkedIn in seconds import { UnipileClient } from 'unipile-node-sdk'; const client = new UnipileClient({ dsn: 'https://api.unipile.com', token: process.env.UNIPILE_TOKEN }); // Search LinkedIn profiles const profiles = await client.users.search({ query: 'Marketing Director', limit: 25 }); // Send connection invitation await client.users.invite({ account_id: accountId, provider_id: 'linkedin_user_id', message: 'Hi! Let\'s connect.' });
RESTful API
Clean, standardized endpoints with JSON responses. Predictable URL structure and HTTP methods.
Real-time Webhooks
Instant notifications for messages, connection acceptances, and events. No polling required.
Secure Authentication
OAuth 2.0 token-based authentication. Secure credential management and automatic token refresh.
Account Protection
Built-in safeguards to protect LinkedIn accounts. Respectful usage patterns and activity limits aligned with platform guidelines.
Smart Rate Limiting
Automatic rate limit management with informative headers. We handle LinkedIn's restrictions for you.
Clear Error Handling
Descriptive error codes and messages. Built-in retry logic with exponential backoff.
One dashboard for all your integrations
Manage all your LinkedIn, WhatsApp, Gmail accounts and more from a single, intuitive interface.
Accounts
03/01/2025
02/15/2025
02/10/2025
03/01/2025
02/28/2025
02/20/2025
03/01/2025
02/25/2025
03/01/2025
02/22/2025
02/14/2025
02/12/2025
02/08/2025
02/05/2025
03/01/2025
02/15/2025
03/01/2025
02/22/2025
Optimize Your Integration with Experts Support
Whether you're starting from scratch or already have a system in place, our integration process is made to get you live fast.
Start Building with LinkedIn API Today
Choose the integration path that fits your timeline and needs.
LinkedIn API Guide FAQ
Everything you need to know about accessing and integrating LinkedIn API
Partially. Basic access to limited data costs nothing, while most other LinkedIn products require partner approval, and Unipile is billed as an API plan per connected account. See the full breakdown in Is the LinkedIn API free?
There are three main paths to LinkedIn API access:
- LinkedIn Partner Program (approval at LinkedIn's discretion, no published timeline)
- Third-party API providers (1-3 days, most businesses)
- DIY development (not recommended for production)
To get a fast access, you need to create a LinkedIn Developer account and register your application. Depending on the data and level of access you require, you may need to go through LinkedIn's partner application process, which can involve submitting your use case for review. Alternatively, you can connect to the Unipile dashboard for simplified access and management.
It depends on the API provider. Here's a comparison between LinkedIn's official OAuth and Unipile's simplified approach:
Unipile LinkedIn API:
// Simple token-based authentication const response = await fetch('https://api.unipile.com/v1/profiles', { headers: { 'Authorization': 'Bearer your-api-token', 'X-DSN': 'your-dsn-endpoint' } });
Yes. LinkedIn caps the calls an application and each member can make per day, resets the counters at midnight UTC, and returns a 429 error when a limit is reached; your app's figures are under Usage & Limits in the Developer Portal. Limits by endpoint, and how Unipile paces calls per connected account, are in our guide to LinkedIn API rate limits.
Available data depends on your access method and user permissions:
Profile Data:
- Name, headline, location
- Work experience and education
- Skills and endorsements
- Contact information (if shared)
- Profile photo and background
Activity Data:
- Posts and articles
- Comments and reactions
- Connection updates
- Job changes and announcements
Network Data:
- Connections list
- Mutual connections
- Follower count
- Network activity
You can pull various types of data using the LinkedIn API, including:
- User profile information (name, headline, location, etc.)
- Posts and shares from a user's LinkedIn feed
- Company information if you have proper permissions
- Engagement metrics like comments, likes, and shares on posts
Note that the specific data available depends on LinkedIn's API tiers and your permissions. For a detailed breakdown of LinkedIn data pull from API, visit the full article on what LinkedIn data can be pulled from their API.
The available routes differ mainly in how they authenticate and how far they scale:
- Manual browsing and copy-paste: fine for a handful of records, does not scale
- Browser extensions: tied to LinkedIn's live markup, and they break whenever the front end changes
- Cloud tools on shared infrastructure: you do not control the sessions they run on
- Account-based API: each end user links their own account, and every retrieval runs on their behalf
We compare what each approach can reach, where it breaks, and what it exposes you to, in our guide to getting LinkedIn data into your software.
To learn how to efficiently get LinkedIn posts using API, including step-by-step instructions and integration tips, check out our detailed guide here: How to Get LinkedIn Posts Using API.
LinkedIn publishes no price for its recruiting APIs: Recruiter System Connect and the Job Posting API are reserved for approved Talent Solutions partners, under terms set in each partner agreement. With a user-side integration, each recruiter keeps their own Recruiter seat and your company pays an API plan per connected account, with no fee per search or per message. See the full breakdown in our LinkedIn Recruiter API guide.
The Unipile API streamlines LinkedIn integration by generating an authorization link, enabling users to connect LinkedIn accounts, manage communications, and access various LinkedIn features directly. This process eliminates the need for complex code, making integration fast and efficient.
Any Python HTTP client works with LinkedIn's REST endpoints, but the official API is limited to its self-serve products unless you are an approved partner. Most teams call the Unipile REST API from Python to act on behalf of each connected user. Code samples are in our LinkedIn API Python guide.
The LinkedIn API allows developers to integrate LinkedIn features into their applications. Common functionalities include retrieving user profiles, sharing posts, accessing company pages, and integrating LinkedIn Ads or Sales Navigator features.
LinkedIn API can be used with any programming language that supports HTTP requests:
Most popular languages:
- Python: Extensive libraries and examples available
- JavaScript/Node.js: Great for web applications
- PHP: Popular for WordPress and web development
- Java: Enterprise applications and Android development
- C#/.NET: Microsoft ecosystem integration
- Ruby: Rapid prototyping and web applications
The limitations and constraints of the LinkedIn API are specified by LinkedIn itself, and they vary according to the endpoints and types of usage allowed. See LinkedIn API rate limits for the details.
Unipile retrieves information on behalf of authenticated users, at their request and within their authorized scope. No data is stored independently by Unipile; information flows through the API in response to user-initiated actions, in compliance with GDPR and applicable data protection regulations.
Unipile is an independent technical intermediary that helps software publishers connect authenticated user accounts to their applications. Supported actions are performed on behalf of the user, within workflows initiated and controlled by that user. Unipile is not affiliated with, endorsed by, or sponsored by LinkedIn. Whether and how to use LinkedIn data in your product remains a customer-side decision, under LinkedIn's terms. Third-party platform features, availability, and access conditions may change at any time.
No. Unipile does not build or maintain any independent database of LinkedIn profile data for its own purposes. Any profile information retrieved through the API is handled only on behalf of the authenticated user, at that user's request, and only to the extent technically necessary for the workflow your application executes. Once the workflow is complete, Unipile does not retain or repurpose the data outside of what the user has initiated.
The Unipile LinkedIn API exposes only the information that the authenticated user could themselves view from their own LinkedIn session. This includes profiles in their network, their messages, their Sales Navigator or Recruiter data when those seats are attached to the account, and the public-facing company pages they can already browse. There is no privileged backend access, no cross-account enrichment, and no scope beyond what the user's own LinkedIn account is authorised to see.
Every action performed through the Unipile LinkedIn API requires the end user to have explicitly connected their LinkedIn account via authentication. Actions are triggered only inside workflows the user has initiated and controls. No background collection runs without an authenticated session, no action is performed on accounts whose owner has not actively linked them through your application.
LinkedIn's official API documentation is hosted on Microsoft Learn at learn.microsoft.com/linkedin, organized by product family: Consumer, Marketing, Sales, Talent, Learning and Compliance. Your apps, products and credentials are managed in the LinkedIn Developer Portal. Unipile's LinkedIn endpoints are documented in the Unipile developer docs.
Create an app in the LinkedIn Developer Portal (My Apps, then Create App) and associate it with a LinkedIn Page. The Auth tab then shows your Client ID, which LinkedIn also calls the API key, and your Client Secret. These credentials only unlock the products added in the Products tab: the two self-serve ones right away, the others after LinkedIn's approval.
Not in the self-serve products, whose open permissions cover sign-in and posting only. The search experience LinkedIn offers partners sits in the Sales Navigator Application Platform, which is not currently accepting new partners. With Unipile, your app runs LinkedIn and Sales Navigator searches on behalf of each connected user, within what that user's own account can see.
Yes, when the agent acts for a member who has authorized it. The official rules still apply: the Messages API, for example, requires each message to be tied to a specific member action, never an automated or scheduled event. Unipile gives agents LinkedIn actions on behalf of each connected user through its API and the LinkedIn MCP server.
r_liteprofile and r_emailaddress belonged to the legacy Sign In with LinkedIn product, deprecated on August 1, 2023. They are replaced by Sign In with LinkedIn using OpenID Connect and its scopes openid, profile (name and profile picture) and email. The member's details come from the ID token or from GET https://api.linkedin.com/v2/userinfo.
Yes, but the official Messages API is restricted to approved partners: it sends messages to first-degree connections, and each message must be tied to a specific member action. Unipile lets your app send and receive LinkedIn messages on behalf of each authenticated user, from their own account. See our LinkedIn messaging API page.
None of the Talent APIs LinkedIn documents is a job search endpoint: they cover job posting, applications (Apply Connect, Apply with LinkedIn) and recruiter system sync, all reserved for approved partners. The Job Posting API is not currently accepting new partners, and LinkedIn points new requests to Apply Connect. Unipile lets your app create, publish and manage job posts from each connected recruiter's account: see the LinkedIn Job Posting API page.
LinkedIn publishes no average approval time. The published deadlines are 21 days to submit the vetting survey, after which the request is marked Insufficient Details, and up to 30 business days for the review of an Ads API tier upgrade. Approval stays at LinkedIn's discretion.
LinkedIn's API Terms of Use set no fixed number of days. Where storage is allowed, you may keep Content only for the duration necessary to provide your application's services to your users, stored so that it can be identified and selectively deleted. You must delete it immediately when the user asks or closes their account; see section 4 of the LinkedIn API Terms of Use.
Ready to integrate LinkedIn API into your product?
Build Now


