LinkedIn API

LinkedIn Profile thin API

Lightweight profile: name, avatar, location, followers, public id, current company, and a basic experience/education list (company + dates; job titles, the current-role flag and the connections label only where the source and the profile show them; no descriptions or skills; past companies may be redacted). For full experience detail, skills, certifications, and verified flags use linkedin.profile.

$0.80/1k req, pay per request, no subscription.

What the API returnedexperience[0]
{
"company":ย "Northwind Robotics",
"companyUrl":ย "https://www.linkedin.com/company/northwind-robotics",
"startDate":ย "Mar 2022",
"endDate":ย "Present",
"current":ย boolean | null,
"position":ย string | null
}
Uptime
99.98%
30d ยท 277,821 calls
Requests
277,823
30d ยท weekly, last 12 wks
Response
9.9s
median ยท 30d

Pricing and providers

LinkedIn Profile thin API pricing: one API, 3 interchangeable providers

The cheapest provider serves first. If it fails, the next one takes over in the same call.

A provider marked Not serving stopped answering reliably and was taken out of the rotation, so your calls go to the others. It is put back on its own once it answers reliably again.

You pay
$8.00
$0.80/1k req, only for what you use. No monthly plan.
Your first 125 requests are free with the $0.10 starting balance.

Try it

Get LinkedIn profile thin in one request

requireFieldsarray
Optional; omit it and routing is unchanged, with the cheapest source serving. Name the output fields this request must be able to return, for example `headline` or `recentPosts`, and it is served only by a source that returns every one of them. Fields you do not name are still returned whenever the serving source has them. This can raise your price: when the cheapest source cannot return a named field, a dearer source serves, and you are quoted and charged its price. A named field can still be absent on a profile that genuinely lacks it. Naming a combination that no single source returns together is refused as invalid input, with no charge.
Open in
Get a free key
Sample response
Free runs return only the first 3 results. Fund a key to get the full response.

This sample shows 28 of 37 fields. See every field

{
  "found": true,
  "data": {
    "name": "Elena Vasquez",
    "location": "Austin, Texas, United States",
    "followers": 8420,
    "about": "Engineering leader focused on developer platforms and infrastructure. Previously built payments infra at scale; now leading the platform team at Northwind Robotics.",
    "avatarUrl": "https://media.licdn.com/dms/image/D4E03AQHElenaVprofile/profile-displayphoto-shrink_800_800/0/1701000000000?e=1735689600",
    "headline": "VP of Engineering at Northwind Robotics",
    "experience": [
      {
        "company": "Northwind Robotics",
        "companyUrl": "https://www.linkedin.com/company/northwind-robotics",
        "startDate": "Mar 2022",
        "endDate": "Present"
      },
      {
        "company": "Cascade Payments",
        "companyUrl": "https://www.linkedin.com/company/cascade-payments",
        "startDate": "Jul 2017",
        "endDate": "Feb 2022"
      },
      {
        "company": "Briar Systems",
        "companyUrl": "https://www.linkedin.com/company/briar-systems",
        "startDate": "Jun 2014",
        "endDate": "Jun 2017"
      }
    ],
    "education": [
      {
        "school": "University of Texas at Austin",
        "schoolUrl": "https://www.linkedin.com/school/university-of-texas-at-austin",
        "startDate": "2010",
        "endDate": "2014"
      }
    ],
    "recentPosts": [
      {
        "id": "7281234567890123456",
        "url": "https://www.linkedin.com/feed/update/urn:li:activity:7281234567890123456",
        "text": "Shipped our new deploy pipeline this week, cut rollout time from 40 minutes to 6.",
        "activityType": "post",
        "createdUtc": 1758585600
      }
    ],
    "articles": [
      {
        "headline": "Why we rebuilt our internal platform team around golden paths",
        "url": "https://www.linkedin.com/pulse/why-we-rebuilt-elena-vasquez",
        "createdUtc": 1751328000
      }
    ]
  }
}

Full parameter and response reference - every field, type, and example for this endpoint.

Reference

One request, one response shape.

Every field you send and every field you get back, each with a real example.

Last verified 2026-10-31 ยท uptime and latency measured over 30d

Request body

JSON, posted to this endpoint.

  • urlstring

    https://www.linkedin.com/in/elena-vasquez-eng

    Full LinkedIn person profile URL, carrying the profile id after /in/, for example https://www.linkedin.com/in/williamhgates. Any other LinkedIn URL names no person, so it is rejected instead of charged: send a company page to linkedin.company_thin or linkedin.company, and a post to linkedin.post.

  • requireFieldsarray

    ["recentPosts"]

    Optional; omit it and routing is unchanged, with the cheapest source serving. Name the output fields this request must be able to return, for example `headline` or `recentPosts`, and it is served only by a source that returns every one of them. Fields you do not name are still returned whenever the serving source has them. This can raise your price: when the cheapest source cannot return a named field, a dearer source serves, and you are quoted and charged its price. A named field can still be absent on a profile that genuinely lacks it. Naming a combination that no single source returns together is refused as invalid input, with no charge.

You send. A small JSON body. The values shown are examples to replace with your own.

Response

JSON, one example value per field.

datadata

The profile result, or null when not found.

  • aboutstring

    Engineering leader focused on developer platforms and infrastructure. Previously built payments infra at scale; now leading the platform team at Northwind Robotics.

    About/summary text of the profile.

  • avatarUrlstring

    https://media.licdn.com/dms/image/D4E03AQHElenaVprofile/profile-displayphoto-shrink_800_800/0/1701000000000?e=1735689600

    URL of the profile avatar image.

  • connectionsstringcan require

    Connections count as LinkedIn's public label shows it, capped at "500+" (for example "8" or "500+"). Null when the serving source does not publish it.

  • followersinteger

    8420

    Number of followers.

  • headlinestringcan require

    VP of Engineering at Northwind Robotics

    Profile headline, or null when the serving source does not publish it.

  • locationstring

    Austin, Texas, United States

    Location of the profile owner.

  • namestring

    Elena Vasquez

    Full name of the profile owner.

  • publicIdentifierstringcan require

    LinkedIn public identifier (the /in/ handle), or null when the serving source does not publish it.

each articledata.articles[]

The profile's published articles, or null when the serving source does not publish them.

  • createdUtcnumbercan require

    1751328000

    UTC epoch timestamp in seconds (Unix time). Multiply by 1000 for a JS Date in milliseconds.

  • headlinestringcan require

    Why we rebuilt our internal platform team around golden paths

    Headline of the article.

  • urlstringcan require

    https://www.linkedin.com/pulse/why-we-rebuilt-elena-vasquez

    Canonical URL of the article.

each currentPositiondata.currentPosition[]

The member's current role as the serving source reports it: one entry, or an empty list when the profile shows no current employer. Null when the serving source does not publish it.

  • companyLinkedinUrlstringcan require

    Company LinkedIn URL, or null when the serving source does not publish it.

  • companyNamestringcan require

    Company name.

  • positionstringcan require

    Job title, or null when the serving source does not publish it or the profile hides it.

each educationdata.education[]

Education entries.

  • endDatestring

    2014

    End date of study.

  • schoolstring

    University of Texas at Austin

    Name of the school.

  • schoolUrlstring

    https://www.linkedin.com/school/university-of-texas-at-austin

    URL of the school page.

  • startDatestring

    2010

    Start date of study.

each experiencedata.experience[]

Work experience entries: company and dates, plus the job title and whether the role is current when the serving source publishes them. Populated whenever the provider has data for the entity.

  • companystring

    Northwind Robotics

    Name of the company.

  • companyUrlstring

    https://www.linkedin.com/company/northwind-robotics

    URL of the company page.

  • currentbooleancan require

    Whether this is a current role, or null when the serving source does not say.

  • endDatestring

    Present

    End date of the role.

  • positionstringcan require

    Job title, or null when the serving source does not publish it or the profile hides it.

  • startDatestring

    Mar 2022

    Start date of the role.

each recentPostdata.recentPosts[]

The profile's recent posts, or null when the serving source does not publish them.

  • activityTypestringcan require

    post

    Type of activity for the post.

  • createdUtcnumbercan require

    1758585600

    UTC epoch timestamp in seconds (Unix time). Multiply by 1000 for a JS Date in milliseconds.

  • idstringcan require

    7281234567890123456

    Unique identifier of the post.

  • textstringcan require

    Shipped our new deploy pipeline this week, cut rollout time from 40 minutes to 6.

    Text content of the post.

  • urlstringcan require

    https://www.linkedin.com/feed/update/urn:li:activity:7281234567890123456

    Canonical URL of the post.

top level
  • foundboolean

    true

    Whether the profile was found.

  • reason"not_found" | "unavailable"

    Present only when `found` is false, and says why there is no result. `not_found`: the source states the target does not exist, or returned nothing for it. `unavailable`: the platform did not show this to the source: it may not exist, or it may be visible only to signed-in users. A `found: false` answer is a successful call, not an error, and `costUsd` is what it actually cost.

You get back. Named, typed fields in the same shape whichever source answers.

FAQ

About the LinkedIn Profile thin API

The AnyAPI LinkedIn Profile thin API returns LinkedIn profile thin data as normalized JSON from one POST call to /v1/run/linkedin.profile_thin. Lightweight profile: name, avatar, location, followers, public id, current company, and a basic experience/education list (company + dates; job titles, the current-role flag and the connections label only where the source and the profile show them; no descriptions or skills; past companies may be redacted). For full experience detail, skills, certifications, and verified flags use linkedin.profile. AnyAPI routes each request across 3 sources and falls back automatically when one fails. It costs from $0.80 per 1,000 requests, in US dollars with no subscription and no monthly minimum. Over the last 30 days, 100.0% of LinkedIn profile thin calls through AnyAPI succeeded, with a median response time of 9.9 seconds across 277,821 measured calls.

It costs from $0.80 per 1,000 requests, in US dollars with no subscription and no monthly minimum. You fund one USD wallet and each call draws it down. Some failed wallet-funded requests incur processing charges that we pass through at cost, with no markup; the error response shows the amount charged.

Lightweight profile: name, avatar, location, followers, public id, current company, and a basic experience/education list (company + dates; job titles, the current-role flag and the connections label only where the source and the profile show them; no descriptions or skills; past companies may be redacted). For full experience detail, skills, certifications, and verified flags use linkedin.profile. The response is normalized JSON with the same envelope every AnyAPI endpoint returns, so parsing a second endpoint is a change of URL and nothing else.

Over the last 30 days, 100.0% of LinkedIn profile thin calls through AnyAPI succeeded, with a median response time of 9.9 seconds across 277,821 measured calls. These are AnyAPI's own measurements of traffic through the gateway, recomputed continuously, not a published service-level target.

Yes. A new AnyAPI account starts with $0.10 of free balance and no card required, which covers 125 LinkedIn Profile thin calls at $0.0008 each.

AnyAPI asks the next of its 3 sources in the same request, cheapest first, so one source going down does not fail your call.

Send a POST request to https://api.getanyapi.com/v1/run/linkedin.profile_thin with your AnyAPI key in an "Authorization: Bearer" header and the input as a JSON body. The same key and the same wallet work on every AnyAPI endpoint.

No. You add US dollars to one prepaid AnyAPI balance and each request draws it down. There is no monthly plan and no minimum, and the same balance pays for every AnyAPI endpoint.

Yes. Install @getanyapi/sdk from npm for TypeScript or getanyapi from pip for Python. Both call every AnyAPI endpoint with the same key, and any HTTP client works too.

Yes. An agent can connect to the AnyAPI MCP server at https://api.getanyapi.com/mcp, or create its own free-trial key with one unauthenticated POST to https://api.getanyapi.com/agent/signup and call this endpoint over HTTP.