LinkedIn Data API Featured API

LinkedIn Data API for professional profiles, companies, and jobs

Create B2B enrichment, recruiting, company intelligence, and content research workflows with LinkedIn API methods for profiles, companies, jobs, posts, and search.

B2B enrichment Company intelligence Jobs and profile research

ScrapeStorm is not affiliated with LinkedIn. Use the API only for compliant and permitted data processing.

Use cases

What you can build

LinkedIn demand is practical: teams want professional enrichment, company context, recruiting research, and market monitoring without stitching multiple collectors together.

01

B2B enrichment

Resolve public profile or company details for lead research, CRM hygiene, and account intelligence.

02

Recruiting research

Support talent workflows with profile, job, and company data surfaces.

03

Content and interaction analysis

Collect post and interaction signals for professional market monitoring.

04

Account intelligence

Combine company, profile, and job surfaces to enrich account records and sales research.

05

Labor market signals

Use jobs and company API methods to monitor hiring activity, role demand, and competitive motion.

Entity directory

All supported entities

Browse every supported LinkedIn entity below, understand what each surface is for, and open the exact docs that matches your workflow.

LinkedIn profile data

4 API methods

Profile API methods resolve public identity, account context, and the base layer for creator, brand, or people-oriented products.

What you get. Use this entity to fetch account details, contacts, summary context, and the identifiers you need before moving into content or social API methods.

API methods inside this entity 4 API methods

Open the API method that matches the lookup, feed, summary, or discovery job you need.

LinkedIn company data

4 API methods

Company API methods are built for public business context, brand lookup, and profile enrichment around organizations.

What you get. Use this entity for account resolution, company-level details, and the first layer of context before opening reviews, posts, or people-oriented API methods.

API methods inside this entity 4 API methods

Open the API method that matches the lookup, feed, summary, or discovery job you need.

LinkedIn jobs data

2 API methods

Job API methods focus on public role listings and employer context for hiring and market research workflows.

What you get. This entity helps you pull listing details and company signals for monitoring, enrichment, and labor-market products.

API methods inside this entity 2 API methods

Open the API method that matches the lookup, feed, summary, or discovery job you need.

Launch path

How teams move from evaluation to launch

LinkedIn workflows usually begin with identity or company context, then add jobs, posts, interactions, and search as the product matures.

  1. 01

    Resolve professional context

    Start with profile or company API methods depending on whether your product is people-first or account-first.

  2. 02

    Add hiring and content surfaces

    Use jobs, posts, and interaction API methods when recruiting, market intelligence, or content analysis needs richer context.

  3. 03

    Search the professional graph

    Layer search API methods for discovery workflows that need people, companies, or opportunities by query.

  4. 04

    Document the data contract

    Link every integration path to API method docs so sales, ops, and engineering share the same field expectations.

Start here

First request

Start with a single API method and inspect the docs for exact identifiers, query parameters, and response fields.

API method Profile: Info by username
Request cost 2 credits

Required parameters

usernamestr
GET /api/v2/linkedin.com/profile/info-by-username
curl --request GET \
  --url "https://www.scrapestorm.net/api/v2/linkedin.com/profile/info-by-username" \
  --header "X-API-Key: 00000000-0000-4000-8000-000000000000" \
  --get --data-urlencode 'username=value'
Auth header X-API-Key
Required parameters username
Billing event 2 credits per successful response
Launch details

Pricing, monitoring, and launch details

LinkedIn API method pricing is visible at method level and billed only for successful responses.

ScrapeStorm is not affiliated with LinkedIn. Use the API only for compliant and permitted data processing.

API methods12
Entities4
Credits2 credits

Per-success credit pricing

API method prices are visible before integration and credits are tied to successful API responses.

API reference and implementation docs

Each platform page links to the API reference and implementation docs for exact request and response details.

Responsible data use

ScrapeStorm is independent from the listed platforms; your team remains responsible for permitted data processing.

Details

Questions before launch

These answers cover coverage, pricing, response formats, and launch details before you commit engineering time.

Coverage 4 entities
Credits 2 credits
Health status Check API status
Can LinkedIn API methods handle both people and company workflows?

Yes. The catalog includes profile, company, jobs, posts, interactions, and search groups where supported.

Do I need separate SDKs for V1 and V2?

No. Both versions are exposed through the same ScrapeStorm HTTP pattern and API key header.

Can LinkedIn API methods support B2B enrichment?

Yes. Profile, company, jobs, posts, and search surfaces are organized for enrichment, recruiting, and market intelligence workflows.

Which API method should a CRM product start with?

Start with company or profile API methods, then add search, posts, or jobs depending on the account intelligence model.

Does ScrapeStorm claim official LinkedIn partnership?

No. ScrapeStorm is independent, and customers are responsible for permitted and compliant data processing.