B2B enrichment
Resolve public profile or company details for lead research, CRM hygiene, and account intelligence.
Create B2B enrichment, recruiting, company intelligence, and content research workflows with LinkedIn API methods for profiles, companies, jobs, posts, and search.
ScrapeStorm is not affiliated with LinkedIn. Use the API only for compliant and permitted data processing.
LinkedIn demand is practical: teams want professional enrichment, company context, recruiting research, and market monitoring without stitching multiple collectors together.
Resolve public profile or company details for lead research, CRM hygiene, and account intelligence.
Support talent workflows with profile, job, and company data surfaces.
Collect post and interaction signals for professional market monitoring.
Combine company, profile, and job surfaces to enrich account records and sales research.
Use jobs and company API methods to monitor hiring activity, role demand, and competitive motion.
Browse every supported LinkedIn entity below, understand what each surface is for, and open the exact docs that matches your workflow.
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.
Open the API method that matches the lookup, feed, summary, or discovery job you need.
Open these docs for a fast public snapshot of profile data before expanding into deeper monitoring or enrichment flows.
Choose this API method when your product needs a compact performance view around profile without opening a larger content collection.
Open these docs when you need the actual profile content surface for monitoring, archive jobs, or reporting workflows.
Choose this API method when your product needs a compact performance view around profile without opening a larger content collection.
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.
Open the API method that matches the lookup, feed, summary, or discovery job you need.
Open these docs for a fast public snapshot of company data before expanding into deeper monitoring or enrichment flows.
Choose this API method when your product needs a compact performance view around company without opening a larger content collection.
Open these docs when you need the actual company content surface for monitoring, archive jobs, or reporting workflows.
Choose this API method when your product needs a compact performance view around company without opening a larger content collection.
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.
Open the API method that matches the lookup, feed, summary, or discovery job you need.
Use this API method for discovery work around jobs when you need to find relevant public accounts, topics, or content quickly.
Start here when you need richer public context behind jobs: Details by job ID and want the most complete identity view first.
Search API methods expose public discovery surfaces, queries, and intent signals across the platform.
What you get. This entity is a natural entry point for research, prospecting, alerting, and products that need to find people, content, or topics fast.
Open the API method that matches the lookup, feed, summary, or discovery job you need.
Use this API method for discovery work around search when you need to find relevant public accounts, topics, or content quickly.
Use this API method for discovery work around search when you need to find relevant public accounts, topics, or content quickly.
LinkedIn workflows usually begin with identity or company context, then add jobs, posts, interactions, and search as the product matures.
Start with profile or company API methods depending on whether your product is people-first or account-first.
Use jobs, posts, and interaction API methods when recruiting, market intelligence, or content analysis needs richer context.
Layer search API methods for discovery workflows that need people, companies, or opportunities by query.
Link every integration path to API method docs so sales, ops, and engineering share the same field expectations.
Start with a single API method and inspect the docs for exact identifiers, query parameters, and response fields.
usernamestrcurl --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'
X-API-Key
username
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 method prices are visible before integration and credits are tied to successful API responses.
Each platform page links to the API reference and implementation docs for exact request and response details.
ScrapeStorm is independent from the listed platforms; your team remains responsible for permitted data processing.
These answers cover coverage, pricing, response formats, and launch details before you commit engineering time.
Yes. The catalog includes profile, company, jobs, posts, interactions, and search groups where supported.
No. Both versions are exposed through the same ScrapeStorm HTTP pattern and API key header.
Yes. Profile, company, jobs, posts, and search surfaces are organized for enrichment, recruiting, and market intelligence workflows.
Start with company or profile API methods, then add search, posts, or jobs depending on the account intelligence model.
No. ScrapeStorm is independent, and customers are responsible for permitted and compliant data processing.