---
title: "LinkedIn API: what you can actually get, and from whom"
description: "What the LinkedIn API really offers, who gets access and what is closed, plus the providers that return LinkedIn data or automate it through your account."
url: https://frontal.so/gtm-apis/linkedin-api
updated: 2026-11-12
---

By data · LinkedIn APIs

# LinkedIn API: *what you can actually get*

LinkedIn's own API opens sign-in and posting to every developer and gates the rest behind approval, so the profile and company data most teams want comes from one of the nineteen providers here, each of which gets there differently.

Short answer

For profile and company data by API, Apollo from $49 a seat, or [People Data Labs](https://frontal.so/gtm-apis/enrichment-apis/people-data-labs-api-review) where the data goes inside a product you sell. For actions on LinkedIn itself, [HeyReach](https://frontal.so/gtm-apis/sending-apis/heyreach-api-review) prices per sender from $79 and [Dripify](https://frontal.so/gtm-apis/sending-apis/dripify-api-review) puts the API on every plan, both acting through your own accounts.

See the 19 providers [All 52 GTM APIs](https://frontal.so/gtm-apis)

**19** providers compared here

**7** usable at zero cost

**2** bill per call, no floor

**17** ship an MCP server

The use case

## Does LinkedIn have an API? Yes, and it is not the one you want

Does LinkedIn have an API? It has several, documented on Microsoft Learn by business line: Consumer, Compliance, Learning, Marketing, Sales and Talent. What it does not have is the LinkedIn API most sales teams picture, one that takes a profile URL and returns a person, an email and a company.

Two permissions are open to every developer through self-service: Sign In with LinkedIn using OpenID Connect, which returns the signed-in member's own name, headline, photo and email, and Share on LinkedIn, which posts on that member's behalf. Everything else on the LinkedIn API access page needs approval, and three programs are closed to new applicants as this page is written.

So this page is in two halves. The first is LinkedIn's own API, product by product, read from LinkedIn's developer documentation and its User Agreement: what each product returns, who may apply, how auth and rate limits work, and what the terms say about scraping. The second is the 19 providers in this directory that work with LinkedIn data anyway, in three kinds, and what each one costs.

Every statement about LinkedIn below comes from LinkedIn's own pages, read on 23 October 2026. Every price comes from the provider's own pricing page, and each review carries the full rate card and the date it was read.

Product by product

## LinkedIn's own API, product by product

LinkedIn organizes its developer API by business line rather than by data type, and the line decides who may use it. The developer API LinkedIn publishes is mostly for marketing platforms, applicant tracking systems and learning platforms building an integration their customers asked for, not for a sales team that wants data out. A LinkedIn API integration, in LinkedIn's own sense, is one of those partner builds.

Read the list below as a map of who LinkedIn is building for. The two consumer products are open; every marketing, sales and talent product is a partner program with an application.

- **Sign In with LinkedIn using OpenID Connect.** Open to all. The openid, profile and email scopes return the signed-in member's id, name, photo and primary email. LinkedIn says it does not verify user identities and should not be marketed as such.
- **Share on LinkedIn.** Open to all. The w\_member\_social permission lets an app post, comment and like on behalf of the authenticated member, which is the whole of the LinkedIn posts API a developer can switch on without approval. Reading other people's posts is not part of it.
- **Verified on LinkedIn.** A Development tier and a Plus tier on the same endpoints: /identityMe for profile data, /verificationReport for verification status and, on Plus only, /validationStatus for bulk validation. This is LinkedIn's own LinkedIn profile verification API, and it reads members who sign in to your platform.
- **Marketing API family.** The LinkedIn advertising API for campaigns and reporting, Matched Audiences, Lead Sync, Events Management, the LinkedIn Conversions API and the LinkedIn Community Management API. All need approval.
- **Sales Navigator Application Platform (SNAP).** Display Services, Analytics Services and Sync Services for CRM partners. LinkedIn says it is not currently accepting new partners for access to the Sales Navigator API.
- **Talent Solutions.** Apply Connect, Apply with LinkedIn, the Job Posting API, CRM Connect and Recruiter System Connect, for applicant tracking and recruiting systems. This is what a LinkedIn Recruiter API means in practice: a sync between an ATS and Recruiter, applied for as a partner.
- **Learning.** The LinkedIn Learning API retrieves learning objects and learning activity reports, for integrations with LinkedIn Learning.
- **Compliance.** Activity retrieval for compliance monitoring and archiving. Closed: LinkedIn lists the permissions for reference and says access may not be requested.

None of those products takes another member's profile URL and returns that person, which is the single most important fact on this page.

Marketing

## The LinkedIn Marketing API: the part that is actually open to apply for

The LinkedIn Marketing API is where LinkedIn has built most of its developer program, and it is the family a GTM team is most likely to be approved for. LinkedIn describes it as APIs to create campaigns, report campaign performance, manage leads and grow a company Page.

The LinkedIn conversion API, which LinkedIn calls the Conversions API, streams conversion events from your server to LinkedIn so campaigns can be measured and optimized. It needs the rw\_conversions and r\_ads permissions plus an ad account role such as Account Manager or Campaign Manager.

The Community Management API manages company Pages and reads their analytics: follower statistics, page statistics, share statistics, social metadata on posts and video analytics, with member-level post statistics alongside. As a LinkedIn analytics API it covers your own Pages and posts, not anybody else's.

Two Marketing products are closed or restricted. The LinkedIn Company Intelligence API is a private API for previously approved developers and is not accepting new applications. Audience Insights and Media Planning go only to developers who meet additional criteria, assessed case by case with no fixed timeline.

If the job is ads, conversions or your own company Page, the Marketing API is the honest answer, and it is a partner application rather than a key you generate.

Access

## LinkedIn API access: open, approved, or closed

LinkedIn API access comes in three states, and the access page is explicit about each. Open permissions are added self-service from the Products tab of an app in the Developer Portal. Partner programs need an application and LinkedIn's approval. Closed programs are listed for reference and cannot be requested.

The approved programs also have tiers. Every app starts on Development and applies separately for Standard, and LinkedIn says it may decline an upgrade even when the minimum requirements are met.

- Advertising API, Development tier: unlimited reads on ad accounts you administer, one test ad account created through the API, and edits on up to 5 ad accounts. Standard removes the account limits and is requested through a support ticket.
- Community Management API, Development tier: 500 calls an app and 100 calls per member of an app per 24 hours, no BATCH\_GET calls, and twelve months to finish building. Standard is the full program with no restrictions.
- Closed as this page is written: new SNAP partners, the Company Intelligence API and the Compliance permissions.

The practical reading is that LinkedIn grants access to products that serve its advertisers, recruiters and learners, and the approval process is how it decides which integrations those are.

Profile data

## LinkedIn profile lookup API: the Profile API, read closely

The LinkedIn Profile API is the one people expect to be a LinkedIn profile lookup API, and its own page says otherwise. Use of it is restricted to developers approved by LinkedIn and subject to the data restrictions in their agreements. It returns a member's profile subject to that member's privacy settings.

For the current member, GET /v2/me returns the signed-in person, with r\_liteprofile for name and photo or r\_basicprofile for name, photo, headline and vanity name. Retrieving another member's profile needs that member's Person ID, which LinkedIn says is available only through certain limited access APIs, and the call returns nothing for members who have limited their Off-LinkedIn Visibility.

The storage rule is the part that ends most plans. LinkedIn says you may store data from the Profile API for authenticated members only, with their permission, and may never store it for members other than the authenticated member.

So there is no LinkedIn people API or LinkedIn search API for finding prospects, and no LinkedIn connections API on the open list either. The LinkedIn data API a sales team wants, a profile in and a person out, is not a LinkedIn product a new developer can get.

Every provider that offers a LinkedIn profile lookup API is therefore working from its own data or from your account, not from LinkedIn's API, and the second half of this page is about which is which.

Auth and limits

## There is no LinkedIn API key: OAuth, tokens and rate limits

A LinkedIn API key is really an app's Client ID and Client Secret, configured in the Developer Portal and exchanged through OAuth 2.0 for an access token. LinkedIn runs two flows: Member Authorization, the 3-legged code flow where a member grants your app access to their resources, and Application Authorization, the 2-legged client credential flow for APIs that are not member specific. The Marketing APIs require Member Authorization.

The LinkedIn API OAuth details are short and worth knowing. An authorization code lasts 30 minutes, access tokens are currently issued with a 60-day lifespan, and refresh tokens are a separate feature enabled per app. LinkedIn asks for the minimal scopes a use case needs and does not support TLS 1.0.

Rate limits are daily and reset at midnight UTC, counted twice: per application and per member per application. LinkedIn says standard limits are not published in its documentation. You read your own in the Analytics tab of the app in the Developer Portal, for endpoints you have called at least once that day.

A request over the limit gets a 429, and LinkedIn may also return a 429 for infrastructure protection. Developer admins get an email when an app passes 75% of its quota, with a delay of about one to two hours, and only for application-level breaches.

Plan an integration around a daily budget you cannot see until you have made the call, which is a different design from the per-second limits most providers below publish.

Docs and tools

## LinkedIn API documentation, versions and tools

The LinkedIn API documentation lives on Microsoft Learn under learn.microsoft.com/linkedin, organized by business line, with getting-access, authentication, API concepts, breaking change policy and error handling pages shared across all of them. The LinkedIn API docs for Marketing are versioned: Marketing Version 202511 is being sunset on November 16, 2026, and LinkedIn asks integrations to move to the latest versioned APIs.

LinkedIn's developer site lists the tools around it: Postman collections for its APIs, GitHub projects with sample apps, OAuth token tools, a payload builder and an API status page. The LinkedIn API Postman collections are the quickest way to see a real request before writing one.

There is no official Python LinkedIn API client in the documentation read for this page. LinkedIn points instead to third-party open source libraries that handle OAuth 2.0 in every major language, so a LinkedIn API C# or Python integration starts from one of those, and its own OAuth sample application is in Java. The endpoints are REST, so any LinkedIn REST API call is an HTTPS request with a bearer token.

LinkedIn's developer docs are thorough on the products they cover; the gap is that the product most sales teams want is not among them.

Pricing

## LinkedIn API pricing: approval is the price

LinkedIn API pricing is not a rate card. None of the LinkedIn developer pages read for this page lists a price for API access; what they list is who may apply, the permissions granted on approval and the tier you start on.

The LinkedIn API cost is therefore time and eligibility rather than dollars: an application, a review with no fixed timeline for the restricted programs, a Development tier to build in, and a separate application for Standard. Some products also assume a LinkedIn product license on the customer side, such as Apply Connect, which LinkedIn describes for customers with a LinkedIn Recruiter Corporate or Recruiter Professional Services license.

Where you see a LinkedIn API price quoted by the call, it is somebody else's product. The LinkedIn API costs that show up on an invoice are the providers in the next sections, and those are published.

Budget for LinkedIn's own API in weeks, and for the alternatives in cents per record.

The terms

## What LinkedIn's User Agreement says about scraping and automation

The providers below each describe their own position.What follows is what LinkedIn's User Agreement, effective November 3, 2025, says in its list of Don'ts, which applies unless LinkedIn has explicitly permitted otherwise in a separate writing.

- Members agree not to develop, support or use software, devices, scripts, robots, crawlers, browser plugins or add-ons to scrape or copy the Services, including profiles and other data.
- Members agree not to override security features or bypass access controls or use limits, naming search results, profiles and videos as examples.
- Members agree not to copy, use or distribute information obtained from the Services, directly or through third parties such as data aggregators or brokers, without the consent of the content owner.
- Members agree not to use bots or other unauthorized automated methods to access the Services, add or download contacts, send or redirect messages, or create, comment on, like or share posts.

If you came looking for a LinkedIn scraping API or a LinkedIn scraper API, read those four lines first, because they describe exactly what those tools do. LinkedIn also reserves the right to restrict or terminate accounts that breach them, which is why the automation vendors below all run through your own account and talk about action ceilings.

Kind one

## Contact data from a LinkedIn URL, priced per hit

The first kind starts from a LinkedIn profile URL and returns an email, a phone or a profile from the provider's own data. This is what most people mean by a LinkedIn profile lookup API, and the providers sell it as a lookup, not as access to LinkedIn.

Wiza takes a LinkedIn URL as its best-matching input and charges from a separate API wallet: $0.025 a credit with a $50 minimum, 2 credits for a verified email, 5 for a phone, 1 for a profile and nothing on a miss. [Reverse Contact](https://frontal.so/gtm-apis/enrichment-apis/reverse-contact-api-review) sells credit packs from $100 for 5,000, or unlimited plans from $249 a month for teams that start from LinkedIn URLs.

Apollo's people match endpoint takes a name and domain, an email or a LinkedIn URL, at $0.0196 a credit. People Data Labs enriches a person by profile, at $0.28 a record on its entry plan, and [Crustdata](https://frontal.so/gtm-apis/enrichment-apis/crustdata-api-review) enriches a full profile from a profile URL, up to 25 at once, priced in credits with no public dollar rate.

[FullEnrich](https://frontal.so/gtm-apis/enrichment-apis/fullenrich-api-review) accepts a LinkedIn profile URL as an input to its [waterfall](https://frontal.so/gtm-apis/stacks/waterfall-enrichment) across 25 sources, at $0.055 a credit. None of these is a LinkedIn public API; each is a database or a waterfall that happens to accept the URL as a key, and its coverage is its own.

Pick among them on what a found row costs and whether a miss is free, which is what the [Wiza alternatives](https://frontal.so/gtm-apis/alternatives/wiza-alternatives) page compares in detail.

Kind two

## LinkedIn automation for outreach, through your own account

The second kind does not return data at all. It runs connection requests, messages and profile visits from a LinkedIn account you connect, and its API lets your stack start campaigns, add leads and read replies. This is the LinkedIn outreach API people mean, and the messaging access LinkedIn reserves for Sales Navigator partners and is not granting to new ones.

HeyReach prices per LinkedIn sender, $79 a sender or $999 for 25, with the API, webhooks and an [MCP server](https://frontal.so/gtm-apis/mcp-servers) on every plan. [Expandi](https://frontal.so/gtm-apis/sending-apis/expandi-api-review) is one plan at $79 a seat billed annually, with 22 webhook events, and its own review notes that LinkedIn's action ceilings are the binding constraint, not requests a minute.

Dripify charges per connected LinkedIn account, from $59 a seat billed annually, with the API, webhooks and MCP server on every plan. The sequencers price LinkedIn as an add-on: Reply.io at $69 a month per account on Email Volume plans, [Woodpecker](https://frontal.so/gtm-apis/sending-apis/woodpecker-api-review) at $29 a connected account, and [lemlist](https://frontal.so/gtm-apis/sending-apis/lemlist-api-review) on its Multichannel plan per user.

Because every one of these acts as your member account, the limit that matters is how many actions LinkedIn tolerates from one profile in a day. In practice this is where a LinkedIn messaging API for outreach comes from, because LinkedIn's own messaging route runs through the Sales Navigator API, which is not accepting new partners.

The [sending APIs](https://frontal.so/gtm-apis/sending-apis) page puts these beside the email-only sequencers on the same cost basis.

Kind three

## Scrapers and automations that read LinkedIn pages

The third kind reads LinkedIn pages. [PhantomBuster](https://frontal.so/gtm-apis/source-apis/phantombuster-api-review) launches Phantoms, prebuilt automations that extract and enrich from more than 15 platforms through your own accounts, LinkedIn chief among them, and meters execution time from $56 a month billed annually. Its review is blunt that what a run costs and how hard it leans on your LinkedIn account is decided by the Phantom.

Bright Data lists LinkedIn profiles and companies among more than 1,500 pre-built scrapers and charges $1.50 per 1,000 records delivered, so a call that returns 50 profiles is 50 units. That is the closest thing in this directory to a LinkedIn company API for data you did not create.

Both sit squarely inside the activity LinkedIn's User Agreement describes in its Don'ts, and neither is a LinkedIn unofficial API in the sense of an endpoint LinkedIn supports. Read the terms above, and each vendor's own position, before connecting an account you care about.

If the job is page content rather than LinkedIn in particular, the scraping providers are compared on their own terms on the [sourcing APIs](https://frontal.so/gtm-apis/source-apis) page.

MCP

## Is there a LinkedIn MCP server?

Not from LinkedIn: none of the LinkedIn developer pages read for this page mentions one. A LinkedIn MCP server, or an MCP server for LinkedIn, in practice means a provider's own server wrapping its LinkedIn work, and seventeen of the providers on this page ship one. These are the ones whose servers wrap LinkedIn work.

On the outreach side, HeyReach issues one per workspace from its Integrations page, Dripify hosts one on every plan, Reply.io hosts a 70-tool server on its API key, Expandi has one in beta, and lemlist and Woodpecker include theirs with the API. On the data side, Reverse Contact hosts one with 16 tools, Crustdata and Apollo host theirs, and PhantomBuster and Bright Data run hosted servers for their automations and scrapers.

There is no LinkedIn Sales Navigator MCP either, for the same reason there is no new Sales Navigator API: SNAP is closed to new partners. The [MCP page](https://frontal.so/gtm-apis/mcp-servers) lists the directory's own server and the vendor ones with their connect details.

An MCP server inherits everything above: it is only as allowed, and only as complete, as the API or the account behind it.

Side by side

## Every provider that works with LinkedIn data, side by side

Entry price and unit cost are read from each vendor's own pricing page. Three kinds sit in one table, a lookup, an automation seat and a scraper record, so compare rates only within a kind.

| Provider | Returns | Entry price | Unit cost | MCP server |
| --- | --- | --- | --- | --- |
| [Apollo API](https://frontal.so/gtm-apis/enrichment-apis/apollo-api-review) | Work email, Mobile phone, Firmographics, LinkedIn profile, CRM records | $49/seat/mo | $0.0196 per credit | Yes |
| [Clay](https://frontal.so/gtm-apis/enrichment-apis/clay-api-review) | Work email, Mobile phone, Firmographics, LinkedIn profile | $167/mo annual | $0.0452 per data credit | Yes |
| [People Data Labs](https://frontal.so/gtm-apis/enrichment-apis/people-data-labs-api-review) | Work email, Mobile phone, Firmographics, LinkedIn profile | $98/mo | $0.28 per record | No |
| [LeadMagic](https://frontal.so/gtm-apis/enrichment-apis/leadmagic-api-review) | Work email, Mobile phone, Firmographics, LinkedIn profile | $99/mo | $0.0198 per credit | Yes |
| [Findymail](https://frontal.so/gtm-apis/enrichment-apis/findymail-api-review) | Work email, Mobile phone, LinkedIn profile, Firmographics | $99/mo | $0.0198 per credit | Yes |
| [Prospeo](https://frontal.so/gtm-apis/enrichment-apis/prospeo-api-review) | Work email, Mobile phone, LinkedIn profile | $49/mo | $0.0245 per credit | Yes |
| [FullEnrich](https://frontal.so/gtm-apis/enrichment-apis/fullenrich-api-review) | Work email, Mobile phone, LinkedIn profile | $29/mo | $0.055 per credit, 1,000-credit plan | Yes |
| [Woodpecker](https://frontal.so/gtm-apis/sending-apis/woodpecker-api-review) | Work email, LinkedIn profile | $39/mo | $0.0078 per email sent | Yes |
| [lemlist](https://frontal.so/gtm-apis/sending-apis/lemlist-api-review) | Work email, Mobile phone, LinkedIn profile | $55/mo annual | $0.008 per credit | Yes |
| [HeyReach](https://frontal.so/gtm-apis/sending-apis/heyreach-api-review) | LinkedIn profile, Work email | $79/sender/mo | Not sold by the unit | Yes |
| [Reply.io](https://frontal.so/gtm-apis/sending-apis/reply-io-api-review) | Work email, LinkedIn profile, CRM records | $49/user/mo annual | Not sold by the unit | Yes |
| [Dripify](https://frontal.so/gtm-apis/sending-apis/dripify-api-review) | Work email, LinkedIn profile | $59/user/mo annual | Not sold by the unit | Yes |
| [Expandi](https://frontal.so/gtm-apis/sending-apis/expandi-api-review) | LinkedIn profile, Work email | $79/user/mo annual | Not sold by the unit | Yes |
| [Bright Data](https://frontal.so/gtm-apis/source-apis/bright-data-api-review) | Firmographics, LinkedIn profile | $1.50/1K requests | $0.0015 per request | Yes |
| [PhantomBuster](https://frontal.so/gtm-apis/source-apis/phantombuster-api-review) | LinkedIn profile, Work email, Firmographics | $56/mo annual | $2.80 per execution hour | Yes |
| [Wiza](https://frontal.so/gtm-apis/enrichment-apis/wiza-api-review) | Work email, Mobile phone, LinkedIn profile, Firmographics | $50 one-time | $0.05 per email, 2 credits | No |
| [Reverse Contact](https://frontal.so/gtm-apis/enrichment-apis/reverse-contact-api-review) | Work email, Mobile phone, Firmographics, LinkedIn profile | $100 one-time | $0.02 per credit | Yes |
| [Crustdata](https://frontal.so/gtm-apis/enrichment-apis/crustdata-api-review) | Work email, Mobile phone, Firmographics, LinkedIn profile | Quote only | Sold in credits; no public dollar price for a credit | Yes |
| [Dropcontact](https://frontal.so/gtm-apis/enrichment-apis/dropcontact-api-review) | Work email, Firmographics, LinkedIn profile | €29/mo | €0.01975 an email found, priced in euros (€79 for 4,000) | Yes |

Read from each vendor's own pages between 23 and 24 October 2026, and each review carries the full rate card.

The directory

## Every provider that returns this, filtered

The 19 providers are chosen by the data each one returns, read off its record, not by hand. Billing model is the filter worth starting with, because it decides whether a quiet month costs you anything.

Each has a full review, with the rate card read off the vendor's own page: [Apollo](https://frontal.so/gtm-apis/enrichment-apis/apollo-api-review), [Clay](https://frontal.so/gtm-apis/enrichment-apis/clay-api-review), [People Data Labs](https://frontal.so/gtm-apis/enrichment-apis/people-data-labs-api-review) and [LeadMagic](https://frontal.so/gtm-apis/enrichment-apis/leadmagic-api-review).

Also with a full review: [Findymail](https://frontal.so/gtm-apis/enrichment-apis/findymail-api-review), [Prospeo](https://frontal.so/gtm-apis/enrichment-apis/prospeo-api-review), [FullEnrich](https://frontal.so/gtm-apis/enrichment-apis/fullenrich-api-review) and [Woodpecker](https://frontal.so/gtm-apis/sending-apis/woodpecker-api-review).

And: [lemlist](https://frontal.so/gtm-apis/sending-apis/lemlist-api-review), [HeyReach](https://frontal.so/gtm-apis/sending-apis/heyreach-api-review), [Reply.io](https://frontal.so/gtm-apis/sending-apis/reply-io-api-review) and [Dripify](https://frontal.so/gtm-apis/sending-apis/dripify-api-review).

And: [Expandi](https://frontal.so/gtm-apis/sending-apis/expandi-api-review), [Bright Data](https://frontal.so/gtm-apis/source-apis/bright-data-api-review), [PhantomBuster](https://frontal.so/gtm-apis/source-apis/phantombuster-api-review) and [Wiza](https://frontal.so/gtm-apis/enrichment-apis/wiza-api-review).

And: [Reverse Contact](https://frontal.so/gtm-apis/enrichment-apis/reverse-contact-api-review), [Crustdata](https://frontal.so/gtm-apis/enrichment-apis/crustdata-api-review) and [Dropcontact](https://frontal.so/gtm-apis/enrichment-apis/dropcontact-api-review).

### Filter

Showing 19 of 19

### [Apollo API](https://frontal.so/gtm-apis/enrichment-apis/apollo-api-review)

Best all-in-one GTM API

Featured

Motion Source Enrich Engage Sync

Model MCP server Free tier Per seat

One of two providers here, with Instantly, that covers sourcing, enrichment and sending behind a single key, which is why it is usually the first API a GTM team wires up and the last one they rip out. The catch is that credits and seats are coupled, so the API inherits a per-seat price even when no human logs in.

- People and organization search across Apollo's own database
- Enrichment returns 1 credit for email, 9 if a mobile comes back
- Sequence, contact and task endpoints cost 0 credits
- Credits are granted per seat per YEAR, not per month

From $49 /seat/mo

[Read the review of the Apollo API](https://frontal.so/gtm-apis/enrichment-apis/apollo-api-review) [site for Apollo (opens in a new tab)](https://go.frontal.so/apollo)

### [Clay](https://frontal.so/gtm-apis/enrichment-apis/clay-api-review)

Best orchestration layer

Motion Source Enrich Signal

Model MCP server Free tier

Clay is not really an enrichment API, it is the router in front of everybody else's. You pay in actions for the work and data credits for the data rather than per record, and the waterfall logic that would take a week to build yourself is a column setting.

- Waterfall across 150+ data providers without separate contracts
- Two meters, actions and data credits, and neither is charged on a lookup that finds nothing
- Free plan runs 500 actions a month with no phone enrichment

From $167 /mo annual

[Read the review of the Clay API](https://frontal.so/gtm-apis/enrichment-apis/clay-api-review) [site for Clay (opens in a new tab)](https://go.frontal.so/clay)

### [People Data Labs](https://frontal.so/gtm-apis/enrichment-apis/people-data-labs-api-review)

Best for building on top of

Motion Source Enrich

Model Free tier

PDL sells the dataset rather than the workflow, and its standard subscription agreement licenses you to show its data to your own customers inside your product, which few other self-serve plans here grant by default. It is not a resale license: you may not resell the data or give your users programmatic access to a substantial part of it. That license is the reason to pick it over a cheaper per-email tool.

- Person, company, job title and school datasets under one key
- Free plan obfuscates emails and phones until you upgrade
- Bulk and search endpoints designed for warehouse loads

From $98 /mo

[Read the review of the People Data Labs API](https://frontal.so/gtm-apis/enrichment-apis/people-data-labs-api-review) [site for People Data Labs (opens in a new tab)](https://www.peopledatalabs.com/)

### [LeadMagic](https://frontal.so/gtm-apis/enrichment-apis/leadmagic-api-review)

Best priced per operation

Motion Source Enrich Verify Signal

Model MCP server

Every operation has a stated credit cost, credits come off only when a lookup succeeds, and search is free in the app and unmetered on the API from Professional. The MCP server ships on every tier, including the cheapest.

- Email finder 1 credit, mobile 5, validation 0.25, job change 3
- Credits deducted on valid results only, never on a miss
- Search is free in the app; the Search API is 1 credit a result on Essential and Growth, unmetered from Professional

From $99 /mo

[Read the review of the LeadMagic API](https://frontal.so/gtm-apis/enrichment-apis/leadmagic-api-review) [site for LeadMagic (opens in a new tab)](https://www.leadmagic.io/)

### [Findymail](https://frontal.so/gtm-apis/enrichment-apis/findymail-api-review)

A refund if your bounce rate passes 5%

Motion Enrich Verify

Model MCP server

Findymail verifies at the moment it finds, so you are not paying twice for the same address. It is the only provider here that puts a number on deliverability and refunds against it: above a 5% bounce rate, the credits come back.

- Under 5% bounce rate or the credits are refunded
- Duplicates found in the last 30 days cost nothing
- Mobile numbers are non-EU only, at 10 credits each
- API on every plan; usage-based plans include 1, 5 or 20 seats, credit plans are for reselling or embedding

From $99 /mo

[Read the review of the Findymail API](https://frontal.so/gtm-apis/enrichment-apis/findymail-api-review) [site for Findymail (opens in a new tab)](https://www.findymail.com/)

### [Prospeo](https://frontal.so/gtm-apis/enrichment-apis/prospeo-api-review)

Low entry for verified email, with rollover

Motion Source Enrich

Model MCP server

Prospeo gets you to 2,000 verified emails a month for $49, tied with Hunter for the cheapest 2,000-email plan here on monthly billing, and unlike Hunter its unused credits roll into the next cycle rather than expiring. The trade is the shape of the product: email and phone, priced per user, and a mobile number costs ten times what an email does.

- 1 credit per verified email, 10 per direct mobile
- Unused credits roll over and stack on the next cycle's pack
- Annual billing delivers the full year of credits upfront

From $49 /mo

[Read the review of the Prospeo API](https://frontal.so/gtm-apis/enrichment-apis/prospeo-api-review) [site for Prospeo (opens in a new tab)](https://go.frontal.so/prospeo)

### [FullEnrich](https://frontal.so/gtm-apis/enrichment-apis/fullenrich-api-review)

Best waterfall without Clay

Motion Enrich Verify

Model MCP server

FullEnrich runs the same waterfall logic Clay does, but as a single API call with a single bill. If all you need is the waterfall and not the spreadsheet around it, this is that half of the trade on its own.

- Work email 1 credit, personal email 3, mobile 10
- Profile and company data free with any enrichment, 0.25 a credit on its own
- Landline results cost nothing, so you only pay for mobiles

From $29 /mo

[Read the review of the FullEnrich API](https://frontal.so/gtm-apis/enrichment-apis/fullenrich-api-review) [site for FullEnrich (opens in a new tab)](https://www.fullenrich.com/)

### [Woodpecker](https://frontal.so/gtm-apis/sending-apis/woodpecker-api-review)

One meter, and the API as a $20 add-on

Motion Engage

Model MCP server

Woodpecker sells one product on one meter, emails sent a month, from $39 for 5,000 or $312 a year. Everything else is an add-on you tick: LinkedIn at $29 a connected account, mailboxes at $4 to $6 each, and the API, webhooks, MCP server and CLI bundled together for $20 a month.

- One meter: $39 a month for 5,000 emails sent, up to $999 for 1,000,000
- API, webhooks, MCP and CLI are one $20 a month add-on
- Unlimited email accounts and team members included at every size

From $39 /mo

[Read the review of the Woodpecker API](https://frontal.so/gtm-apis/sending-apis/woodpecker-api-review) [site for Woodpecker (opens in a new tab)](https://woodpecker.co/)

### [lemlist](https://frontal.so/gtm-apis/sending-apis/lemlist-api-review)

API, MCP and CLI on the cheapest plan

Motion Engage Enrich Signal

Model MCP server

lemlist puts unlimited users and unlimited email senders on its entry plan, then adds the API, an MCP server and a CLI to the same tier rather than holding them back for an upgrade. Data is the thing it sells separately: a $16 add-on buys 2,000 credits a month across 25-plus providers, and intent signals are another $21.

- Unlimited users and email senders from $55 a month billed yearly
- API, MCP server and CLI on the entry plan, not an upgrade
- Data and intent signals are separate add-ons, $16 and $21 a month

From $55 /mo annual

[Read the review of the lemlist API](https://frontal.so/gtm-apis/sending-apis/lemlist-api-review) [site for lemlist (opens in a new tab)](https://go.frontal.so/lemlist)

### [HeyReach](https://frontal.so/gtm-apis/sending-apis/heyreach-api-review)

API, webhooks and MCP on the $79 entry plan

Motion Engage

Model MCP server Per seat

HeyReach prices per LinkedIn sender at $79 a month and puts the API, webhooks, an MCP server and client workspaces on that entry plan rather than reserving them for an agency tier. Above about 13 senders the $999 Agency plan is cheaper per sender, and the $2,999 Unlimited plan is capped at 300 by fair use.

- $79 a sender, or $999 for 25 senders once you pass about 13
- API, webhooks, MCP server and workspaces on every plan
- 300 requests a minute, and API keys that never expire

From $79 /sender/mo

[Read the review of the HeyReach API](https://frontal.so/gtm-apis/sending-apis/heyreach-api-review) [site for HeyReach (opens in a new tab)](https://www.heyreach.io/)

### [Reply.io](https://frontal.so/gtm-apis/sending-apis/reply-io-api-review)

Best for teams that outgrow per-seat pricing

Motion Engage

Model MCP server Per seat

Reply.io meters active contacts rather than emails, and the price flips shape partway up the slider: $49 a user at 1,000 contacts, then $159 for unlimited users at 10,000. It is also the only sender here that publishes the formula behind its unlimited mailbox claim, at one mailbox per 40 active contacts.

- Unlimited users from the 10,000 active contact tier upward
- Fair usage policy publishes a mailbox ceiling: contacts divided by 40
- API on every plan, but v1 and v2 allow 15,000 calls a month against v3's 150,000 a week

From $49 /user/mo annual

[Read the review of the Reply.io API](https://frontal.so/gtm-apis/sending-apis/reply-io-api-review) [site for Reply.io (opens in a new tab)](https://reply.io/)

### [Dripify](https://frontal.so/gtm-apis/sending-apis/dripify-api-review)

An OpenAPI spec and documented errors for LinkedIn automation

Motion Engage

Model MCP server Per seat

Dripify prices by LinkedIn account rather than by volume, because LinkedIn itself is the constraint: the plan you pick sets your daily connection requests and messages. The API, webhooks and an MCP server come with every plan, from Pro at $59 a seat, with a downloadable OpenAPI spec and published rate limits, which is more than most tools in this category manage.

- One seat connects one LinkedIn account, so a team of five needs five
- Every plan allows up to 75 connection requests and 100-plus messages a day
- API, webhooks and MCP server on every plan, from $59 a seat billed annually

From $59 /user/mo annual

[Read the review of the Dripify API](https://frontal.so/gtm-apis/sending-apis/dripify-api-review) [site for Dripify (opens in a new tab)](https://dripify.com/)

### [Expandi](https://frontal.so/gtm-apis/sending-apis/expandi-api-review)

Best for webhook-driven LinkedIn campaigns

Motion Engage

Model MCP server Per seat

Expandi publishes exactly one plan at $99 a month with every feature in it, which makes it the simplest thing to price in this category. The integration surface is webhooks rather than a documented API: 22 outbound events, and a per-campaign URL that accepts a POST to add, pause or resume a lead. The full REST reference sits behind a login. An MCP server, still labeled beta, signs in through OAuth at api.liaufa.com/mcp.

- One published plan, $99 a month or $79 billed annually, per seat
- 22 webhook events, from connection accepted to email bounced
- A reversed webhook per campaign adds leads with a POST, no auth header

From $79 /user/mo annual

[Read the review of the Expandi API](https://frontal.so/gtm-apis/sending-apis/expandi-api-review) [site for Expandi (opens in a new tab)](https://expandi.io/)

### [Bright Data](https://frontal.so/gtm-apis/source-apis/bright-data-api-review)

Best for search results and pre-built scrapers at volume

Motion Source Signal

Model MCP server Free tier No monthly floor

Bright Data is web data infrastructure: proxies, an unblocker, a SERP API and more than 1,500 pre-built scrapers. The three API products a GTM team calls, the SERP API, the Web Unlocker API and the Web Scraper API, are priced the same way: $1.50 per 1,000 successful requests or records, or $499 a month for about 380,000.

- SERP, Unlocker and Scraper APIs at $1.50 per 1,000, charged on success only
- 5,000 free credits a month shared across all three, no card
- SERP API capped at 1,000 a minute until the account holds funds

From $1.50 /1K requests

[Read the review of the Bright Data API](https://frontal.so/gtm-apis/source-apis/bright-data-api-review) [site for Bright Data (opens in a new tab)](https://brightdata.com/)

### [PhantomBuster](https://frontal.so/gtm-apis/source-apis/phantombuster-api-review)

Best for running LinkedIn automations from code

Motion Source Enrich Engage

Model MCP server

PhantomBuster runs Phantoms, prebuilt automations that extract and enrich from over 15 platforms, LinkedIn among them, through your own accounts. The API does not scrape anything itself: it launches an agent and reads what the agent produced, and the bill is execution hours, slots and email credits rather than requests.

- Plans meter execution time: 20, 80 or 300 hours a month
- No published request rate limit; slots cap how many Phantoms run at once
- Hosted MCP server with OAuth on every plan

From $56 /mo annual

[Read the review of the PhantomBuster API](https://frontal.so/gtm-apis/source-apis/phantombuster-api-review) [site for PhantomBuster (opens in a new tab)](https://phantombuster.com/)

### [Wiza](https://frontal.so/gtm-apis/enrichment-apis/wiza-api-review)

LinkedIn URLs in, verified emails and mobiles out, paid per hit

Motion Source Enrich

Model No monthly floor

Wiza sells its API apart from its seat plans: a prepaid balance of API credits at $0.025 each, from a $50 minimum, that anyone can buy without a subscription. A verified email costs 2 credits, a phone 5 and a profile 1, and nothing is charged when nothing is found. None of the individual seat plans, even the unlimited annual ones, lists API access.

- API credits at $0.025 each, 2,000 minimum for $50, no plan required
- 2 credits a verified email, 5 a phone, 1 a profile, 0 on a miss
- Async reveals: 15 requests a second, then 5 or 15+ running at once by API tier

From $50 one-time

[Read the review of the Wiza API](https://frontal.so/gtm-apis/enrichment-apis/wiza-api-review) [site for Wiza (opens in a new tab)](https://wiza.co/)

### [Reverse Contact](https://frontal.so/gtm-apis/enrichment-apis/reverse-contact-api-review)

Unlimited profile lookups for a team that starts from LinkedIn URLs

Motion Enrich Source

Model MCP server Free tier

Reverse Contact sells person and company data two ways: credit packs from $100 for 5,000, or unlimited monthly plans priced by endpoint family. Go at $249 makes profile fetches from a social URL unlimited, Plus at $449 adds search and Max at $699 adds enrichment from an email, a name or a domain. Emails, phones and live refreshes stay on credits on every plan, and nothing is charged when nothing is found.

- Credit packs from $100 for 5,000, valid 3 months; 500 free credits, no card
- Unlimited plans from $249 a month, each one unlocking an endpoint family
- Hosted MCP server with 16 tools, OAuth or an API key, plus a CLI

From $100 one-time

[Read the review of the Reverse Contact API](https://frontal.so/gtm-apis/enrichment-apis/reverse-contact-api-review) [site for Reverse Contact (opens in a new tab)](https://www.reversecontact.com/)

### [Crustdata](https://frontal.so/gtm-apis/enrichment-apis/crustdata-api-review)

Search wide for pennies of a credit, then pay only for the fields you keep

Motion Source Enrich Signal

Model MCP server Free tier

Crustdata prices every call in credits by what it returns: a search result is 0.03 credits and an empty search is free, a person profile is 1 credit and each contact field is an add-on on top. What it does not publish is what a credit costs in dollars. New accounts get $20 in credits, self-serve packs are priced in the dashboard, and enterprise plans start at four figures a month.

- Search at 0.03 credits a result, and a search that returns nothing is free
- Person enrich from 1 credit, up to 9 with every contact add-on
- $20 in free credits; the dollar rate of a credit is not on the public pages
- Hosted MCP server, and limits set per endpoint, from 10 to 30 requests a minute

From Quote only

[Read the review of the Crustdata API](https://frontal.so/gtm-apis/enrichment-apis/crustdata-api-review) [site for Crustdata (opens in a new tab)](https://crustdata.com/)

### [Dropcontact](https://frontal.so/gtm-apis/enrichment-apis/dropcontact-api-review)

Email finding with no contact database behind it, for GDPR-first teams

Motion Enrich Verify

Model MCP server Free tier

Dropcontact finds and verifies a work email from a name and a company without keeping a contact database: its pricing page says it works "exclusively with algorithms" on EU servers. A credit is spent only when a verified email comes back, and refunded when none does. It is priced in euros only, from €29 a month for 500 emails, and the API takes up to 250 contacts per asynchronous request.

- Pay on success: a credit only when a verified email is returned
- No contact database; built for GDPR, on EU servers
- Priced in euros, from €29 a month for 500 emails, API and MCP on every plan
- Up to 250 contacts per request, 60 requests a second

From €29 /mo

[Read the review of the Dropcontact API](https://frontal.so/gtm-apis/enrichment-apis/dropcontact-api-review) [site for Dropcontact (opens in a new tab)](https://www.dropcontact.com/)

Buyer's guide

## Four things that decide a LinkedIn integration

In the order they cost you money.

01

### Whose data is it

LinkedIn's own API returns the authenticated member's data and your own Pages and ads, and forbids storing anybody else's. A contact-data provider returns its own data keyed by a LinkedIn URL. Decide which of those you actually need before reading a price.

02

### Whose account carries the risk

Automation and scraping tools act as a LinkedIn account you connect, and LinkedIn's terms let it restrict that account. A lookup provider touches no account of yours. That difference matters more than any rate.

03

### What a found row costs

Wiza charges nothing on a miss, Reverse Contact sells unlimited plans by endpoint family, and automation tools charge per seat whatever the reply rate. Price the row you keep, not the request you send.

04

### Which limit binds

LinkedIn's own API runs on a daily budget you read in the Developer Portal. Automation tools are bound by how many actions LinkedIn tolerates from one profile. Data providers publish per-second or per-minute rates. Design to the limit that actually stops you.

Keep going

## Comparisons, stacks and alternatives

The same providers, seen three other ways: head to head on the [compare hub](https://frontal.so/gtm-apis/compare), by the reason teams leave on the [alternatives hub](https://frontal.so/gtm-apis/alternatives), and wired together with the cost run end to end on the [stacks hub](https://frontal.so/gtm-apis/stacks).

The same providers, sorted by other data: [People data APIs](https://frontal.so/gtm-apis/people-data-apis), [Company data APIs](https://frontal.so/gtm-apis/company-data-apis) and [Technographic data APIs](https://frontal.so/gtm-apis/technographic-data-apis).

And: [Email validation APIs](https://frontal.so/gtm-apis/email-validation-apis) and [B2B data APIs](https://frontal.so/gtm-apis/b2b-data-apis).

By the stage of the motion they serve: [Enrichment APIs](https://frontal.so/gtm-apis/enrichment-apis), [Sending APIs](https://frontal.so/gtm-apis/sending-apis) and [Sourcing APIs](https://frontal.so/gtm-apis/source-apis).

Head to head, with the arithmetic done: [Apollo vs Clay](https://frontal.so/gtm-apis/compare/apollo-vs-clay), [Apollo vs People Data Labs](https://frontal.so/gtm-apis/compare/apollo-vs-people-data-labs), [Apollo vs LeadMagic](https://frontal.so/gtm-apis/compare/apollo-vs-leadmagic) and [Apollo vs Prospeo](https://frontal.so/gtm-apis/compare/apollo-vs-prospeo).

Also side by side: [Clay vs FullEnrich](https://frontal.so/gtm-apis/compare/clay-vs-fullenrich), [Clay vs People Data Labs](https://frontal.so/gtm-apis/compare/clay-vs-people-data-labs), [LeadMagic vs Findymail](https://frontal.so/gtm-apis/compare/leadmagic-vs-findymail) and [LeadMagic vs Prospeo](https://frontal.so/gtm-apis/compare/leadmagic-vs-prospeo).

And: [Findymail vs Prospeo](https://frontal.so/gtm-apis/compare/findymail-vs-prospeo), [FullEnrich vs Findymail](https://frontal.so/gtm-apis/compare/fullenrich-vs-findymail), [Reply.io vs Woodpecker](https://frontal.so/gtm-apis/compare/reply-io-vs-woodpecker) and [Dripify vs Expandi](https://frontal.so/gtm-apis/compare/dripify-vs-expandi).

Teams leaving one of these have somewhere to go: [Apollo](https://frontal.so/gtm-apis/alternatives/apollo-api-alternatives), [Clay](https://frontal.so/gtm-apis/alternatives/clay-alternatives), [LeadMagic](https://frontal.so/gtm-apis/alternatives/leadmagic-alternatives) and [Findymail](https://frontal.so/gtm-apis/alternatives/findymail-alternatives).

And: [Prospeo](https://frontal.so/gtm-apis/alternatives/prospeo-alternatives), [FullEnrich](https://frontal.so/gtm-apis/alternatives/fullenrich-alternatives), [People Data Labs](https://frontal.so/gtm-apis/alternatives/people-data-labs-alternatives) and [Reply.io](https://frontal.so/gtm-apis/alternatives/reply-io-alternatives).

## Not sure which provider to pick? *Clay runs 150+ from one table.*

Clay runs a waterfall across 150+ data providers from one table, without a separate contract with each. A lookup that finds nothing costs no data credit, and the free plan includes 500 actions a month.

[Try Clay](https://go.frontal.so/clay) [See the stacks](https://frontal.so/gtm-apis/stacks)

Frontal is a Clay Elite Studio Partner.

FAQ

## LinkedIn APIs, answered

**How many providers that work with LinkedIn data are in this directory?**

19, chosen by what each one returns rather than by hand, and each with its own review carrying the price, the rate limit and the auth method read from the vendor's own pages.

**Which providers that work with LinkedIn data have a free tier?**

Apollo, Clay, People Data Labs, Bright Data, Reverse Contact, Crustdata and Dropcontact. What each free tier includes differs a lot, so the review says what you actually get.

**Which provider that works with LinkedIn data is cheapest?**

It depends which of the three kinds you need. For a lookup from a profile URL, Apollo at $0.0196 a credit, LeadMagic at $0.0198 and Reverse Contact at $0.02 sit together, and Wiza charges $0.05 for a verified email and nothing on a miss. Automation is priced per LinkedIn account, from a $29 Woodpecker add-on to $79 a sender on HeyReach, and Bright Data charges $1.50 per 1,000 scraped records.

**How are providers that work with LinkedIn data billed?**

13 of the 19 publish a per-unit rate; the rest sell a plan, quote on request or price in another currency, and each review says which.

**Which ones ship an MCP server?**

Apollo, Clay, LeadMagic, Findymail, Prospeo, FullEnrich, Woodpecker, lemlist, HeyReach, Reply.io, Dripify, Expandi, Bright Data, PhantomBuster, Reverse Contact, Crustdata and Dropcontact. The ones the directory reviews live on the MCP page with the connect details.

**Is the LinkedIn API free?**

LinkedIn's developer pages list no price for API access. The open permissions, Sign In with LinkedIn and Share on LinkedIn, are added self-service; every other product needs an application and LinkedIn's approval, and some are closed to new applicants.

**How do I get a LinkedIn API key?**

There is no single key. You create an app in the LinkedIn Developer Portal, which gives it a Client ID and Client Secret, and add the products you are allowed to use from its Products tab. Then you exchange those credentials through OAuth 2.0 for an access token, currently issued with a 60-day lifespan.

**Can the LinkedIn API look up a profile from a URL?**

Not for a new developer. LinkedIn restricts its Profile API to approved developers, returns another member only by a Person ID available through limited access APIs, and says data may never be stored for members other than the authenticated member. Providers that look up a LinkedIn URL do it from their own data.

**Is there a LinkedIn Sales Navigator API?**

There is the Sales Navigator Application Platform, SNAP, with display, analytics and sync services for CRM partners. LinkedIn says it is not currently accepting new partners for access to the Sales Navigator API.

**Does LinkedIn allow scraping?**

Its User Agreement says members agree not to use software, scripts, robots, crawlers or browser plugins to scrape or copy the Services, including profiles, and not to use bots or unauthorized automated methods to access them. The agreement itself and each vendor's own position are the documents to read.
