Proxycurl alternative
Proxycurl announced it was winding down in 2025 following litigation from LinkedIn. If you are here because your integration stopped working, this page is about getting you running again rather than selling you anything.
Where Proxycurl is the better choice
- It had a genuinely good developer experience, and a lot of engineers liked it.
- Its person-lookup-by-email and contact enrichment had no direct equivalent here.
- It offered a well-documented reverse lookup from work email to profile.
We have not benchmarked their data quality against ours and do not publish comparisons we did not run.
What happened, briefly
LinkedIn brought legal action against Proxycurl's operator, and in 2025 the service announced it was shutting down. Customers were given a wind-down period. If you are reading this because a scheduled job started returning errors, that is the reason.
We are not going to use that as a scare tactic. It is worth saying plainly that legal risk in this category is real and ongoing, that it applies to us as much as to anyone else, and that any provider telling you otherwise is selling confidence they do not have.
Mapping your calls across
The concepts map closely enough that most migrations are an afternoon:
| What you were doing | Here |
|---|---|
| Person profile endpoint | GET /v1/profile with url, publicIdentifier or profileId |
| Company profile endpoint | GET /v1/company with url or universalName |
| Person search | GET /v1/profile-search with title, currentCompany, geoId |
| Company search | GET /v1/company-search |
| Employee listing | GET /v1/profile-search filtered on currentCompany |
| Job search | GET /v1/job-search |
Authentication changes from a bearer token to an X-API-Key header. The response envelope differs — single records come back under element, lists under elements with a pagination object — so your parsing layer needs a pass, but the field names are broadly recognisable.
What has no equivalent here
Be aware of this before you start porting. Proxycurl offered contact enrichment including work email lookup and reverse lookup from an email address to a profile. We do not, at any price. Email is not part of a public profile and we are not going to pretend otherwise.
If email was the reason you used it, you need a dedicated email provider, and this migration only covers the rest of your usage. That is a genuine gap and you should factor it in rather than discovering it in week two.
Credit-based pricing also does not carry over. Here you hold a USD balance and each call is priced in dollars, which means you can compare the cost of an endpoint against its value directly instead of converting through a credit rate.
A sensible way to migrate
Take the free trial balance and port one endpoint — usually profile lookup, since it is the highest volume — before touching anything else. Run it in parallel against a sample of records you already have data for, and compare fields. That tells you what your mapping layer actually needs far better than reading documentation will.
Then port search, then whatever is left. Keep the profile ID rather than the URL as your stored key while you are in there; it survives someone changing their vanity handle, which the URL does not.
What Enricho costs
Published per-call prices, no credit conversion. Failed requests are never charged.
| Request | Starter | Scale |
|---|---|---|
| Company | $0.0400 | $0.0180 |
| Company search page | $0.0400 | $0.0180 |
| Group | $0.0400 | $0.0180 |
| Group search page | $0.0400 | $0.0180 |
| Job | $0.0100 | $0.0045 |
| Job search page | $0.0100 | $0.0045 |
Frequently asked questions
Is Proxycurl really gone?
The service announced a shutdown in 2025 following legal action by LinkedIn. If you have an active integration, check your own account for the current position rather than relying on this page.
Can I get work email addresses like Proxycurl offered?
No. That is the one capability with no equivalent here. Email addresses are not public profile data and we do not offer email enrichment on any endpoint or plan.
How long does migrating take?
For a straightforward profile-and-company integration, most teams report an afternoon. The work is in the response envelope and auth header rather than in concepts, since the endpoints map closely.
Are you at risk of the same thing happening?
Legal risk in this category is real and applies to every provider including us. We return only publicly visible data, never use customer credentials or cookies, and honour data removal requests — but we are not going to claim immunity we cannot back up.