GTM and CRM teams ask for "LinkedIn API access" and mean: enrich this /in/… URL, pull the company page, list recent posts. LinkedIn's developer portal hears something else: build an approved experience with member OAuth, ads, or Marketing Developer Platform (MDP) scopes.

Those are different products. Confusing them is why enrichment projects stall for months waiting on partner approval that was never going to cover arbitrary public profile GETs. Need sign-in, posting on behalf of a member, ads, or an experience LinkedIn has approved? Use LinkedIn's official APIs. Need public people, company, post, job, or Ad Library JSON for enrichment without a partner deal? Use a public-data API such as Social Fetch LinkedIn — credit-metered, same envelope as other platforms, charge on completed lookups.

The access problem in one paragraph

LinkedIn does not sell a self-serve "enrich any public profile" SKU the way you buy a credit pack elsewhere. Official developer products are gated around apps LinkedIn trusts and members who grant permission. If your feature is "prospect never connected to us; we only have their public LinkedIn URL," you are outside that model. Waiting on MDP approval will not invent a product LinkedIn did not ship.

What LinkedIn's official APIs are for

LinkedIn's developer surface (partner programs, member authorization, Marketing Developer Platform and related products) is built for:

• Sign-in and identity
• Publishing or managing content on behalf of a member who connected
• Ads and approved marketing integrations
• Partner features LinkedIn explicitly opens to a program

That path is correct when your product sits inside LinkedIn's permission model. It is the wrong procurement ticket for CRM enrichment of cold /in/… URLs.

Plain glossary answer: Does LinkedIn have an API?.

Why partner access feels like a wall

Teams that treat "apply for LinkedIn API" as a checkbox hit the same friction:

Approval is not a pricing page. You are not picking Free / Pro. You are asking LinkedIn whether your use case fits a program. Many enrichment and scraping-shaped products never get (and may never need) that access.

Scopes follow members, not public pages. Official reads and writes assume someone authorized your app. A spreadsheet of public URLs is not an authorized member graph.

The sales and compliance process has its own calendar. Roadmaps that block on "when MDP lands" lose quarters. If the feature only needs public fields, that wait was optional.

Vendor concentration risk is real. LinkedIn-only enrichment businesses can vanish (Proxycurl shut down in July 2025 after LinkedIn litigation). See Social Fetch vs Proxycurl for the migration framing — and prefer vendors that are not a single-network bet if your product already spans TikTok and Instagram.

None of this is a complaint that LinkedIn should open unrestricted scrapes. It is a product classification: partner APIs and public enrichment solve different jobs.

Public enrichment is a different product

A public-data LinkedIn API accepts public identifiers (person /in/…, company pages, public post or job URLs) and returns structured JSON your pipeline can upsert. No LinkedIn partner app required for those lookups. No member OAuth for the prospect.

Compliance and ToS still apply to your use of public data. A managed API moves fetch-layer maintenance off your team; it does not erase lawful-use obligations. Read LinkedIn's terms for your use case. I am not your lawyer.

DIY browser farms, session reuse, and Sales Navigator automations are a third path — high maintenance, high breakage, often the wrong compliance story. Tradeoffs: Social Fetch vs DIY scraping. Outreach automation (not a profile schema API): vs PhantomBuster. Creator OAuth / connection-style products: vs Phyllo.

Decision table

If counsel requires LinkedIn-approved access for a specific product surface, stay official for that surface. Enrichment of public pages can still live on a separate public-data key.

What Social Fetch covers on LinkedIn

Social Fetch exposes documented /v1/linkedin/... routes for public people profiles, company pages, organizations, posts, people search, jobs, Ad Library, and post transcripts where available. Responses use the shared { data, meta } envelope — lookupStatus, meta.requestId, meta.creditsCharged — next to TikTok, Instagram, and X.

Typical path:

1. Sign up; spend free credits on one person URL and one company page
2. Call GET /v1/linkedin/profiles with public url params (batchable)
3. Branch on lookupStatus before upsert; keep requestId on failures

Vendor shortlist and official-vs-enrichment ranking: Best LinkedIn data APIs in 2026. Cross-network creator cards: Cross-platform creator profiles.

Billing for enrichment volume

LinkedIn on Social Fetch is credit-metered. Do not assume every call is 1 credit.

From our docs and pricing page:

• 100 free credits on signup, no card
• Profile GETs are typically 2 credits per URL (up to documented batch limits)
• Search and list routes (people search, profile posts, and similar) often cost more — attempt fees plus per-row charges appear on some operations. Read the operation page
• Charge on completed lookups — trust meta.creditsCharged. Pre-send validation errors and our infrastructure failures (lookup_failed, 503 temporarily_unavailable) do not debit. Completed not_found can bill because the lookup ran
• PAYG credits do not expire; optional subscriptions exist for steady volume

That meter is simpler than waiting on partner approval: buy capacity, call public URLs, reconcile from meta.

Related reading

• How to scrape LinkedIn data — DIY vs partner/MDP vs Social Fetch with runnable GETs
• LinkedIn platform hub — routes and examples
• Best LinkedIn data APIs in 2026 — ranked options
• Does LinkedIn have an API? — short glossary
• Social Fetch vs Proxycurl — post-shutdown LinkedIn enrichment
• Social Fetch vs Phyllo — connection / creator OAuth lane
• Social Fetch vs PhantomBuster — automation vs JSON enrichment
• Pricing — packs, charge-on-completed-lookup rules

FAQ

Does LinkedIn have an API?

Yes. Official partner and member-authorized APIs exist. Public-data APIs cover public profiles, companies, posts, jobs, and search without MDP access. Details: glossary.

Can I use LinkedIn's official API for any public /in/ URL?

Generally no. Official access follows approved apps and member permissions. Arbitrary public enrichment is a different product category.

Does Social Fetch replace LinkedIn partner APIs?

No. Public page lookups only. Keep LinkedIn's APIs for posting, login, ads, and approved marketing features.

Do LinkedIn lookups cost credits on Social Fetch?

Yes. Profile GETs are typically 2 credits per URL; search and list routes can cost more. Always check meta.creditsCharged.

Is LinkedIn scraping legal?

You remain responsible for lawful use under LinkedIn's terms and local law. We return publicly visible data and do not give legal advice.