Proxycurl shut down in July 2025. This is a developer's guide to moving your LinkedIn data pipeline to LinkFinder AI — with a full endpoint map, before/after code, and an architecture that doesn't depend on LinkedIn accounts.
Last updated: May 30, 2026
For years, Proxycurl was the LinkedIn data API that developers reached for first. It was clean, well-documented, fairly priced, and reliable — a genuinely good product built for engineers. Credit where it's due: it set the bar for what a LinkedIn enrichment API should feel like.
That ended in 2025. In January 2025, LinkedIn (owned by Microsoft) filed a federal lawsuit alleging Proxycurl operated large numbers of fake accounts to collect member data. Facing the cost of fighting a multi-billion-dollar opponent, Proxycurl settled and shut down in July 2025. The API endpoints went dark, the documentation was pulled, and under the settlement collected LinkedIn data had to be deleted.
One thing worth being deliberate about while you migrate: the reason Proxycurl was vulnerable was its reliance on LinkedIn accounts. LinkFinder AI's B2B Data Lookup retrieves business-contact and company data without using your own LinkedIn account, which removes both the ban risk on your side and the specific exposure that ended Proxycurl. No provider can promise it will never face litigation, but the underlying approach is different.
An honest side-by-side. Proxycurl genuinely did some things well — this isn't a clean sweep.
type fieldProxycurl split work across many endpoints. LinkFinder AI uses a single endpoint — POST https://api.linkfinderai.com — where the type field selects what you want. Here's how the old endpoints map across.
| Proxycurl endpoint | What it did | LinkFinder AI equivalent |
|---|---|---|
| Person Profile | Profile data from a LinkedIn URL | B2B Data Lookup |
| Person Search | Find people by filters (title, geo, company) | Not supported — LinkFinder AI enriches contacts you already have |
| Person Lookup | Resolve a person from name + company | Full Name → LinkedIn URL · lead_full_name_to_linkedin_url |
| Role Lookup | Find the decision-maker at a company | Company Employees · company_domain_to_employees |
| Company Profile | Company data from a company URL | Company Enrichment |
| Company Lookup | Resolve a company from its name | Company Enrichment · company_name_to_website |
| Employee Count | Company headcount | Company Enrichment |
| Contact API (email / phone) | Work email & phone | B2B Data Lookup |
type values shown in code below that aren't in your published docs (e.g. profile / company lookups) are placeholders — check the exact strings in your dashboard under API Documentation. The documented types are company_name_to_website.
status field ("success" or "error") and a result field. Update your parsing to read result, and note that a successful call can still return result: null if no data was found (it still costs 1 credit).
Sign up for a free trial — your key is in the dashboard under Settings → API Key. You start with free credits, enough to test your whole migration before paying.
Point requests at https://api.linkfinderai.com and replace your Proxycurl key with Authorization: Bearer YOUR_API_KEY. All requests are POST with a JSON body.
Use the mapping table above. Person Profile and Email Lookup map directly; company calls become Company Enrichment. Proxycurl's filter-based Person Search has no equivalent — LinkFinder AI enriches contacts you bring rather than searching for new ones.
Read status and result instead of the raw object. Handle 429 with exponential backoff (1s → 2s → 4s) and treat result: null as "not found", not an error.
The same jobs, a simpler API, and an approach that removed the single biggest risk Proxycurl carried.
B2B Data Lookup pulls business-contact and company data without using your LinkedIn account — no ban risk for you, and not the architecture that ended Proxycurl.
A single POST endpoint with a type field replaces a dozen Proxycurl routes. Fewer integration points, less to maintain. See the API docs.
Describe your ideal customer in plain English and get up to 100 matching profiles per call — a step up from Proxycurl's filter-based Person Search.
type values, and reading the new status/result response shape. Most teams finish in an afternoon.POST endpoint with a type field. Every job Proxycurl did — profile lookup, person search, company data, employee count — has an equivalent, so it's a remapping exercise, not a rewrite. See the API documentation.https://api.linkfinderai.com, change the auth header to your LinkFinder key, map endpoints to request types, and update response parsing.Get a free API key with 100 credits, point your pipeline at LinkFinder AI, and have your migration tested before lunch.
Free credits • No LinkedIn account required • REST + JSON