LinkedIn
GET /v1/linkedin/profile

LinkedIn Profile API

LinkedIn person profile with experience[], education[], similarProfiles[] — masked guest text becomes restricted:true.

2 credits per request
TL;DR
LinkedIn person profile with experience[], education[], similarProfiles[] — masked guest text becomes restricted:true. The LinkedIn Profile API (LinkedIn) is a single authenticated GET request to /v1/linkedin/profile that responds with clean JSON and costs 2 credits. Pass cache=true for a free 24h cache hit; default is always fresh. Start with 100 free credits — no credit card.

What is the LinkedIn Profile API?

Public LinkedIn person profile as clean JSON for B2B sales intel. Core identity: name, headline, about, followers, currentCompany — about from the real bio (JSON-LD), never LinkedIn's og:description SEO blurb. connections only when LinkedIn exposes a trustworthy count (logged-out LinkedIn often omits it — a platform limit, not a Captapi gap). B2B sections when upstream exposes them: experience[], education[], similarProfiles[] (people-also-viewed discovery graph), plus projects / publications / articles / activity / recommendations / certifications / languages. Guest-masked asterisk descriptions (******* …) are returned as description:null with restricted:true — not as fake star text. Native HTML bills 1 credit; Apify section enrich is 2.

What you get

  • experience[] + education[] for B2B qualification
  • similarProfiles[] discovery graph
  • restricted:true instead of ******* masking
  • SEO-clean about + honest connections nullability

Try it

Open in Playground

Fill in the parameters below and copy a ready-to-run request, or open the live Playground to run it against your account (no API key paste).

Parameters

Sign in to run live
curl "https://api.captapi.com/v1/linkedin/profile?url=https%3A%2F%2Fwww.linkedin.com%2Fin%2Fpaul-martin-a5aa98" \
  -H "Authorization: Bearer capt_live_..."
# or: -H "x-api-key: capt_live_..."

Edit the parameters and the code updates instantly. Switch languages and hit copy.

Example response

{
  "success": true,
  "data": {
    "platform": "linkedin",
    "type": "person",
    "url": "https://www.linkedin.com/in/paul-martin-a5aa98",
    "username": "paul-martin-a5aa98",
    "name": "Paul Martin",
    "headline": "Culver City, California, United States | Professional Profile",
    "location": "Culver City, California, United States",
    "about": null,
    "followers": 5532,
    "connections": 500,
    "profileImage": "https://media.licdn.com/dms/image/v2/C5603AQERBmOpeQdTJg/profile-displayphoto-shrink_200_200/profile-displayphoto-shrink_200_200/0/1603153614207?e=2147483647&v=beta&t=jmt32YrTWx2FRGXeRg6yYkMBcNR7iGokOvlfuVH5d3U",
    "currentCompany": null
  }
}

Billing metadata is returned in response headers: X-Captapi-Credits (credits charged), X-Captapi-Cache (hit or miss), and X-Captapi-Source. Failed requests (4xx/5xx) are never charged. See the full list of error codes in the error reference.

Response structure

A successful call returns success, cached, creditsUsed, and a data object with the following fields:

Top-level fields

  • platformPlatform identifier for this response (matches the endpoint's platform).
  • typeContent type of the item.
  • urlCanonical URL of the item.
  • usernameAccount username / handle.
  • nameName of the item or account. On profile endpoints: deprecated alias of displayName (one release).
  • headlineProfile headline.
  • locationLocation shown on the profile or item.
  • aboutAbout.
  • followersFollower count.
  • connectionsNumber of connections.
  • profileImageProfile image URL. Deprecated alias of avatar on Instagram/Twitter/Threads/TikTok profile endpoints (one release).
  • currentCompanyCurrent company inferred from LinkedIn worksFor / headline — not SEO meta.

Parameters

NameTypeRequiredDescription
urlstringYesLinkedIn profile URL, e.g. https://www.linkedin.com/in/paul-martin-a5aa98. The URL platform must match this endpoint's platform. Do not pass cross-platform URLs, e.g. YouTube to TikTok, Instagram to Facebook, LinkedIn to X/Twitter, or Pinterest to Rumble.
cachebooleanNoSet true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh. Envelope includes cached + cachedAt on hits.

Authentication: send your key as Authorization: Bearer capt_live_.... A typical call costs 2 credits. Pass cache=true for a free 24h cache hit; default is always fresh.

Using an AI agent? This endpoint is the MCP tool linkedin_profile via @captapi/mcp. Set it up →

How it works

  1. 1. Sign up — get 100 free credits, no card required.
  2. 2. Create a key from your dashboard.
  3. 3. Send one request to /v1/linkedin/profile and parse the JSON response.

Use cases

Profile Enrichment

Add live stats, bio, and account flags to a contact you already have.

Creator Verification

Confirm a known handle, audience size, and business/verified status before outreach.

Competitive Analysis

Track follower growth and posting cadence for accounts you already follow.

Partnership Qualification

Vet known partnership and sponsorship targets with fresh profile data.

Frequently asked questions

What does the LinkedIn Profile API do?+

The LinkedIn Profile API lets you fetch profile or page details and audience stats from a public LinkedIn profile or page using one GET request to /v1/linkedin/profile. It returns clean JSON — no OAuth or infrastructure setup required.

How many credits does the LinkedIn Profile API cost?+

Each successful call costs 2 credits. Pass cache=true to serve from the 24h cache (0 credits on hit); default is always fresh. Hits include cached + cachedAt. Selected profile endpoints also accept cacheMaxAge=1d|3d|7d|14d|30d. Failed or empty results are never charged.

Do I need a LinkedIn API key or OAuth?+

No. A single Captapi key works across every platform Captapi supports — YouTube, TikTok, Instagram, Facebook, Twitter/X, Reddit, Threads, Bluesky, Pinterest, LinkedIn, Rumble, Spotify, Kwai, and more. We handle proxies, rate limits, retries, and authentication for you.

Is the LinkedIn Profile API suitable for production use?+

Yes. It is a stable REST endpoint with predictable JSON and automatic retries. Pass cache=true to serve from the 24h cache (0 credits on hit); default is always fresh. Hits include cached + cachedAt. Selected profile endpoints also accept cacheMaxAge=1d|3d|7d|14d|30d. Use it for analytics, monitoring, and content automation.

More LinkedIn APIs

Ready to use the LinkedIn Profile API?

Sign up, grab your key, and make your first call in 60 seconds.