LinkedIn API

Fetch public LinkedIn data with one API

Name: LinkedIn Data API
Brand: SocialCrawl
Availability: InStock

Fetch public LinkedIn data as structured JSON with one SocialCrawl API key. Same Post, Comment, and Author schema as every other platform. Reads are priced in credits.

Read the docs How it works Try live

/v1/linkedin

44 active endpoints

GET /v1/linkedin/profile
GET /v1/linkedin/profile/full
GET /v1/linkedin/profile/posts
GET /v1/linkedin/company
GET /v1/linkedin/company/posts
GET /v1/linkedin/post
GET /v1/linkedin/post/comments
GET /v1/linkedin/search/people
GET /v1/linkedin/search/posts
GET /v1/linkedin/search/jobs

What LinkedIn endpoints does SocialCrawl ship?

44 live read endpoints for public LinkedIn data. People and company profiles, posts, comments, jobs, and search. Data API only. No private InMail.

Profile

5 credits

/v1/linkedin/profile

Get LinkedIn user profile.

url

Full profile

5 credits

/v1/linkedin/profile/full

LinkedIn company profile, recent posts, and computed analytics in one call.

url, posts, cursor, include

Profile posts

5 credits

/v1/linkedin/profile/posts

List a LinkedIn member's posts.

url, cursor, page

Company

5 credits

/v1/linkedin/company

Get LinkedIn company page.

url

Company posts

5 credits

/v1/linkedin/company/posts

List LinkedIn company posts.

company_id, page, sort_by

Post

5 credits

/v1/linkedin/post

Get LinkedIn post details.

url

Post comments

5 credits

/v1/linkedin/post/comments

Get LinkedIn post comments.

url, page, post_type, sort_order

People search

10 credits

/v1/linkedin/search/people

Search LinkedIn people.

query, page, first_name, last_name, title

Post search

5 credits

/v1/linkedin/search/posts

Search public LinkedIn posts by keyword.

query, page, sort_by, date_posted, content_type

Job search

10 credits

/v1/linkedin/search/jobs

Search LinkedIn jobs.

query, page, date_posted, experience_level, job_type

LinkedIn API44 endpoints supported

View docs

Returns a LinkedIn member's public profile: full name, headline, location, follower and connection counts, profile picture, and profile URL.

Use it as the starting point for any person lookup, then call the profile sub-endpoints for their experiences, skills, or posts.

5 credits

GET/v1/linkedin/profile?url=https%3A%2F%2Fwww.linkedin.com%2Fin%2Fwilliamhgates%2F

url

url · Full URL of the LinkedIn profile page

$ curl https://www.socialcrawl.dev/v1/linkedin/profile?url=https%3A%2F%2Fwww.linkedin.com%2Fin%2Fwilliamhgates%2F \
    -H "x-api-key: sc_YOUR_API_KEY"

idle

// Running this live needs your own API key. Hit "Try it" to see an example response

How the LinkedIn API works

LinkedIn is a normal SocialCrawl social surface. You call GET /v1/linkedin/… with an API key, spend credits on live misses, and get a single JSON envelope back. No second SDK.

Authenticate every call

Send your key in the x-api-key header. The same key works across the SocialCrawl catalog.

GET with query params

Routes are GET. Pass handles, urls, queries, and cursors as query strings. We validate formats before charging.

Pay in credits, not seats

Live misses debit the route tier. Cache hits cost 0. Empty or hard failures refund.

Read one JSON envelope

Every response is the same shape: success, data, credits_used, credits_remaining, request_id, cached.

The usual integration chain

Most products resolve an account, page content, then deepen only the posts that matter.

01Account

GET /v1/linkedin/profile

Author-shaped profile

Resolve the handle or id once.

02Feed

GET /v1/linkedin/profile/full

PostList of recent public items

Page with cursor or after when the route supports it.

03Item

GET /v1/linkedin/profile/posts

Full Post for one URL or id

List rows are not enough when you need the full record.

04Comments

GET /v1/linkedin/company

CommentList when the platform exposes it

Expand only when a thread matters.

request

GET /v1/linkedin/profile
  ?url=https://www.linkedin.com/in/williamhgates/
Host: www.socialcrawl.dev
x-api-key: sc_your_api_key_here

response envelope

{
  "success": true,
  "data": { "/* Author | Post | PostList | CommentList | … */": true },
  "credits_used": 1,
  "credits_remaining": 9999,
  "request_id": "req_…",
  "cached": false
}

What lands in data

Field names match the rest of SocialCrawl where archetypes align.

Authorprofile

id, username, display_name, avatar_url, bio, followers, url, ext

PostList / Postprofile/full

items[].post with id, url, content, engagement, author, published_at, ext

CommentListprofile/posts

items[] with author, content.text, engagement, published_at when comments ship

Search / Mediacompany

search hits, media metadata, or transcripts depending on route

Inside the gateway

Same request lifecycle as every other /v1 platform endpoint.

Edge receives the call

Next.js catch-all routes into the Hono social API. We mint a request_id, authenticate the key, then enforce rate limit and concurrency.

Validate, then debit

Registry lookup finds the route. Required params run first. Invalid input returns 400 with no charge. Valid calls debit before upstream work.

Cache or fetch

A deterministic cache key is built from platform + resource + params. Hit: credits_used = 0. Miss: upstream fetch with retries and circuit breaker.

Normalize and return

Upstream JSON is mapped to Author / Post / PostList / CommentList (or route archetype), validated, wrapped in the success envelope, and logged for billing audit.

Billing rules that matter in production

Standard live miss: tier cost (often 1 credit)
Advanced reads: typically 5 credits
Premium reads: typically 10 credits
Metered routes: min floor when documented
Cache hit: 0 credits
Empty / hard fail: auto-refund
Bad params: 400, never charged
No credits: 402, never charged
Disabled routes: 503, never charged

How we get the data

LinkedIn is public-read data on SocialCrawl. We normalize it into the shared schema so your code does not learn a second OAuth flow.

What LinkedIn is for this API

Public LinkedIn surfaces exposed by the registry. Read-only for research, monitoring, and product jobs.

How SocialCrawl reaches it

Social-read upstreams behind one gateway. Prism composites combine legs when a fat route is registered.

What leaves our edge

Unified JSON envelope: success, data, credits_used, request_id, cached. Shared Author / Post / Comment leaves where archetypes align.

What we do not ship live

No write endpoints and no private inbox. Disabled routes stay out of the active count. Prefer registry docs for the live inventory.

field map sketch

public profile / channel→ author.*profile identity and counters

public post / media→ post.* / items[].postpost content and engagement

comment page / tree→ CommentList items[]comments or search hits when present

What this API is used for

The jobs this API is most often used for.

44active LinkedIn endpoints in the registry

1 / 5 / 10credit ladder across standard, advanced, premium

B2B prospecting and company content monitoring

Callers concentrate on profile, content lists, search, and deepen paths on LinkedIn. People, company, jobs, and posts on the shared schema with credit pricing instead of a LinkedIn partnership app for these public reads.

Detail reads are typically a few seconds on live miss. Search and fat composites are slower paths.

What people build with the LinkedIn API

The jobs LinkedIn data is most often used for. Each one is a full recipe with the endpoint chain and pricing.

Social listeningPost search with date filters for B2B conversation.

Comment scrapingComments and comment replies on a public post URL.

Creator analyticsCompany pages and the posts they publish.

Identity resolutionCompany and profile resolution for the professional lane. Our least stable upstream, so verify before you rely on it.

Market researchPost search with date filters. Useful for B2B phrasing, and the upstream is our least stable, so keep a second source on any claim.

Video transcriptsPost text comes back inside the post record itself. The upstream here is our least stable, so verify before you depend on it.

Ad intelligenceAd search and ad detail for B2B creative. The upstream here is our least stable, so keep a second source on anything you report.

Use case examples

Common ways teams put this data to work, and the stack each one tends to run.

Monitoring jobs

Python, cron, Slack bots

Poll profiles and feeds on LinkedIn. Alert when engagement velocity jumps.

Research and VoC

Node, notebooks, BI loads

Search and expand posts for brand, product, and competitor language on LinkedIn.

Backend product jobs

Go, workers, Explorer

Wire resolve to list to detail into pipelines. Cache hits keep recurring runs cheap.

Call it in two lines

Live misses spend credits by tier. Cache hits are free. Empty or hard failures refund.

curl "https://www.socialcrawl.dev/v1/linkedin/profile?url=https://www.linkedin.com/in/williamhgates/" \
  -H "x-api-key: sc_your_api_key_here"

curl "https://www.socialcrawl.dev/v1/linkedin/profile/full?url=https://example.com/…" \
  -H "x-api-key: sc_your_api_key_here"

LinkedIn on SocialCrawl

Same key as the rest of the catalog

Platform docs Get an API key

Endpoints

What data does the LinkedIn API return?

Every endpoint returns structured JSON in a unified envelope. Computed fields such as engagement rate and content category are included only where the endpoint supports them and the required source inputs are present.

ProfileGet LinkedIn user profile CompanyGet LinkedIn company page with its full About tab PostGet LinkedIn post details Search PeopleSearch LinkedIn people Company PeopleList people at a LinkedIn company Post CommentsGet LinkedIn post comments Profile PostsList a LinkedIn member's posts Profile ReactionsList posts a LinkedIn member reacted to Post RepostsList reposts of a LinkedIn post Group PostsList posts in a LinkedIn group Company Affiliated PagesList a company's affiliated/showcase pages Post Comments RepliesList replies to a LinkedIn comment Profile ExperiencesList a member's work experiences Profile EducationsList a member's education history Profile SkillsList a member's skills Profile HonorsList a member's honors and awards Profile CertificationsList a member's licenses and certifications Profile PublicationsList a member's publications Profile VolunteersList a member's volunteer experiences Profile RecommendationsList recommendations for a member Profile Interests CompaniesList companies a member follows Profile Interests GroupsList groups a member follows Profile ImagesList a member's image posts Profile VideosList a member's video posts Profile CommentsList a member's comments Post ReactionsList reactors on a LinkedIn post Company JobsList a company's job postings Search JobsSearch LinkedIn jobs Search LocationResolve a location to a LinkedIn geocode id Search SchoolsSearch LinkedIn schools Search IndustryResolve an industry name to a LinkedIn industry id Profile AboutGet a member's account freshness signals (NOT the profile About section)Profile ContactGet a member's public contact info Profile StatsGet a member's follower + connection counts Company Job CountGet a company's open job count Company InsightsGet aggregate insights about a company's members GroupGet LinkedIn group details JobGet LinkedIn job details Company PostsList LinkedIn company posts AdGet LinkedIn ad details Ads SearchSearch LinkedIn ads Search PostsSearch public LinkedIn posts by keyword Post TranscriptGet a LinkedIn post video transcript Profile FullLinkedIn company profile, recent posts, and computed analytics in one call.

Comparison

How does SocialCrawl compare to LinkedIn Marketing API for LinkedIn data?

Same LinkedIn data, two very different paths. Auth, rate limits, schema, and cost, side by side.

Feature	SocialCrawl	LinkedIn Marketing API
Authentication	One x-api-key header	OAuth 2.0 with member consent screens
Setup / approval	Sign up and call immediately	Developer app review plus Marketing Developer Platform approval
Rate limits	Credit-based, pay per request	Daily call quotas per app and per member token
Response schema	Unified JSON shared across 51 platforms	LinkedIn-specific response shapes you map yourself
Pricing	1 credit standard, 5 advanced, 10 premium; 100 free credits	Free, but access gated to approved partner use cases
Data coverage	Public profiles, companies, posts, ad and post search, transcripts, Ad Library	Member-authorized data, ad campaign management, and official posting
Maintenance	Schema stays stable when LinkedIn changes internals	You track API versions and partner program requirements

Authentication

SocialCrawl

One x-api-key header

LinkedIn Marketing API

OAuth 2.0 with member consent screens

Setup / approval

SocialCrawl

LinkedIn Marketing API

Developer app review plus Marketing Developer Platform approval

Rate limits

SocialCrawl

Credit-based, pay per request

LinkedIn Marketing API

Daily call quotas per app and per member token

Response schema

SocialCrawl

Unified JSON shared across 51 platforms

LinkedIn Marketing API

LinkedIn-specific response shapes you map yourself

Pricing

SocialCrawl

1 credit standard, 5 advanced, 10 premium; 100 free credits

LinkedIn Marketing API

Free, but access gated to approved partner use cases

Data coverage

SocialCrawl

Public profiles, companies, posts, ad and post search, transcripts, Ad Library

LinkedIn Marketing API

Member-authorized data, ad campaign management, and official posting

Maintenance

SocialCrawl

Schema stays stable when LinkedIn changes internals

LinkedIn Marketing API

You track API versions and partner program requirements

FAQ

Have a question? We got answers

Find answers to frequently asked questions about SocialCrawl's API, pricing, and capabilities.

How do I scrape LinkedIn data with an API?

SocialCrawl provides 44 LinkedIn API endpoints, including profiles, company pages, posts, company post feeds, post search, ad search, video transcripts, and the LinkedIn Ad Library. Send a GET request with your x-api-key. No OAuth 2.0 flow, no app review, no LinkedIn Marketing Developer Platform approval required.

What LinkedIn endpoints does SocialCrawl offer?

44 endpoints spanning member profiles, company pages, posts, search, jobs, and the Ad Library, including profile (user data), company (company pages), post (single post details), company/posts (recent company posts), search/people (people search), search/posts (keyword post search), search/jobs (job search), the profile sub-resources (experiences, educations, skills, certifications, and more), post/transcript (video transcript of a post), and ads/search and ad (the Ad Library).

How much does the LinkedIn API cost on SocialCrawl?

Profile, company, post, company/posts, and search/posts cost 1 credit each on the standard tier. The Ad Library ad endpoint costs 5 credits on the advanced tier, and post video transcripts cost 10 credits (premium). Every new account gets 100 credits free, no credit card required.

Do I need a LinkedIn OAuth app or Marketing API approval?

No. SocialCrawl works without OAuth 2.0 credentials, a LinkedIn developer app, or Marketing Developer Platform approval. Pass your SocialCrawl x-api-key and a LinkedIn URL. The response comes back in a unified schema consistent with every other platform we support.

Is it legal to scrape LinkedIn with this API?

SocialCrawl reads only publicly available LinkedIn data through our upstream provider, the same pages any logged-out visitor can see. You remain responsible for complying with LinkedIn's User Agreement and any applicable data-protection law in your use case. SocialCrawl operates under a documented GDPR legitimate-interest framework: public, logged-out data only, no credential use, short-lived caches (2 to 30 minutes) with no persistent store, and a public opt-out channel for anyone whose public info appears in responses. Full details: socialcrawl.dev/legal/public-data-notice.

Can I pull LinkedIn Ad Library data for competitor research?

Yes. The ad endpoint wraps the LinkedIn Ad Library: pass an Ad Library URL and get the full record: creative, copy, advertiser, impression range, and the targeting LinkedIn discloses. Ideal for ad intelligence, creative research, and competitive monitoring on B2B campaigns.

What is the best LinkedIn scraper API?

SocialCrawl covers a wide read surface for public LinkedIn data: 44 endpoints, including profiles, company pages, posts, company feeds, ad search, post search, video transcripts, and the Ad Library. Standard calls cost 1 credit, advanced 5, premium 10, and every new account starts with 100 free credits, no OAuth app or partner approval.

Is there a LinkedIn data API?

Yes, SocialCrawl works as a LinkedIn data API for public data, returning member profiles, company pages, posts, company feeds, people and post search, video transcripts, and the LinkedIn Ad Library as unified JSON. LinkedIn's official API does exist, but it is partner-gated behind Marketing Developer Platform approval and mostly serves member-authorized data and ad campaign management. SocialCrawl needs no OAuth app or partner approval: pass your x-api-key and a LinkedIn URL, from 1 credit per request with 100 free credits on signup.

LinkedIn scraping API vs the official LinkedIn API: what's the difference?

With SocialCrawl there is no app review or approval queue. Sign up and call LinkedIn endpoints immediately with a single x-api-key. Responses share one unified schema with every other SocialCrawl platform, and credit-based pricing replaces per-platform quotas. Official APIs are still the right choice for posting and other write actions: SocialCrawl is read-only data.

Ask AI about SocialCrawl

Ask ChatGPT Ask Perplexity Ask Gemini Ask Claude Ask Grok

Read the LinkedIn API reference in the docs

🤖 AI agent or LLM? Read this page as markdown