What the API does and who it is for
Fresh LinkedIn Scraper API, developed by SaleLeads.ai, is a hosted scraping layer that sits between your application and LinkedIn's public-facing data. Instead of maintaining your own scraper infrastructure — dealing with IP bans, rate limiting, and LinkedIn's evolving markup — you send a GET request and receive structured data back in roughly 887 ms on average.
The primary audiences are:
- Sales and lead generation teams building prospect lists from LinkedIn profiles and company pages.
- Recruiters and HR tools that need to pull candidate work history, education, certifications, and contact signals.
- Market researchers tracking competitor hiring patterns, company growth signals, or content engagement.
- Product teams embedding LinkedIn intelligence (job counts, people insights, affiliated pages) directly into their platforms.
With 4,676 marketplace subscribers and a popularity score of 9.9 out of 10, it has clear real-world adoption. A 98% success rate suggests the underlying infrastructure handles LinkedIn's anti-scraping measures reliably enough for production use.
Endpoint walkthrough
The API exposes 43 endpoints across six logical groups.
User profile data
The core profile group gives you everything visible on a LinkedIn member's profile page. /api/v1/user/profile retrieves the headline, summary, and identity fields. Dedicated endpoints then peel off specific sections: work experience (/experience), education (/educations), skills, certifications, honors, volunteer activity, publications, and recommendations. Two endpoints cover engagement behavior — posts the user has published and comments they have left — which is useful for qualifying leads by activity level before outreach.
A couple of endpoints stand out. /api/v1/user/contact targets contact information fields that LinkedIn surfaces on profiles. /api/v1/user/save-to-pdf returns a PDF rendition of the profile, which could slot into reporting or CRM attachment workflows without additional formatting work. /api/v1/user/follower-and-connection exposes follower and connection counts, a lightweight signal of a person's LinkedIn reach.
Company data
The company group covers profile details, associated people, posts, current job listings, and a standalone job count endpoint — handy for tracking hiring velocity over time without fetching full job lists. /api/v1/company/affiliated-pages and /api/v1/company/associated-member-insights provide relationship and workforce analytics data that would otherwise require manual LinkedIn navigation.
Jobs
Two endpoints handle job data: a detail endpoint for a specific listing and a search endpoint for querying across listings. These are the building blocks for job board aggregators or internal tools that monitor when target companies open roles.
Posts and engagement
Four endpoints decompose a LinkedIn post into its constituent engagement signals: comments, reactions, reposts, and replies to comments. This granularity makes it possible to analyze content performance or identify engaged audiences around specific posts — useful for social listening or intent-based lead qualification.
Search
The search group (/api/v1/search/posts, /search/people, /search/location, /search/schools, /search/suggestion-industry) enables keyword and filter-driven discovery rather than lookup by a known profile URL. This is what makes the API useful for list-building at scale rather than just profile enrichment.
Groups
/api/v1/group/info retrieves metadata about LinkedIn Groups, which can feed community-mapping or niche audience research workflows.
Pricing breakdown
The API uses a freemium model with four tiers:
| Plan | Monthly cost | Requests included | Rate limit | Overage per request |
|---|---|---|---|---|
| Basic | $0 | 50 | — | — |
| Pro | $49 | 20,000 | 20 / min | $0.0080 |
| Ultra | $199 | 100,000 | 120 / min | $0.0065 |
| Mega | $499 | 500,000 | 300 / min | $0.0050 |
The Basic plan's 50 requests per month is realistically only useful for local prototyping or evaluating response shapes before committing budget. It is not sufficient for any live enrichment pipeline.
Pro at $49/month gives 20,000 requests at 20 requests per minute. At that rate limit, a batch job enriching 1,000 profiles (assuming a few endpoints per profile) would take a meaningful amount of time. This tier suits small teams doing periodic enrichment rather than real-time lookups.
Ultra at $199/month is marked recommended and represents the best per-request economics among the mid-tier options. 100,000 requests covers substantial enrichment volume, and the 120 req/min rate limit makes batch jobs practical. Overage at $0.0065 per request is reasonable if you occasionally spike.
Mega at $499/month is aimed at high-volume platforms — 500,000 requests and 300 req/min suits SaaS products where LinkedIn data is a core feature rather than a supplementary enrichment layer. The $0.0050 overage rate is the lowest available.
For custom volume requirements, SaleLeads.ai offers direct contact via Telegram (@saleleads) or email ([email protected]).
Practical use cases
- CRM enrichment: Pipe a list of LinkedIn profile URLs through
/user/profile,/user/experience, and/user/contactto populate or refresh contact records automatically. - Recruitment sourcing: Use
/search/peopleto find candidates matching a role, then pull full profiles including education and certifications for shortlisting. - Competitive intelligence: Monitor a competitor's
/company/job-countweekly to gauge team growth, and pull/company/poststo track messaging strategy. - Lead scoring: Combine a prospect's recent post activity (
/user/posts) and follower count (/user/follower-and-connection) to weight outreach priority. - Job board aggregation: Use
/job/searchand/job/detailto aggregate listings by industry, location, or company and surface them in a niche job board product.
Limitations and things to check before integrating
A few practical considerations are worth thinking through before committing to an integration:
- Data freshness: The name emphasizes "fresh" data, but the documentation does not specify how frequently the underlying cache refreshes. If your use case requires real-time accuracy (e.g., live profile lookups during a sales call), verify cache behavior with the provider.
- Rate limits on Basic: No rate limit is published for the free tier. Clarify this before using Basic in any automated context, even for testing.
- LinkedIn ToS exposure: LinkedIn's terms of service restrict automated data collection. The API handles the technical scraping, but the legal compliance responsibility generally rests with the end user. Evaluate this against your product's risk tolerance and jurisdiction.
- Endpoint completeness: The listing notes 43 total endpoints but only shows 40. The three unlisted endpoints are not documented here; contact the provider to understand what they cover.
- No SDK mentioned: The API appears to be a straightforward REST interface — any HTTP client works — but no official SDK or code samples are referenced in the available documentation.
Getting started
The API is available through a marketplace (given its subscriber count and structured pricing plans). Signing up for the Basic plan requires no upfront cost, giving you 50 requests to test endpoint responses against real LinkedIn URLs before choosing a paid tier. Focus your free calls on the endpoint types most central to your workflow — for most use cases, that means /user/profile and either /company/profile or /job/search.
For volume above what any listed plan covers, or for questions about data freshness and caching behavior, reach the SaleLeads.ai team at [email protected] or via Telegram at @saleleads.
