Skip to content
truescrape
Free key

What Can a LinkedIn Profile Viewer Actually See?

Two different things get called a "LinkedIn profile viewer" — browsing anonymously, and pulling public profile data. LinkedIn's own API returns only your own profile, and the law on reading the rest is more nuanced than "public data is fair game."

9 min read · 16 Oct 2026

"LinkedIn profile viewer" means two different things, and the answer depends on which you want. One is viewing a profile without the owner knowing — anonymous browsing, which LinkedIn supports natively. The other is reading profile data programmatically — and there LinkedIn's official API returns only your own profile, the public web profile is deliberately thin behind a sign-in wall, and the legal picture is more nuanced than the "scraping public data is fine" headline suggests.

Here is what each kind of viewer can and cannot see.

Viewing a profile anonymously

LinkedIn has this built in. In private mode, when you look at someone's profile, "their name and other profile information isn't shared with the owners of the profiles they view." The trade-off is symmetric: on a free account in private mode, "you won't be able to see who's viewed your profile either." A Premium account keeps "the list of people who viewed your profile in the last 90 days" even while browsing privately.

So the simplest "profile viewer" is LinkedIn itself, set to private mode. No third-party tool is needed, and nothing about it touches the API or scraping.

What a logged-out visitor sees

If you open a LinkedIn profile without signing in, you get a limited public version of it, and LinkedIn pushes you toward an account. Its own help docs say a member can "control what sections of your profile are eligible for display to people who are not signed in to LinkedIn," and that a visitor "may be prompted to sign up or sign in to LinkedIn to view parts of your public profile."

That public view — the headline, the summary a member chose to expose, current role, location — is the data a "profile viewer" tool can actually read, because it is what LinkedIn serves to anyone. Everything behind the sign-in wall is, by design, not public. To see exactly which fields come back for a real profile, paste a link into the free LinkedIn profile viewer; it reads the same logged-out page and shows an empty field as a dash. How that compares with what Instagram and Snapchat show is in what you can see on each without an account.

Does LinkedIn's API return other people's profiles?

No. This is the part most people get wrong. LinkedIn's current consumer API — Sign In with LinkedIn using OpenID Connect — lets an app authenticate a member and read that member's own basic profile. A call to GET https://api.linkedin.com/v2/userinfo returns only sub, name, given_name, family_name, picture, locale, and email. The older /v2/me endpoint, deprecated in 2023, was the same shape: the signed-in member's "lite profile including their id, name, and profile picture."

There is no official endpoint that takes an arbitrary member and returns their profile. The API is built to log a person in, not to look other people up. Any tool that reads arbitrary public profiles is reading the public web page, not calling a documented API.

The part that is genuinely contested: is it allowed?

This is where "it's public, so it's fine" falls apart, and the honest answer is that it is unsettled and fact-specific.

LinkedIn's robots.txt states plainly that "the use of robots or other automated means to access LinkedIn without the express permission of LinkedIn is strictly prohibited," and it disallows nearly everything for every crawler except LinkedIn's own bot and a short whitelist of search engines. LinkedIn's User Agreement terms say it "doesn't permit the use of any third party software, including 'crawlers', bots, browser plug-ins, or browser extensions ... that scrape, modify the appearance of, or automate activity on LinkedIn's website."

The famous case here is hiQ Labs v. LinkedIn, and it is usually summarized wrong. The Ninth Circuit did rule that scraping public data is likely not a violation of the Computer Fraud and Abuse Act — that is the half everyone quotes. But hiQ ultimately lost: in November 2022, a district court held that LinkedIn's anti-scraping User Agreement terms were enforceable and that hiQ had breached them, and the case ended in a consent judgment with a permanent injunction barring hiQ from scraping and an order to delete the data it had collected. By then hiQ had gone out of business.

The lesson is not "scraping is legal" or "scraping is illegal." It is that the CFAA (a hacking statute) and a platform's contract terms are two separate questions, and you can be clear of one while losing on the other. Meta's own public-Page access tells the same contract-versus-CFAA story, where a court reached the opposite result on the contract claim precisely because the collector was logged out. Reading genuinely public, logged-out data stands on much firmer ground than anything that requires an account — which is exactly why the only defensible version of this is public-only.

What TrueScrape reads

TrueScrape reads the public LinkedIn surface, logged out. The /v1/linkedin/profile endpoint returns a person's public profile as LinkedIn serves it to a signed-out visitor; there are companion endpoints for a company page and its public posts. What it does not do is reach anything behind the sign-in wall — there is no logged-in session, no account, and no attempt to pull private connections, messages, or a member's non-public fields. Person search and the member feed sit behind that wall, so they are not offered.

curl "https://api.truescrape.com/v1/linkedin/profile?url=https://www.linkedin.com/in/some-public-profile/" \
  -H "x-api-key: YOUR_KEY"

So: if you want to view a profile without being seen, use LinkedIn's private mode. If you want public profile data programmatically, know that LinkedIn's API only returns your own profile, that the rest comes off the public page, and that the line worth staying on the right side of is "public and logged-out" — not "public, so anything goes."

Sources

Referenced in this post

Everything described here runs on the same API. You are never charged for a failed request, an empty result, or a cache hit.

Get a free keyAll posts