§ The LinkedIn hub
LinkedIn

LinkedIn
scraper.

No proxy needed. 6 pre-built endpoints, parsed JSON in seconds.

6 endpoints·From $0.005 per call·Median under 2s
§ One call

Send a URL.
Get back JSON.

The profile scraper takes one input: url. The response carries every public field LinkedIn exposes.

Request
cURL
curl https://api.hproxy.com/v1/scrape/linkedin/profile/collect/by/url \
  -H "Authorization: Bearer $HPROXY_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://www.linkedin.com/in/parrsam/"}'
POST // 1 call · $0.0050 · <2s
Response200 OK
{
  "success": true,
  "name": "Sam Parr",
  "image": "https://media.licdn.com/dms/image/v2/….jpg",
  "location": "Westport, Connecticut, United States",
  "followers": 64803,
  "about": "I founded The Hustle, a business news media company with $12 when I was around 25 years…",
  "experience": [
    {
      "@type": "Organization",
      "name": "Hampton",
      "url": "https://www.linkedin.com/company/myhampton",
      "location": "Austin, Texas Metropolitan Area",
      "member": {
        "@type": "OrganizationRole",
        "description": "founder of Hampton, growth-marketing collective…"
      }
    }
  ],
  "education": [
    {
      "@type": "EducationalOrganization",
      "name": "Belmont University",
      "url": "https://www.linkedin.com/school/belmont-university/",
      "member": {
        "@type": "OrganizationRole",
        "startDate": 2008,
        "endDate": 2012
      }
    }
  ],
  "similarProfiles": [
    {
      "link": "https://ca.linkedin.com/in/stevemcody",
      "name": "Steve Cody",
      "image": "https://media.licdn.com/dms/image/v2/….jpg"
    }
  ]
}
What comes backparsed fields
LinkedIn Profile
linkedin_profile
namestring
imageurl
locationstring
followersnumber
aboutstring
experiencearray
educationarray
One real call · one structured record
§ Coverage

What you can
actually pull.

§ 01

Profiles

Bio, follower and following counts, post totals, verified flag, links, and the profile image — every public field the platform exposes about an account.

§ 02

Companies

Company pages with description, employee count, industry, headquarters, founding year, funding history, and the logo.

§ 03

Posts

Full post objects: caption text, like and comment counts, view counts, media URLs, and timestamps — pulled by handle or by direct URL.

§ 04

Ads

Ad-library entries with creative references, advertiser, run dates, and impressions where the platform publishes them.

§ Every endpoint

The full list.
Prices included.

Every line is a live endpoint. Click through for the input schema, response shape, and the curl recipe.

§ What people build

One LinkedIn scraper.
Many shapes of work.

§ 01

Audience & creator discovery

Build lead and creator-discovery pipelines from LinkedIn public profiles. Filter by follower count, engagement, and region. The JSON is flat enough to drop into a Postgres column without normalisation.

§ 02

Brand & trend monitoring

Track every public post mentioning a brand or keyword across LinkedIn. Pipe captions into sentiment models and chart engagement over time without writing a single parser.

§ 03

Ad-library mirroring

Build your own LinkedIn ad archive. Cross-reference advertisers, creatives, and run dates to map a competitor's entire paid strategy.

§ 04

AI training data

Feed clean, structured LinkedIn JSON straight into your model fine-tuning pipeline. Same schema every call — no scraping infrastructure to maintain.

§ Questions

The honest
answers.

The questions that come up before the first call. If yours isn’t here, the founder reads support email himself — just write in.

Do I need proxies to use the LinkedIn scraper?

No. Every endpoint runs on our residential pool — fifty million IPs sourced through opt-in partner SDKs. You send an HTTP request with your API key; rotation, retries, and anti-bot handling are ours to worry about.

How does HProxy get past LinkedIn’s rate limits and bot detection?

Each call is routed through a residential session that matches typical organic traffic patterns. We don’t advertise specifics; what matters is the result — a 99%+ success rate on public-data endpoints in real customer traffic.

What does the JSON response look like?

Every endpoint returns a flat top-level wrapper (platform, scraper, data, creditsUsed, elapsedMs, requestId) with the parsed LinkedIn entity inside data. See the live example near the top of this page for the exact shape.

Is scraping public LinkedIn data legal?

Public data scraping (no login, no private content, no PII beyond what linkedin.com itself publishes) sits within the boundaries set by hiQ Labs v. LinkedIn and similar US/EU precedents. We don’t serve endpoints that touch authenticated content. You’re responsible for your own use of the data under your local data-protection law (GDPR, CCPA, etc.).

What does each call cost?

From $0.005 per call on the standard endpoints. Endpoints that do heavier upstream work — AI transcripts, posts with media archived to R2 — cost more. The exact per-call price shows on each endpoint row below. One call = one charge, never multiplied by record count.

Can I test before signing up?

Yes — the wallet starts with a $2 deposit that’s refundable for 24 hours. That’s plenty of calls to verify the response shape matches what you’re building across all 6 LinkedIn endpoints.

How fast are the responses?

Median response time across the LinkedIn endpoints is under 2 seconds. Heavier endpoints (deep comment threads, cursor-paginated lists) can run 4-8 seconds depending on the page depth requested.

§ Try it

Two dollars,
first run.

Sign in with Google, drop $2 in the wallet, fire your first LinkedIn call against linkedin.com. If it doesn’t do what you need, the balance is refundable for 24 hours.