Before plugging a prospecting tool into LinkedIn, one simple question arises: what does LinkedIn actually say? Articles on the topic often repeat rules of thumb attributed to "the community", without quoting the texts. Yet LinkedIn publishes documents that frame scraping, each aimed at a different party: the member, the software vendor and the data seller.
This article reads them one by one, as published on the date we consulted them (September 29, 2026), says what they do not say, and gives four questions to ask any tool before entrusting it with your account. It is not legal advice.
The User Agreement: what you, as a member, promise
LinkedIn's User Agreement, in the version in force since November 3, 2025, lists the prohibited actions in its section 8.2. Three lines directly concern prospecting.
- Develop, support or use software, devices, scripts, robots or any other means or processes (the text mentions "crawlers, browser plugins and add-ons") to "scrape or copy the Services".
- Use bots or other unauthorized automated methods to access the Services, add or download contacts, send or redirect messages, or create, comment on, like, share or re-share posts.
- Rent, lease, loan, trade, sell or re-sell the Services or related data, or otherwise monetize them, without LinkedIn's consent.
The agreement also states that LinkedIn reserves the right to restrict, suspend or terminate your account if you breach the contract or the law or are misusing the Services.
A LinkedIn help page is even more direct: LinkedIn does not permit any third-party software, including "crawlers, bots, browser plug-ins, or browser extensions", that scrapes data, modifies the appearance of the site or automates activity. It warns that members using such tools risk having their accounts restricted or shut down, and that prohibited tools may become non-operational without notice.
The API terms: what the partner vendor promises
LinkedIn's API Terms of Use (last updated December 13, 2022, effective for existing developers on January 13, 2023) target software vendors with official access. They define "Non-Official Content" as content obtained through scraping, crawling, spidering or any other technology used to access LinkedIn content outside the APIs.
Three prohibitions follow for a partner vendor: combining official content with other LinkedIn content, including Non-Official Content; accessing, storing, displaying or facilitating the transfer of content obtained through scraping, including via a third party; and selling access to an aggregated collection of Member profiles. Another clause forbids using the APIs to automate posting.
The community policies: the data seller and invitations
The Professional Community Policies do not allow content that promotes or distributes, among other things, the "sale of scraped data". They also prohibit using the invitation feature to send promotional messages to people you do not know, and agreeing in advance to like or re-share each other's content (engagement "pods").
| Document | Party targeted | What it prohibits, in short | Stated consequence |
|---|---|---|---|
| User Agreement (section 8.2) | The member | Scraping or copying the Services via software, script, robot or extension; automating contact adds and messages; monetizing data without consent | Account restricted, suspended or terminated |
| Help page on third-party software | The member | Any third-party software that scrapes data, modifies the site or automates activity | Account restricted or shut down; tool may stop working without notice |
| API Terms of Use | The partner vendor | Combining official data with non-official content; aggregating profiles; automating posting | Not specified in the extracts consulted |
| Community policies | Member and data seller | Content promoting the sale of scraped data; promotional invitations to strangers; agreed engagement exchanges | Not specified in the extracts consulted |
What these texts do not say
- They give no numerical quota. The invitation thresholds per day or per week found online are rules of thumb from third-party tools, not rules published by LinkedIn. Our article on LinkedIn prospecting limits covers those benchmarks and the commercial use limit.
- They certify no tool. No document says "this tool is compliant". A vendor claiming so speaks for itself.
- They do not address personal data protection. GDPR compliance for your prospects is a separate subject that does not depend on what LinkedIn allows.
- They change. The cited version of the agreement dates from November 3, 2025; reread the live version before deciding.
Four questions to ask a tool before connecting your account
- How does it access LinkedIn data? An official API, an extension installed in your browser, or a server that connects on your behalf? The texts above prohibit unauthorized scraping and automation whatever the mechanism: the vendor's answer tells you what your account is exposed to.
- Does it use your session? If the tool acts with your login and credentials, you are the one who signed the User Agreement, so you answer for a breach.
- Where does the data it delivers come from? A file of profiles advertised as "extracted from LinkedIn" runs into the texts on selling scraped data.
- What happens if your account is restricted? Your conversations and relationships live on that account. Ask whether the tool keeps serving you without it, and whether you can work without depending on a single source.
Apply these same questions to Ember's Lead Intelligence before connecting a LinkedIn account: no tool, ours included, is exempt from this review.
Further reading
- LinkedIn prospecting limits: key rules and thresholds covers quotas, the commercial use limit and daily activity benchmarks. This article cites no threshold: it reads the contracts and distinguishes the parties they target.
- How do Sales Navigator InMail credits work? is about InMail credits and exports. Here the subject is what is prohibited and which questions to ask a tool.
Sources
- protéger la démocratie à l'ère numérique
- Guide de survie en guerre de l'information | PDF
- API Terms of Use: what developers may not extract, combine or resell as LinkedIn data: source S1
- User Agreement: commercial use, scraping and automation restrictions: source S1
- Professional Community Policies: LinkedIn's rules on automation, fake accounts and spam: source S1
FAQ
Free diagnostic
Test your sales file
Drop an Excel or CSV and check its readiness without sending its rows to Ember.
