# gtm-api.com > The LinkedIn API and MCP server for AI agents. Give an AI agent one key to search, connect, message, and enrich on LinkedIn, on owned accounts that stay safe by design. 20,000+ LinkedIn accounts run on the gtm-api.com stack, and under 1% of them have ever been restricted. LinkedIn is the live channel, with email, messengers and calendars on the roadmap on the same typed contract. ## Product pages - [gtm-api.com](https://gtm-api.com/): The LinkedIn API and MCP server for AI agents, on accounts the customer owns. - [Use cases](https://gtm-api.com/use-cases/): Who runs this and what they run it for. - [AI SDR](https://gtm-api.com/use-cases/ai-sdr/): An agent that researches accounts, writes the opener and executes LinkedIn outreach on owned accounts, inside per-account safety limits. - [GTM engineers](https://gtm-api.com/use-cases/gtm-engineers/): Connect Claude, ChatGPT or a custom agent to LinkedIn through one typed contract. - [Agencies](https://gtm-api.com/use-cases/agencies/): Onboard clients without touching their password, and pull health and analytics for every account in one call. - [Platforms](https://gtm-api.com/use-cases/platforms/): Ship LinkedIn inside your own product: one typed contract, native account connection, per-account pricing. - [Account providers](https://gtm-api.com/use-cases/account-providers/): Warm, secure and lease LinkedIn account fleets: smart-limit warm-up, scoped expiring access grants, bulk actions across the fleet. - [LinkedIn automation in 2026: how it works](https://gtm-api.com/linkedin-automation/): The category hub: where LinkedIn automation runs (browser extension, desktop app, the vendor's cloud, an API), what tools charge, the limits and rules it works under, and the page that covers each, with gtm-api.com's API and MCP server first. - [LinkedIn scraping in 2026: how each route works](https://gtm-api.com/linkedin-scraper/): The scraping hub: what LinkedIn data is collected for, the four routes to it (LinkedIn's own APIs, a browser extension, a scraper vendor or dataset, an API that reads through an account you connect), what each costs and puts at risk, and where the User Agreement and the law stand, with gtm-api.com's API and MCP server first: searches and profile reads on LinkedIn accounts the customer owns, from $10/account with calls not metered. ## Free tools - [Free tools](https://gtm-api.com/tools/): Small checks that run without an account. - [LinkedIn shadowban checker](https://gtm-api.com/tools/linkedin-shadowban-checker/): Send one connection request to a real profile on our side and see within two minutes whether it arrived. One check per profile a month, no signup. Every account connected to gtm-api.com gets the same probe automatically on its first sync. - [LinkedIn limits calculator](https://gtm-api.com/tools/linkedin-limits-calculator/): Six facts about an account in (age, recent sends, limit hits, blocks, sessions, profile completeness), a warm-up score and a daily ceiling per action out. The math gtm-api.com smart limits run on every connected account, computed in the browser, no signup. - [LinkedIn MCP config generator](https://gtm-api.com/tools/linkedin-mcp-config-generator/): Paste an API key or choose browser sign-in, pick Claude Desktop, Claude Code, claude.ai, ChatGPT, Cursor, VS Code, Codex or another MCP client, and copy the exact config or command for https://mcp.gtm-api.com/mcp, where it goes and a one-line test. Built in the browser: the key is never sent. - [LinkedIn post date extractor](https://gtm-api.com/tools/linkedin-post-date-extractor/): Paste a LinkedIn post, comment or activity link, a urn or the bare id, and get the exact date and time it went up, in UTC and the visitor's time zone, decoded from the first 41 bits of the post id. Runs in the browser: no request to LinkedIn or anywhere else, nothing stored. ## Guides - [LinkedIn API in 2026: The Developer Guide](https://gtm-api.com/linkedin-api/): What the official API covers, what a third-party LinkedIn API adds, pricing and safety. - [LinkedIn MCP Server](https://gtm-api.com/linkedin-mcp-server/): Give your AI agent LinkedIn access - connect Claude, ChatGPT or Cursor to one endpoint, with typed tools for every LinkedIn action. - [Safe LinkedIn Automation](https://gtm-api.com/safe-linkedin-automation/): Why accounts get banned, 2026 limits, and how to automate without getting restricted. - [LinkedIn Connection Limits (2026)](https://gtm-api.com/linkedin-connection-limits/): The weekly cap, the per-account daily ceiling, the rolling window, and how sending capacity is earned. - [LinkedIn Limits (2026)](https://gtm-api.com/linkedin-limits/): Every cap per action and per plan, with reset times: invitations, messages, InMail, search, the 30,000 ceiling. - [LinkedIn Account Restricted](https://gtm-api.com/linkedin-account-restricted/): Temporary vs permanent restrictions, how to restore access, and how to avoid the next one. - [Scaling LinkedIn Automation](https://gtm-api.com/scaling-linkedin-automation/): What running more than one account takes: warm-up, per-account ceilings, and the real multiplication math. - [LinkedIn API Pricing (2026)](https://gtm-api.com/linkedin-api-pricing/): The free official tier, per-account vs per-call models, and gtm-api.com's numbers, from $39/account scaling to $10, unlimited calls. - [Best LinkedIn API (2026)](https://gtm-api.com/best-linkedin-api/): Account-based APIs, scraper APIs and MCP compared on access, account model, pricing shape and what sits behind each safety claim. - [LinkedIn API Rate Limits (2026)](https://gtm-api.com/linkedin-api-rate-limits/): The two throttle levels, the daily reset, the three products that publish real numbers, and what a 429 does and does not tell you. - [Sales Navigator API (2026)](https://gtm-api.com/sales-navigator-api/): What SNAP is, why it is closed to new partners, what its terms rule out, and how teams reach Sales Navigator through a seat instead. - [How to Get LinkedIn API Access (2026)](https://gtm-api.com/linkedin-api-access/): What is self-serve, what needs partner approval, which programs are closed, and why LinkedIn issues no object called an API key. - [LinkedIn Profile Data API (2026)](https://gtm-api.com/linkedin-profile-data-api/): What LinkedIn's own API returns about a member, the 24-hour storage cap on most profile data, and the three third-party routes to a profile: dataset, scraper, account-based API. - [Connect LinkedIn to Claude (2026)](https://gtm-api.com/connect-linkedin-to-claude/): Per-client MCP setup for Claude Desktop, claude.ai and Claude Code, why the config file silently drops a remote server, and when an API key replaces the browser sign-in. - [15 Best LinkedIn Automation Tools (2026)](https://gtm-api.com/best-linkedin-automation-tools/): Operator tools ranked on account safety and stability, on published specs, with where each one runs the automation. - [What Is a Go-to-Market (GTM) Strategy?](https://gtm-api.com/what-is-gtm/): How a company brings a product to a market and turns it into revenue, from first principles to the AI-agent era. - [LinkedIn Messaging API](https://gtm-api.com/linkedin-messaging-api/): LinkedIn documents a Messages API and an Invitations API, both sit in the closed Compliance program, no published scope grants sending, and the terms bar any send the member did not personally trigger. - [LinkedIn Message Limits (2026)](https://gtm-api.com/linkedin-message-limits/): No daily cap on DMs to connections, 50 InMail credits a month on Sales Navigator, the unpublished thread limit that actually stops volume senders, and the pacing that stays under it. - [LinkedIn Search Limits (2026)](https://gtm-api.com/linkedin-search-limit/): What spends the commercial use limit, what does not, the midnight-PST reset on the 1st, why the limit looks stuck, and search pacing for automated accounts. - [LinkedIn Integrations (2026)](https://gtm-api.com/linkedin-integrations/): n8n, Zapier and Make all ship a LinkedIn app, and all three only publish content. What each built-in integration covers, why none of them can send a connection request, and how to add the outreach half without losing the account. - [Automate LinkedIn with n8n (2026)](https://gtm-api.com/automate-linkedin-with-n8n/): Three outreach workflows built from HTTP Request and Webhook nodes: enrich then invite, follow up on acceptance, and route replies, with the URN step and the Test-versus-Production webhook trap that break most tutorials. - [LinkedIn Shadow Ban](https://gtm-api.com/linkedin-shadow-ban/): The name is informal, the mechanism is published twice: policy enforcement may limit content visibility and feed algorithms taper distribution, neither with a notice. The 10-minute check, what precedes a sag, and the recovery sequence. - [LinkedIn Scraping vs a Safe API (2026)](https://gtm-api.com/linkedin-scraping-vs-api/): What counts as scraping, the two hiQ rulings on the legal question, why logged-in scrapers lose accounts, and when a scraper, a dataset or an account-based API is the right route to LinkedIn data. - [LinkedIn Jobs API](https://gtm-api.com/linkedin-jobs-api/): LinkedIn's one official jobs API only writes: approved partners post and close jobs, new partnerships are closed, and no official endpoint reads a listing. The three products people mean by a jobs API and the route that answers each. - [n8n LinkedIn Node](https://gtm-api.com/n8n-linkedin-node/): n8n's built-in LinkedIn node has one operation, Post: Create. Invitations, messages, enrichment and people search come from a community node you install yourself, and where n8n runs decides whether you can install it at all. - [Zapier LinkedIn Integration (2026)](https://gtm-api.com/zapier-linkedin-integration/): Zapier's LinkedIn app has three actions, no triggers and no search actions. What the three cover, why the company Page dropdown comes back empty, the premium-app rule that decides which route a Free plan can reach, and what each design costs in tasks. - [LinkedIn API Documentation](https://gtm-api.com/linkedin-api-documentation/): The documentation lives on learn.microsoft.com as six business lines, each versioning on its own schedule. How to read a version header, the two different support windows, the /v2 against /rest split, and the four things the docs never publish. - [LinkedIn Posts API](https://gtm-api.com/linkedin-posts-api/): Publishing to a member's feed is self-serve on w_member_social, one of only three open permissions. Reading those same posts back runs on a closed permission, nothing official reads a third party's posts at any tier, and comments and reactions need a separate _feed scope family that refuses an app which can already publish. - [Is Sales Navigator Worth It?](https://gtm-api.com/is-sales-navigator-worth-it/): LinkedIn's published prices, the 25% against 6% annual-discount split, and what the Core to Advanced step actually buys (team and AI features, not more InMail and not more filters). The three absences on every tier, and what cancelling does to your access. - [LinkedIn Search API](https://gtm-api.com/linkedin-search-api/): LinkedIn publishes two search APIs and neither searches LinkedIn: People Typeahead matches name prefixes against your own Page's followers on a restricted permission, and RSC Unified Search is an iframe for ATS vendors. What an account-based search returns instead, and the five profile fields it never fills. - [Unipile Overview](https://gtm-api.com/unipile-overview/): A neutral read of a multichannel API: nine live channels against three announced ones, the published per-linked-account price list, the LinkedIn limits it documents but does not enforce, and an MCP server aimed at developers rather than agents. - [Proxycurl Overview](https://gtm-api.com/proxycurl-alternative/): What the credit-priced data API was (21 endpoints, one bearer key, no LinkedIn account of the customer's), the LinkedIn v. Nubela docket from the January 2025 filing to the July 2025 judgment, why the hiQ CFAA ruling did not help a contract case, and NinjaPear as the only successor Nubela names. - [Is Scraping LinkedIn Legal?](https://gtm-api.com/is-scraping-linkedin-legal/): Three questions under one name. A computer crime: for signed-out public pages the Ninth Circuit says no. A breach of the User Agreement: yes for any account holder, and hiQ settled that half for $500,000. Data protection: where the fines have landed, EUR 240,000 against Kaspr. Which one reaches a B2B team, and what an account-based API changes. - [ConnectSafely.ai Overview](https://gtm-api.com/connectsafely-overview/): An engagement platform with a developer surface behind it: post boosting and AI comments at the front, a REST API of 60+ endpoints, a hosted MCP server and an 86-command CLI on one $10 per connected account plan. The caps its docs publish per action, and the two different safety figures the vendor prints on two of its own pages. - [Linked API Overview](https://gtm-api.com/linkedapi-overview/): A single-vendor read of the developer-shaped LinkedIn API: one dedicated cloud browser per connected account, 58 documented actions posted as workflows to a single endpoint, $49 and $74 per seat with no volume bracket, caps the platform enforces itself across eleven action categories, and a 59-tool MCP server with its source on GitHub. - [How to Avoid Getting Banned on LinkedIn](https://gtm-api.com/avoid-linkedin-ban/): Prevention as a six-step sequence rather than a number to stay under: the account state worth automating, a warm-up ramp that earns capacity, randomized intervals, one browser profile and one IP per account, a full stop on the first refusal, and the counters that move before a ban does. - [HeyReach Overview](https://gtm-api.com/heyreach-overview/): A single-vendor read of the agency-shaped LinkedIn tool: one campaign rotating across a pool of connected accounts it calls senders, every reply pooled in one shared inbox, per-sender pricing with free seats, the weekly and daily ceilings it freezes accounts against, and the Campaign API, hosted MCP server and CLI it has shipped since late 2025. - [Cold LinkedIn Messages: The Three Rulebooks](https://gtm-api.com/cold-linkedin-message-rules/): Three separate rulebooks govern a cold LinkedIn message, and each one punishes something different: the User Agreement risks the account, data protection law risks the company, and best practice risks only the reply rate. Every guideline sorted into one of the three, with the primary source behind each. - [LinkedIn AI Agent](https://gtm-api.com/linkedin-ai-agent/): What an agent does through typed tools on a LinkedIn account you own, what it cannot do whatever the model, what LinkedIn's own documentation rules out, what unattended means once the client stops asking for approval, and the daily budget and health state the account has to hold for any of it to last a month. - [Apify LinkedIn Scraper: Which Actor Does What](https://gtm-api.com/apify-linkedin-scraper/): Apify is a marketplace, so the scraper is whichever actor you picked. Twelve LinkedIn actors for jobs, profiles, companies, posts and Sales Navigator read side by side: who wrote each one, what it charges per result, which ones run inside your own LinkedIn session, and who maintains it when LinkedIn changes. - [LinkedIn Job Scraper](https://gtm-api.com/linkedin-job-scraper/): Two shapes of LinkedIn job scraper and what each one puts at risk: the anonymous route reads public job pages, spends IP addresses and caps out near a thousand results a search, the session-backed route drives your own li_at cookie and puts the account in play. The fields that come back, the 429 and cookie-expiry ceilings, and when a listing was only a proxy for a hiring signal. - [LinkedIn Email Scraper](https://gtm-api.com/linkedin-email-scraper/): A LinkedIn profile does not publish an email address, so every email scraper is a lookup somewhere else: a pattern guess tested against the mail server, a contact database, or the contact card a member shows their connections. What accept_all proves, how to test a match rate, and the CNIL's EUR 240,000 decision against a contact-scraping extension. - [Connect GetSales to gtm-api.com](https://gtm-api.com/connect-getsales-to-gtm-api/): Paste a GoLogin profile ID and gtm-api.com connects a LinkedIn account that already runs in GetSales, no new session, no re-login, the profile keeps its proxy. - [The gtm-api.com AI Assistant](https://gtm-api.com/gtm-api-ai-assistant/): The assistant built into the API docs reads the live API and the changelog and answers in plain English, the fastest way to start with the LinkedIn API. - [The gtm-api.com Free Plan](https://gtm-api.com/gtm-api-free-plan/): One LinkedIn account with the full UI, API and MCP, no card, capped on frequency and volume rather than features. ## Key facts - Interface: MCP-first, plus REST and webhooks - one typed schema. The exact live tool count is the `tools` field of https://mcp.gtm-api.com/health. - Supported AI clients: Claude, ChatGPT, Cursor, LangChain, n8n. - Safety: owned accounts, isolated cloud browser + dedicated proxy per account, warm-up, server-side daily limits, preview→confirm on outward actions. - Pricing: from $39 per connected account/month (to $10 at volume), unlimited API calls and actions, no per-action fees and no feature gates. Forever free plan with 1 connected account and no card, capped on frequency and volume rather than on features. Annual: pay for 12 months, get 15. 5G Proxy add-on: +$15 per account for a dedicated 5G mobile route. ## Get started - [Get an API key](https://app.gtm-api.com/login) - [Developer docs](https://docs.gtm-api.com/) - [API examples on GitHub](https://github.com/gtm-api/linkedin-api-examples) - [Pricing](https://gtm-api.com/pricing/) - [Blog](https://gtm-api.com/blog/) - [YouTube channel](https://www.youtube.com/@gtm-api) ## Optional - [Terms of Service](https://gtm-api.com/legal/terms/) - [Privacy Policy](https://gtm-api.com/legal/privacy/) - [Data Processing Agreement](https://gtm-api.com/legal/dpa/) - [Cookie Policy](https://gtm-api.com/legal/cookies/)