LinkedIn Scraper API
Turn public LinkedIn pages into structured JSON over one REST API. Profiles, companies, jobs, job search, posts, and public contact data, each from a dedicated endpoint, no LinkedIn login and no cookies to manage.
Free 1,000 requests. Median response 2.6s. Residential-first proxies. No credit card, no LinkedIn login.
curl "https://api.linkedinscraperapi.com/api/v1/linkedin/search?keywords=software+engineer&api_key=$API_KEY"Scrape LinkedIn without getting blocked
Anti-bot bypass
Proxy rotation
JS rendering
Structured JSON
Pay for success
One REST call
Choose from multiple LinkedIn Scraper API endpoints
Profile
Job
Email & Lead
Post
Company
Search Results
Sales Navigator
Followers & Connections
Comment
What you can build
Sales and lead enrichment
Recruiting and talent sourcing
Firmographic and market data
Hiring and compensation intelligence
Content and creator analytics
People and company databases
Simple, usage-based pricing
- All endpoints included
- Structured JSON output
- Anti-bot + rotating proxies
- 10 concurrent requests
- Community support
- Everything in Free
- Higher concurrency
- Email support
- Everything in Vibe
- Priority request routing
- Priority support
- Everything in Pro
- 500+ concurrent requests
- SLA + dedicated support
Pay-as-you-go top-ups run $0.90 per 1,000 successful requests. Median response 2.6s. You only pay for requests that succeed.
Drops into your stack
No-code
LLM and RAG
SDKs and REST
FAQ
A LinkedIn Scraper API is a REST service that reads public LinkedIn pages and returns them as structured JSON. Ours covers the public surfaces LinkedIn renders logged-out: profiles, companies, jobs, job search, posts, and public contact data. You send one GET request with an api_key and get parsed JSON back, with no LinkedIn login, no cookies, and no Partner Program approval.
Scraping publicly available data is generally treated as permissible, and US courts read the CFAA narrowly for public pages in cases like hiQ v. LinkedIn, but that is not blanket permission. You remain responsible for copyright, LinkedIn's own terms, and personal-data rules such as the GDPR, and the regulated part is usually what you do with the data, especially outreach. Treat data as public business information, have a lawful basis, and honor opt-outs. This is general information, not legal advice.
No. The official LinkedIn APIs are gated behind the Partner Program and, for member data, the member's own OAuth consent, so they cannot return an arbitrary public profile. Our API needs neither a partner approval nor a LinkedIn login. We read the public logged-out pages through managed residential proxies and authenticate with a single api_key.
No, and we are explicit about it. A member's email sits behind the logged-in Contact-info modal and is essentially never public, so our email endpoint returns the external website (which companies do expose) and marks email null with a note. Connection-only fields need a logged-in account, which we do not use. We report what is public and flag what is walled rather than implying access to private data.
Six public surfaces, each with a dedicated endpoint: profiles (/in/ pages), companies (/company/ pages), a single job posting, job search results, posts, and public contact data for a profile or company. Every endpoint accepts a url input, returns the same structured JSON style, and shares one api_key and the 1,000-request free tier.
The free plan covers 1,000 requests with no card. Pro works out to about $0.60 per 1,000 requests and pay-as-you-go is $0.90 per 1,000, and you are billed only for successful requests. Retries across proxy tiers behind a successful call are not charged separately.