What Fresh LinkedIn Profile Data does and who it is for
Fresh LinkedIn Profile Data is a scraping-as-a-service API that fetches LinkedIn data at request time — meaning you get whatever is live on LinkedIn the moment you call the endpoint, not a cached snapshot from weeks ago. The provider is explicit about this: data is scraped directly from the web on demand, which is why the API carries an average latency of about 13.5 seconds per call. That latency is a deliberate tradeoff for freshness, and it matters when you are building tools where stale contact details or outdated job titles would undermine the product.
The API targets developers building:
- Sales and marketing tooling — lead enrichment, prospect research, decision-maker identification
- Recruiting platforms — sourcing candidates, checking open-to-work status, pulling CVs
- Market intelligence products — tracking company headcount, job postings, company insights
- Social listening — scraping post content, reactions, comments, and activity timestamps
With 39 endpoints spanning profiles, companies, jobs, posts, and search, the surface area is wide enough to avoid stitching together multiple separate APIs.
Endpoint walkthrough and credit costs
Every API call consumes credits, but not at a flat rate — the credit cost varies by endpoint. Understanding this before you pick a plan is essential, because the number of requests your plan allows and the number of credits it includes are two different ceilings.
Profile and people data
- GET /enrich-lead — the core profile enrichment endpoint. Costs 1 credit at minimum, with each optional extra field adding 0.5 credits, capped at 3 credits. This is your go-to for structured profile data.
- GET /get-extra-profile-data — fetches supplementary fields such as languages, certifications, publications, patents, and awards that the base enrichment call does not include.
- GET /get-profile-posts and GET /get-profile-recent-activity-time — 2 credits each, useful for tracking how active a contact is.
- GET /get-opentowork-status and GET /get-open-profile-status — 1 credit each, lightweight signals for recruiters.
- GET /get-profile-pdf-cv — 1 credit, returns a downloadable CV representation of the profile.
- GET /get-recommendations-given and GET /get-recommendations-received — 1 credit each.
- GET /get-year-of-experiences — returns total years of experience derived from the profile history.
Company data
- GET /get-company-by-linkedinurl and GET /get-company-by-domain — 1 credit each, the most common company lookup paths.
- GET /get-company-by-id — 1 credit, useful when you already have LinkedIn's internal company ID.
- GET /get-company-insights — the heavyweight company endpoint at 5 credits per call, returning deeper analytical data.
- GET /get-company-jobs-count — 1 credit, a quick signal for hiring velocity.
- GET /get-company-posts — 2 credits.
- POST /search-companies-instantly — searches a cached database of 64 million company records. Costs 1 credit per 10 companies returned (searches returning fewer than 10 still consume 1 credit). This is distinct from the real-time search flow.
Asynchronous search flows
Several heavier searches follow a two-step async pattern: you POST to a search endpoint, receive a request_id, then poll a status endpoint until the search completes, and finally fetch results.
- POST /search-companies (25 credits) → GET /check-search-companies-status → GET /get-search-companies-results
- POST /search-employees and POST /big-search-employee → GET /check-search-status → GET /get-search-results
The 25-credit cost of /search-companies is significant — on the BASIC plan, that is 5% of your monthly credit allocation per call. Plan accordingly if company search is a core use case.
Jobs and posts
- POST /search-jobs — 2 credits; paginate using the
startparameter (0, 25, 50…) to retrieve full result sets. - POST /search-jobs-v2 — 1 credit, simpler payload.
- GET /get-job-details — 1 credit, returns full job description plus company basics.
- POST /search-posts and GET /get-post-comments / GET /get-post-reactions — 2 credits and 1 credit respectively.
Google-powered search endpoints
POST /google-profiles, POST /google-companies, and POST /google-schools use Google as an intermediary to discover LinkedIn URLs matching your criteria — each costs 2 credits and can return up to 100 results per call.
Pricing breakdown
| Plan | Monthly cost | Credits/month | Requests/month | Rate limit | Overage per credit |
|---|---|---|---|---|---|
| BASIC | $10 | 500 | 500 | 20 / min | — |
| PRO | $45 | 4,500 | 6,000 | 20 / min | $0.0120 |
| ULTRA (recommended) | $250 | 32,000 | 40,000 | 50 / min | $0.0080 |
| MEGA | $1,000 | 200,000 | 240,000 | 150 / min | $0.0060 |
A few things to notice. First, credits and requests are counted separately — on PRO, you have 6,000 requests but only 4,500 credits, so multi-credit endpoints will exhaust your credits before your request allowance. Second, unused credits do not roll over. Third, the BASIC plan has no overage pricing, implying hard cutoffs once you hit 500 credits. Fourth, rate limits jump materially between tiers: PRO and BASIC are both capped at 20 requests per minute, while ULTRA doubles that to 50 and MEGA goes to 150.
For a quick sanity check on BASIC: 500 credits at 1 credit per enrichment call gives you 500 profile lookups per month — fine for a prototype or personal tool, inadequate for any production enrichment flow. PRO's 4,500 credits at the same rate support roughly 4,500 enrichments or a mix of cheaper and pricier calls.
Practical use cases
Lead enrichment at scale: Feed a list of LinkedIn profile URLs into /enrich-lead with optional extras to fill out CRM records. At ULTRA, 32,000 credits supports up to 32,000 single-credit enrichments per month, or roughly 10,000 fully loaded 3-credit enrichments.
Recruiting pipelines: Combine /search-employees with /get-opentowork-status and /get-profile-pdf-cv to filter and qualify candidates programmatically without manual LinkedIn browsing.
Company monitoring: Use /get-company-insights (5 credits) and /get-company-jobs-count (1 credit) together to track growth signals for a target account list. On ULTRA, that's up to 5,300 company insight pulls per month.
Content and engagement tracking: The post-related endpoints let you track what companies and individuals are publishing, who is reacting, and when profiles were last active — useful for timing outreach or measuring campaign attribution.
Limitations and considerations before integrating
Latency: The average 13,537 ms response time makes this unsuitable for synchronous user-facing requests. Design your integration around background jobs and queues, not inline API calls during a page load.
Success rate: The 92% average success rate means roughly 1 in 12 calls will fail. Build retry logic and handle error responses gracefully in your pipeline.
No credit rollover: Credits expire at the end of each billing cycle. If your usage is spiky, you may want to over-provision rather than under-provision, and time subscription changes to end of cycle.
Asynchronous endpoints: The multi-step search flows (POST → poll status → fetch results) require your system to handle delayed resolution. Factor this into architectural decisions, especially if you need search results in near-real time.
Credit accounting: Carefully map your workflow to endpoint credit costs before committing to a plan. A workflow that leans on /get-company-insights (5 credits) or /search-companies (25 credits) will exhaust a given credit budget far faster than one built on 1-credit lookups.
Getting started
Fresh LinkedIn Profile Data is available through RapidAPI. Subscription management, including cancellation, is handled through the RapidAPI dashboard. The provider offers a 100% refund if you use up to 10% of your credits and are unsatisfied, which gives you a low-risk window to validate integration before committing to a billing cycle. Start on BASIC to verify your use case works end-to-end, then evaluate whether PRO or ULTRA matches your throughput needs based on actual credit consumption patterns from your test runs.
