Is There a LinkedIn API for Outreach? Official APIs, MCP Servers and What to Use Instead (2026)
LinkedIn has no official API or MCP server for running outreach. See what its APIs allow, what third-party LinkedIn APIs do, and what to use instead.
TL;DR: No. LinkedIn has no official API or MCP server you can sign up for and run outreach from. Its self-serve API permissions cover signing in and posting, commenting and liking as the signed-in member; its Messages and Invitations APIs are restricted to approved partners, and LinkedIn's rules for the Messages API say a message can't come from an automated or scheduled event. To run LinkedIn outreach from code or an AI assistant, teams either build on a third-party LinkedIn API that acts through their own account, or use a LinkedIn GTM tool such as traxy that finds high intent leads and runs LinkedIn and email campaigns from their connected sender accounts. With the traxy MCP, you can run that LinkedIn and email outreach from Claude, ChatGPT or another AI chat, and nothing sends until you say yes.
traxy wrote this guide, and we make a LinkedIn GTM tool. traxy is not affiliated with LinkedIn. Claims about LinkedIn's APIs come from LinkedIn's own documentation, help pages and newsroom, linked where they appear, and each third-party vendor is described from its own website. Checked November 10, 2026. APIs and partner programs change, so confirm with LinkedIn and each vendor before you build on them.
Does LinkedIn have an official API for outreach?
No. LinkedIn has no API you can sign up for and run outreach from. LinkedIn's page on getting access to its APIs says most permissions and partner programs need explicit approval from LinkedIn, and that open permissions are the only ones available to every developer. Those open permissions are Sign In with LinkedIn (the signed-in member's name, headline, photo and email) and Share on LinkedIn (post, comment and like posts on behalf of the signed-in member). None of them sends a connection request or a message.
LinkedIn documents these APIs for messaging, sales and Pages, each with its own access rules:
LinkedIn API or program | What LinkedIn says it does | Who can use it |
|---|---|---|
Sign In with LinkedIn, Share on LinkedIn | Sign-in, and posting, commenting and liking as the signed-in member | Any developer, self-serve (access page) |
Messages API | Lets members create messages to first-degree connections or reply to existing conversations | Approved partners only. Each message must be tied to a specific member action, which can't be an automated or scheduled event (Messages API) |
Invitations API | Sends connection invitations on behalf of the signed-in member | Approved partners only (Invitations API) |
Sales Navigator Application Platform (SNAP) | Sales Navigator modules embedded in another app, for viewing profiles and accounts and for connecting with and messaging leads, including InMail | Approved SNAP partners. LinkedIn says it is not currently accepting new partners for the Sales Navigator API (SNAP docs) |
Pages messaging API | Send and receive messages in a company Page's inbox | Through LinkedIn's API partner platforms: Bird CRM, Brandwatch, Hootsuite, Oktopost, Sprinklr and Zoho Recruit (LinkedIn Help) |
Community Management API | Manage company Pages, posts, comments and reactions for Pages and members, and read their analytics | Vetted developers, with development and standard tiers (overview) |
Advertising API | Advertising on LinkedIn | Approved developers, who apply in the Developer Portal (access page) |
The Messages API rules matter most for outreach. LinkedIn requires that the member opts in to each message, can edit any prepared draft, and takes an affirmative action to send it, and that the message is posted at or around the time the member acted. Under those rules an app can't use the Messages API for automated or scheduled sends, which is what an outreach sequence does.
If you use LinkedIn's Marketing APIs for ads or Page reporting, their docs carry a notice that version 202511 sunsets on November 16, 2026. Our Marketing API 202511 migration guide covers what to change.
What do LinkedIn's own pages say about the Messages API and the Sales Navigator API?
They say the Messages API is for approved partners only, every message must follow a member action, and the Sales Navigator API isn't taking new partners. These are the passages, each linked to LinkedIn's own page and checked November 2026. Text in quotation marks is LinkedIn's exact wording.
LinkedIn page | What the page says | What it means for outreach |
|---|---|---|
"Most permissions and partner programs require explicit approval from LinkedIn. Open Permissions are the only permissions that are available to all developers without special approval." | Self-serve access covers signing in and posting, commenting and liking as the member. It doesn't include messages or invitations. | |
"Usage of this API is restricted to approved partners, subject to limitations via API agreement." | You can't sign up for it yourself. | |
"A message must be associated with a specific member action. Member actions do not include an automated or scheduled event." | Even an approved partner can't use it to send the scheduled steps of a sequence. | |
"A message must be posted at, or around the time the member took action to send the message." | Messages can't be queued to go out later. | |
"Usage of this API is restricted to approved partners, subject to limitations via API agreement." | Connection requests through LinkedIn's API are partner-only too. | |
"We are not currently accepting new partners for access to the LinkedIn Sales Navigator API." | A new app can't join the Sales Navigator API program for now. LinkedIn says it will update the page if availability changes. | |
Since February 1, 2025, display integrations between Sales Navigator and other platforms, such as Embedded Profiles, are available only to Sales Navigator Advanced Plus customers. | Showing Sales Navigator inside an existing partner's app needs the Advanced Plus plan. |
Put together, LinkedIn's official APIs don't let a team outside its partner programs run connection requests and follow-up messages as a sequence. The routes teams use instead are covered further down.
Does LinkedIn have an official MCP server?
No. We found no LinkedIn documentation for an MCP server that sends messages or connection requests. MCP (Model Context Protocol) is the standard AI assistants such as Claude and ChatGPT use to call tools in other apps. LinkedIn's developer product catalog lists products such as Sign In with LinkedIn, Share on LinkedIn, Advertising, Community Management and Sales Display, and no MCP server.
Two related things do exist:
Hiring Pro in Claude. On October 21, 2026, LinkedIn announced that hirers can use Hiring Pro, its hiring product for small businesses, through Claude. Claude drafts the job post, and once the hirer edits and approves it, it publishes on LinkedIn for free. LinkedIn says the partnership covers Hiring Pro jobs only.
"Develop with MCP." LinkedIn's developer site shows a "Develop with MCP" link marked New. The page behind it needs a LinkedIn sign-in, and we found no public documentation of what it covers. Check what LinkedIn documents before you plan around it.
The LinkedIn MCP servers for outreach that we found are built by third parties. The next section covers five of them.
What does a vendor's "official Claude connector" mean?
It means the vendor's own MCP server is listed in Claude's Connectors Directory. It doesn't mean LinkedIn approved the tool or what it does on LinkedIn. Anthropic's connector verification page (checked November 2026) says the directory lists connectors from Anthropic and from third-party developers, and labels each one by how much Anthropic reviewed it:
Verified. Anthropic tested the connector's tools for quality and compatibility. Anthropic says verification "isn't a security audit or a guarantee of how the connector will perform."
Community. A third-party developer built it, and Anthropic screened it before listing but hasn't reviewed it in depth.
Custom. You added it yourself by URL, and Anthropic hasn't reviewed it.
The same page says "The developer operates the connector and controls its tools, which can change after review," and that listing a connector doesn't change the tools it exposes. So a LinkedIn outreach connector in Claude reaches LinkedIn the same way the vendor's own product does: through a LinkedIn partner API if the vendor has partner access, or through the LinkedIn account you connect to the vendor. The only connector from LinkedIn itself in Claude that we found is Hiring Pro, and it covers job posts.
Before you connect a LinkedIn outreach connector, ask the vendor:
Who builds and runs it, and is the vendor affiliated with LinkedIn?
Does it send through a LinkedIn partner API, or through your own logged-in LinkedIn account?
Does every send, launch or reply wait for your yes in chat?
Which daily limits, active hours and stop rules apply to your account?
Then read what LinkedIn says about third-party automation, covered below. The same questions apply to traxy. The traxy MCP is traxy's own MCP server, not a LinkedIn product, and traxy is not affiliated with LinkedIn. traxy runs LinkedIn GTM end to end: it finds high intent leads from LinkedIn activity, researches each one and runs personalized LinkedIn and email sequences from your own connected sender accounts. You run that outreach in the app, through trax, or from the traxy MCP in Claude, ChatGPT, Codex, Cursor or Grok after a yes in chat. It runs on autopilot only after you approve the campaign, or you approve every message, and replies, unsubscribes and hard bounces stop the sequence. See LinkedIn GTM from your AI chat and LinkedIn outbound with traxy.
What do third-party LinkedIn APIs and MCP servers do?
They act through your own LinkedIn account. You connect an account you own, and the vendor's service carries out actions such as searching people, sending connection requests and messaging from it, through a REST API, an MCP server for AI assistants, or both. None of them is LinkedIn's API, and each vendor's own wording on its relationship with LinkedIn is quoted below. Each was checked November 2026.
Unipile
Unipile's LinkedIn API page is aimed at software companies. It connects your users' authenticated LinkedIn accounts (Classic, Recruiter and Sales Navigator) to your app through one API, with messaging, InMail, connection invitations and conversation sync. Users connect through Unipile's hosted sign-in, or with credentials, cookies or a Chrome extension. Unipile says it is not affiliated with, endorsed by or sponsored by LinkedIn. Fits better than traxy if you are building LinkedIn messaging into your own product for your users.
Linked API
Linked API automates messaging, connection requests, search and data extraction on LinkedIn and Sales Navigator through an API, SDK, CLI, no-code platforms or its MCP server for Claude, ChatGPT, Codex, Cursor and other clients. It says every action runs in a dedicated cloud browser for your account, and that it is not affiliated with, authorized by, endorsed by or sponsored by LinkedIn. Fits better than traxy if you want to script single LinkedIn and Sales Navigator actions yourself, such as search and data extraction, through an API, SDK or CLI.
GTM API
GTM API (gtm-api.com) describes itself as an MCP-first LinkedIn API, where one key lets an AI agent search, connect, message and enrich on your own LinkedIn accounts through MCP tools or REST. It says each account runs in its own isolated cloud browser with a dedicated proxy and smart limits, and its MCP docs say outward actions such as sends return a preview and need a confirmation step. GTM API says it is not affiliated with, endorsed by or sponsored by LinkedIn. Fits better than traxy if you are a developer or GTM engineer who wants LinkedIn actions as typed tools across several accounts.
proReach
proReach is a LinkedIn outreach tool that finds people from a description of your buyer and runs connection request and message sequences from your own profile. Its hosted MCP server gives an AI agent 13 tools to read the workspace, draft a campaign, add or find leads, launch behind a confirmation step, pause, and report on metrics and replies. proReach says the agent's tools only write campaign plans and proReach performs the LinkedIn actions later, inside daily caps, working hours and cooldowns, and that sending replies stays a human action. Its MCP page says no LinkedIn MCP server available today, its own included, is endorsed by LinkedIn. Fits better than traxy if you want a LinkedIn-only tool where the AI agent only writes campaign plans and replies always stay a human action.
ReachHunt
ReachHunt offers an API and an MCP server for LinkedIn and X (Twitter): messages, lead lists from searches, posts and groups, campaigns with connection requests and InMails, a shared inbox and webhooks for replies. It says it works through the LinkedIn accounts you connect to ReachHunt with its browser extension, and that ReachHunt is not affiliated with LinkedIn Corporation. Fits better than traxy if you also want X DMs in the same inbox and API.
Several of these vendors describe pacing, limits or warm-up meant to protect your account. No tool can promise account safety, for the reason in the next section.
What does LinkedIn say about third-party automation?
LinkedIn doesn't permit third-party software that automates activity on its website, and says members who use such tools risk having their accounts restricted or shut down. Its help page on prohibited software and extensions names crawlers, bots, browser plug-ins and extensions that scrape, modify the appearance of or automate activity on LinkedIn's website. It quotes the User Agreement's ban on using bots or other unauthorized automated methods to access the service, add or download contacts, or send or redirect messages.
LinkedIn's page on automated activity asks members whose accounts are restricted for automated activity to disable the software. It also asks members who use third-party software for productivity reasons, and want LinkedIn to consider partnering with it, to contact LinkedIn.
This applies to every tool that sends on LinkedIn for you, traxy included. No vendor can promise your account won't be restricted. You can still send from your own account, stay well inside LinkedIn's limits, and review messages before they go out.
Is there a LinkedIn API to run my outreach from?
No. LinkedIn doesn't offer one, so teams pick one of three routes. Outreach is more than sending: you need the right people, a reason to contact each one, a message that uses that reason, follow-ups, rules that stop a sequence when someone replies, and an inbox. The routes differ in how much of that you build yourself.
Build on a third-party LinkedIn API. Unipile, Linked API, GTM API and ReachHunt give your code or AI agent LinkedIn actions on accounts you connect. You build the rest: who to contact, research, copy, sequence logic, stop rules and the inbox. If your product fits one of LinkedIn's partner programs, you can apply to it, but LinkedIn says it isn't currently accepting new Sales Navigator API partners.
Use a LinkedIn GTM tool that runs the campaigns. The tool finds the people, prepares the messages and runs LinkedIn and email sequences from your connected sender accounts, with review steps before anything sends. traxy works this way, in its app or from your AI chat through the traxy MCP.
Mix the two. Run campaigns in a GTM tool and read its lead data from your own code. In traxy, the REST API is for reads (leads, signals and engagement history), and the traxy MCP is where actions happen, from research to launching campaigns.
For the prospecting process itself, from picking who to contact to the first message, start with our LinkedIn prospecting guide.
Where does traxy fit?
traxy is a LinkedIn GTM tool that covers both halves of outbound. It finds high intent leads from LinkedIn activity and runs LinkedIn and email outreach to them from your own connected sender accounts. We are the vendor here, and traxy is not affiliated with LinkedIn.
Finding leads. traxy finds people who write, comment on or like posts about the problem you solve (Signals), people who engage with the profiles, posts and company pages you track (Tracking), and people you describe in plain English, searched across 71M+ scanned LinkedIn likes, posts and comments (social intent search). A person counts as a lead only with a 50% or higher ICP match, and each lead shows the post or comment behind it.
Running outreach. A campaign can research each lead for the facts you ask for, groups leads by signal with a personalized message variant for each group, and runs LinkedIn and email sequences from the sender accounts you connect, within each account's limits, active hours and ramp-up (sender accounts). You test the plan on sample leads with nothing sent, review who joins and who is skipped at launch, then approve each message in a review queue or let the approved campaign send (review and launch). Replies, unsubscribes and hard bounces stop the sequence, and conversations land in one inbox.
From your AI assistant. The traxy MCP server connects Claude, ChatGPT, Cursor, Codex and other clients through OAuth. From chat you can list and research leads, run social intent search, start a confirmed discovery run, qualify a post's audience, update your ICP and Signal Brief, manage Tracking, apply lead actions, request contact lookups and send leads to a Webhook, Clay, n8n or Zapier destination. You can also draft a campaign, test it on sample leads, preview and launch it, manage its sequence and sender accounts, send one-off LinkedIn messages, reply in the inbox, pause, resume or stop a lead's sequence and read outbound performance.
From your code. The REST API is for reads: leads, signals, tracked profiles, analytics and meetings, with an API key for the workspace.
Yes, you can run LinkedIn and email outreach from your AI chat through the traxy MCP, and nothing sends until you say yes. There is no approval card in an AI chat, so your client shows what it is about to do, such as launching a campaign, sending a message or replying in the inbox, and waits for your explicit yes. Actions that use capacity ask first too. Messages and campaigns send from your own connected LinkedIn and email accounts, and replies, unsubscribes and bounces stop a sequence. The REST API is for reads; the MCP is where actions happen. To set it up, you sign in to traxy from your AI client, pick workspaces and approve, with no API key. In the app, trax, the traxy agent, can build the same campaign with you. See LinkedIn GTM from your AI chat for the full workflow.
See how campaigns run in LinkedIn outbound with traxy, or compare MCP options in Claude MCP servers for sales teams.
Which route fits you?
You are | Route | Examples |
|---|---|---|
A developer building LinkedIn features into your own product | A third-party LinkedIn API on your users' connected accounts, or a LinkedIn partner program if your product qualifies | Unipile, Linked API, GTM API |
A GTM engineer who wants an AI agent to act on LinkedIn from chat | A third-party LinkedIn MCP server; check that sends wait for your confirmation | Linked API, GTM API, proReach, ReachHunt |
A GTM team that wants high intent leads plus LinkedIn and email outreach in one place | A LinkedIn GTM tool that runs campaigns from your connected sender accounts, from its app or your AI chat, with your yes before anything sends | traxy |
An agency running outbound for clients | The same GTM tool route, run per client, sending from each client's own connected accounts | traxy, with each client in its own workspace (agency docs) |
FAQ
Can I send LinkedIn messages through LinkedIn's official API?
Only as an approved partner. LinkedIn restricts its Messages API to approved partners, and its rules say each message must come from a specific member action, not an automated or scheduled event. The open, self-serve permissions don't include messaging.
Can I send connection requests through the LinkedIn API?
LinkedIn's Invitations API sends invitations on behalf of the signed-in member, and LinkedIn restricts it to approved partners.
Is there an official LinkedIn MCP server for outreach?
We found none in LinkedIn's documentation. LinkedIn's Hiring Pro connector in Claude, announced October 21, 2026, covers job posts only. The LinkedIn MCP servers for outreach we found, such as Linked API, GTM API, proReach and ReachHunt, are third-party.
Does an "official Claude connector" mean LinkedIn approved the tool?
No. It means the vendor's MCP server is listed in Claude's Connectors Directory, with a Verified or Community label for how much Anthropic reviewed it. Anthropic says the developer operates the connector and controls its tools. The listing says nothing about LinkedIn's approval, so check how the vendor connects to LinkedIn.
Is the LinkedIn Sales Navigator API open to new developers?
No. LinkedIn's Sales Navigator Application Platform docs say it is not currently accepting new partners for the Sales Navigator API.
Can the traxy MCP server send LinkedIn messages or launch campaigns?
Yes. Through the traxy MCP you can draft a campaign, test it on sample leads, preview and launch it, manage its sequence and sender accounts, send one-off LinkedIn messages and reply in the inbox, as well as find, qualify and research leads. Before anything sends or launches, your AI client shows what it is about to do and waits for your explicit yes. Messages go out from your own connected LinkedIn and email accounts.
Is it safe to use a third-party LinkedIn API?
LinkedIn's help pages say it doesn't permit third-party software that automates activity on its website, and that members who use such tools risk restriction. No vendor, traxy included, can promise your account won't be restricted.
Related reading
Keep reading
All Prospecting & Outreach guides
LinkedIn Prospecting (2026): How to Prospect on LinkedIn Step by Step, With Message Examples & Signals That Tell You Who to Contact First
How to prospect on LinkedIn step by step: profile, ICP, list building, message examples, signals, niche markets, tools and every outreach guide we publish.
Sales Prospecting Statistics (2026): Follow-Ups, Response Time and Reply Rates
Sales prospecting statistics for 2026 on follow-ups, lead response time, cold email and cold call reply rates and SDR metrics, each linked to its source.
Best Clay Alternatives (2026): 7 Tools for Signal-Based Prospecting
Compare the best Clay alternatives in 2026 for signal-based prospecting: traxy, Apollo, Persana, Common Room, Unify, Sales Navigator, and ZoomInfo.