Social Fetch
Get API key
All platforms

LinkedIn scraper API

Enrich people and company records from public LinkedIn pages — profiles, company pages, posts, and search — without running a residential-proxy browser farm.

13 endpoints
Get 100 free creditsRead API docs

Why teams use Social Fetch for LinkedIn

LinkedIn is where B2B enrichment goes to die when teams try to DIY it. Headless browsers, checkpoint walls, and session reuse create fragile pipelines that fail in ways that look like "bad data" instead of infrastructure problems.

Social Fetch LinkedIn routes accept public profile or company identifiers and return structured JSON. People search and company post lists support go-to-market and research workflows that only need public fields — not Sales Navigator session hijacking.

Post transcripts help when you want text out of native video posts for CRM notes or research agents.

What LinkedIn data can you get?

  • People profile cards from public LinkedIn URLs or identifiers.
  • Company page metadata for account enrichment.
  • Person and company posts for activity signals.
  • People search for prospecting-style discovery (public results).
  • Post transcripts where available.

LinkedIn API endpoints

Grouped by capability from the live API catalog. Open an endpoint page for parameters and examples — credit notes come from OpenAPI pricing extensions.

Profiles & channels

3

Lists & graphs

2

Content

1

Search & discovery

2

Transcripts

1

Ads

2

Jobs

2

How to call the LinkedIn API

  1. 1. Create your API key

    Sign up at Social Fetch. Use free credits to pull one person profile and one company page before wiring batch jobs.

  2. 2. Call LinkedIn routes

    Use the documented `/v1/linkedin/...` paths with `x-api-key`. Prefer URL or public identifier params as shown in docs — do not invent undocumented query flags.

  3. 3. Write with lookupStatus

    Only upsert when status is found. Keep `requestId` on failed enrichment rows so ops can replay or escalate.

How much does the LinkedIn API cost?

LinkedIn routes document flat and metered credit models depending on the operation (for example search vs single profile). Read each operation's pricing blurb; never assume every LinkedIn call is 1 credit.

See credit packs

Social Fetch vs the official LinkedIn API

LinkedIn's official APIs are partner- and member-authorized. They are appropriate when you build experiences LinkedIn has approved. Social Fetch covers public page enrichment for CRM and research use cases that do not have (and may never get) Marketing Developer Platform access.

LinkedIn API FAQ

Is there a LinkedIn scraper API?

Social Fetch provides REST routes for public LinkedIn people, company, post, and search data without requiring a LinkedIn partner app for those lookups.

Can I fetch LinkedIn company pages?

Yes — company routes return public company page fields suitable for account enrichment.

Do you support LinkedIn people search?

Yes. People search is a documented marketplace route. Pricing may be metered — check the operation page.

How much does the LinkedIn API cost?

Credits vary by route. Profile GETs are typically cheaper than search. See docs and `meta.creditsCharged`.

LinkedIn official API vs Social Fetch?

Official APIs require LinkedIn's access programs and member authorization. Social Fetch is public-data lookup for enrichment pipelines.

Can I get LinkedIn post transcripts?

Where supported, transcript routes accept public post URLs. Confirm coverage and credits in docs.

Will this work behind LinkedIn auth walls?

We only return publicly visible data. Content gated to logged-in networks beyond public visibility is out of scope.

Is LinkedIn scraping legal?

Public-data use still needs your own legal review against LinkedIn's terms and local law. We do not provide legal advice.

Start with LinkedIn data

Create an account, spend the 100 free credits on live LinkedIn routes, then buy a pack when the JSON fits your pipeline. Credits do not expire on pay-as-you-go packs.

Open playgroundView pricing