How Do You Get LinkedIn API Access in 2026?
If your use case is login or basic identity: go to developer.linkedin.com, create an app linked to a verified LinkedIn Company Page, and enable the Sign In with LinkedIn product. Access is immediate. If your use case is ad management, campaign analytics, or page management: apply for the Marketing Developer Platform (MDP). Create an app, submit a use-case description with privacy policy and product demo, and wait for LinkedIn's manual review. Timeline: 4 to 8 weeks on the fast path; 3 to 4 months is more common. If your use case is creator profile data, follower counts, or audience demographics without applying for a partnership: a third-party unified API like Phyllo provides this data through creator-authenticated OAuth without requiring your platform to hold LinkedIn partner status.
What LinkedIn API Access Tiers Exist in 2026?
LinkedIn does not offer a single unified API. Access is split across five distinct product tiers, each with its own eligibility requirements, approval path, and data scope. Understanding which tier maps to your use case before you apply will save significant time.
A few things the table above does not capture:
- LinkedIn does not publish official pricing for MDP access. The $699+/month figure is an informed market estimate based on reported partner disclosures, not a published list price.
- The Sales Navigator API (SNAP) is explicitly not accepting new partner applications as of 2026. LinkedIn's developer portal states they are periodically reviewing onboarding capacity. Existing SNAP partners retain access; everyone else is locked out indefinitely.
- Even within the free Consumer tier, data scope is narrow. Name, profile photo, and headline - that is effectively the full dataset available without partner approval. Follower counts, engagement metrics, and audience demographics are not accessible on any free tier.
- The Advertising API within MDP has its own sub-tiers: Development (POST for up to 5 ad accounts, GET for unlimited accounts) and Standard (no account limit). LinkedIn reserves the right to decline Standard tier upgrades even if you meet the stated requirements.
Marketing Developer Platform: Who Qualifies?
The Marketing Developer Platform is LinkedIn's API tier for companies building ad management tools, campaign reporting integrations, company page analytics dashboards, and lead generation workflows. It is the tier that gives you access to the Campaign Management API, Reporting API, Audience Insights, Lead Sync, Conversions API, and Page Management capabilities.
LinkedIn's official terms describe MDP as open to "qualified developers" - but that phrasing is deliberately vague. In practice, LinkedIn approves applications from:
- Established marketing technology platforms with an existing product and a verifiable customer base.
- Ad agencies and marketing services companies building tools for their own managed-service clients (not for general resale).
- Analytics and reporting tools that aggregate LinkedIn campaign data within a broader multi-channel dashboard.
- Platforms building LinkedIn Lead Gen Form integrations for CRM or marketing automation workflows.
LinkedIn routinely rejects applications from:
- Competitive intelligence tools or platforms whose output could substitute for LinkedIn's own paid products (Sales Navigator, Talent Insights).
- Data enrichment services that intend to store or resell LinkedIn data beyond the approved integration use case.
- Lead generation platforms - LinkedIn explicitly protects this segment as part of its Sales Navigator revenue model.
- Applications where the use case description is vague, the privacy policy is thin, or the product demo does not clearly show how LinkedIn data will be used and surfaced.
One critical point from LinkedIn's own API terms: approval is not a guarantee even if you meet the stated requirements. LinkedIn "reserves the right to review applications and select partners at its discretion." Meeting the eligibility criteria moves your application forward; it does not guarantee approval.
The Approval Process, Step by Step
There is no single "apply" button for the Marketing Developer Platform. The process runs across several steps, and the order matters - missing a prerequisite at any stage sends you back to the start.
Step 1: Create a LinkedIn Developer account
Go to developer.linkedin.com and sign in with a LinkedIn account. You will need a verified company LinkedIn Page associated with your application. Personal accounts are not eligible. If your company page does not yet exist, create it before starting - verification is required before you can proceed.
Step 2: Register your application
In the Developer Portal, create a new app. You will need: a verified Company Page URL, an application name and logo (minimum 100 x 100 px), a full privacy policy URL (not a placeholder - LinkedIn reviews this), and agreement to the API Terms of Use. After submission, LinkedIn generates a verification request to confirm the link between your app and the company page.
Step 3: Request the Marketing Developer Platform product
Under the Products tab of your registered app, request access to the Marketing Developer Platform. This triggers the formal review process. You will be asked to provide a detailed description of your use case, the specific MDP APIs you intend to use, how LinkedIn data will be processed and stored, and a demo video or working product demonstration.
Step 4: Complete privacy and security vetting
LinkedIn's review includes an assessment of your privacy and security practices, not just your use case. The review may include follow-up questions about your data storage architecture, user consent flows, and what happens to LinkedIn data when a user revokes access. Having documented answers to these questions before the review begins significantly reduces back-and-forth time.
Step 5: Await LinkedIn's decision
LinkedIn does not publish a target review timeline and explicitly states in its Marketing Developer Terms that it makes no commitment to any specific response timeframe. Once a decision is made, you will receive either an approval (with access to the requested API products) or a rejection (which may or may not include a stated reason).
Step 6: For the Advertising API, apply for Standard tier separately
If your use case requires Standard tier access to the Advertising API - necessary for managing more than 5 ad accounts - you must apply for a tier upgrade separately after receiving initial MDP approval. Standard tier requires demonstrating active usage and meeting minimum qualification thresholds. LinkedIn again reserves the right to decline even if thresholds are met.
How Long Does Approval Really Take?
LinkedIn does not publish target timelines. Based on reported developer and agency experience across the ecosystem in 2025 and 2026, the realistic range is:
The 4-to-8-week timeline is the exception rather than the rule. Most teams building net-new integrations in 2026 should plan for a 3-to-4-month runway before they can rely on MDP access for a production feature. If your product launch timeline cannot absorb that wait, evaluate the alternatives in the final section of this post before starting the application.
One practical note on speeding things up: LinkedIn's review team responds to completeness, not persistence. Applications that arrive with a working product demo, a clearly articulated data flow, a comprehensive privacy policy, and specific answers to how LinkedIn data will be used and protected move faster through review than applications that are vague on any of those points. Resubmitting a rejected application without substantively changing it does not improve the outcome.
What Happens If You Are Rejected?
LinkedIn does not guarantee that a rejection will include an explanation. In many cases, the notification is a brief message that your application was not approved, with no detail on the specific reason.
The most common rejection patterns, based on reported developer experiences, are:
- Use case overlap with LinkedIn's paid products - any application that could substitute for Sales Navigator, Recruiter Lite, or Talent Insights is likely to be declined. LinkedIn actively protects these revenue lines through its API approval process.
- Data enrichment or resale intent - applications that describe using LinkedIn data to build or enrich a third-party database, even if framed as an analytics use case, are high-rejection-risk.
- Insufficient privacy policy - a privacy policy that does not address LinkedIn data specifically, that contains placeholder text, or that lacks a clear data deletion mechanism will typically fail the vetting stage.
- Unclear or absent product demo - LinkedIn's review includes evaluating how your product actually surfaces LinkedIn data. An application without a working demo, or with a demo that does not clearly show the LinkedIn integration, leaves the reviewer unable to assess compliance.
If rejected, you can reapply. Before doing so, address the underlying issue rather than resubmitting the same application. If you can identify the rejection reason from the notification, fix it directly. If no reason was given, conduct a self-audit against the four patterns above - most rejections trace back to one of them.
For teams with use cases that fall outside what LinkedIn approves - particularly those needing creator profile data, follower analytics, or audience demographics for influencer marketing or creator economy platforms - the official MDP approval path may simply not be the right route. The next section covers why.
Restricted Endpoints and Data Gaps
Even with full Marketing Developer Platform approval, LinkedIn's API has meaningful data gaps that affect specific use cases. Understanding these before you invest in the approval process will help you avoid building against endpoints that do not exist.
What MDP access does not include
- Follower demographics by age, gender, or geography for individual creator profiles. These are not exposed through any commercial API tier.
- Engagement rates at the creator or content level. Impression and reach data is available for company pages via the Community Management API, but not for individual member profiles at scale.
- People search or profile search at volume. The People Search API is restricted; commercial use cases for searching LinkedIn members programmatically are not supported on the commercial tier.
- Connection graph or network data. LinkedIn does not expose connection-level data through its API for non-personal use cases.
- Direct messaging or InMail at scale. The Messaging API is not part of MDP and is not available for commercial integrations.
What changed in 2025–2026
- The r_liteprofile scope has been replaced by r_basicprofile in current API versions. Apps still using the older scope need to migrate to avoid breaking changes.
- LinkedIn deprecated Marketing Version 202501 (January 2025 versioned release). Teams on this version are required to migrate to the latest versioned APIs to avoid service disruption.
- The Member Post Analytics API, introduced in 2025, added individual member-level reach and impression data for the first time - accessible through trusted third-party platforms. This partially addresses the historical gap in personal profile analytics, though it requires platform-level approval and remains limited in scope.
- Rate limits have become stricter across data-heavy endpoints. The default application-level limit is 100,000 API calls per day, but individual endpoints can be significantly lower - as few as 10 requests per day per member on some endpoints. LinkedIn does not offer self-serve limit increases beyond what is negotiated at the partner tier.
Related Reading:
For a full breakdown of LinkedIn API pricing across all tiers - including estimated costs for MDP, Recruiter System Connect, and Sales Navigator - see How Much Does the LinkedIn API Cost? Pricing Explained on the Phyllo blog.
The Alternative: Phyllo's LinkedIn Data Layer
For platforms that need LinkedIn creator profile data, follower counts, engagement metrics, or audience demographics - and cannot wait 3 to 4 months for partner approval, or whose use case falls outside what LinkedIn approves - Phyllo provides a LinkedIn data layer that operates through creator-authenticated OAuth rather than a LinkedIn partner agreement.
When a creator connects their LinkedIn account through Phyllo's connect flow, Phyllo retrieves their profile data, content performance metrics, and audience insights on their behalf. This data is returned through a single API endpoint that works identically regardless of whether the creator is also on Instagram, TikTok, YouTube, or any of the other platforms Phyllo supports.
What Phyllo's LinkedIn data layer provides
- Creator profile data - name, headline, follower count, connection count, and profile verification status.
- Content performance data - impressions, reach, engagement metrics, and video watch time for posts the creator has authorised access to.
- Audience demographics - age range, gender breakdown, and geographic distribution for authenticated creator accounts.
- Cross-platform normalisation - the same data schema applies to LinkedIn, TikTok, Instagram, and 100+ other platforms, so your platform does not need separate data models per network.
- Token lifecycle management - LinkedIn access tokens expire after 60 days. Phyllo handles refresh logic automatically, removing the most common cause of silent production failures in LinkedIn integrations.
What it is not
Phyllo's LinkedIn data layer is an OAuth-permissioned data retrieval layer for platforms serving creators and influencer marketing use cases. It is not a way to access LinkedIn's ad management APIs, run programmatic ad campaigns, or query LinkedIn members who have not authenticated. For ad-management and campaign-analytics use cases, the Marketing Developer Platform is the correct path.
For influencer marketing platforms, creator economy tools, and B2B analytics products that need LinkedIn creator data at scale - without the MDP approval timeline and without the data gaps listed above - Phyllo is the path most teams in 2026 are taking.
🔗 Explore Phyllo's LinkedIn APIs
See the full data coverage, authentication flow, and integration options at getphyllo.com/linkedin-apis.
FAQ for Developers
Is LinkedIn API access free in 2026?
Partially. Sign In with LinkedIn and the Share on LinkedIn product are free and available after app creation and a basic review. Any meaningful data - follower counts, audience demographics, engagement analytics, company insights, or ad management - requires Marketing Developer Platform or Partner-level access, which is application-gated and, at the MDP tier, estimated to start at $699+/month for approved partners. LinkedIn does not publish a price list.
How do I apply for the LinkedIn Marketing Developer Platform?
Go to developer.linkedin.com, create an app linked to a verified LinkedIn Company Page, and request the Marketing Developer Platform product under the Products tab. You will be prompted to submit a use case description, your privacy policy URL, and a product demo. LinkedIn manually reviews all applications. There is no published timeline for a decision.
Why was my LinkedIn API application rejected?
LinkedIn rarely states the reason for rejection. The most common causes are: use case overlap with LinkedIn's own paid products (Sales Navigator, Talent Insights), intent to build a data enrichment or resale product, an insufficient privacy policy, or a missing or unclear product demo. Address these specifically before reapplying.
Can I get LinkedIn API access without a partner application?
For creator profile data, follower counts, and audience demographics, yes - through a unified API like Phyllo, which retrieves this data via creator-authenticated OAuth without requiring your platform to hold LinkedIn partner status. For ad management, campaign analytics, and page insights, no - the Marketing Developer Platform approval is required.
Is the LinkedIn Sales Navigator API available in 2026?
No. LinkedIn has paused new partner onboarding for the Sales Navigator API (SNAP) as of 2026. Existing partners retain access. LinkedIn indicates it will update the developer portal when availability changes.
How long does LinkedIn API approval take?
LinkedIn does not publish a target timeline. Based on reported developer experience: 4 to 8 weeks on the fast path, 3 to 4 months as a typical outcome, and 6 months or longer for applications that require multiple rounds of review or fall close to LinkedIn's policy boundaries. Recruiter and Talent API partnerships typically take 4 to 6 months or more.
