Proxycurl
Proxycurl's own site says it is no longer in service. If you built person lookups on it, one FoxAPIs endpoint takes a name and a company and returns a person record today. It returns less than a full profile in several places, and this page lists each one.
Read 22 November 20264 sources linkedPOST /v1/enrich_personWhere FoxAPIs wins
- You need something that is running today: Proxycurl is not, and there is no renewal to wait on.
- You want to know how sure the match is, why it was accepted and which same-name people were set aside.
- You want to pay per call from credits you buy once, with no subscription.
Where Proxycurl wins
- You need a profile with the free-text description of each job, the company website for each job, the city and country, and follower counts: this call returns title, company and dates for each job and none of the others.
- You look people up by work email or by profile slug: this call needs a name, and takes a company, a title, a profile link, a Twitter handle or a domain to narrow the match.
- You use the similar-people list: this call does not return one.
Who Proxycurl is for
Teams that built person lookups on Proxycurl's API and need something that is still running, without re-doing the whole integration.
What happened to Proxycurl
Proxycurl was a person and company data API from Nubela. What follows is only what Nubela and LinkedIn published, with the page each statement comes from.
- Proxycurl's page says "Proxycurl is no longer in service" and points visitors to NinjaPear, a product from the same company. Proxycurl pageread 22 November 2026
- Nubela's founder post, dated 4 July 2025, says LinkedIn filed a lawsuit against Proxycurl in January 2025, that shutting Proxycurl down was needed to comply with the legal settlement with LinkedIn, and that the team is now focused on NinjaPear, which it calls a Competitive Intelligence Data company. The post does not mention refunds. Goodbye Proxycurlread 22 November 2026
- LinkedIn's post of 28 July 2025 says LinkedIn has successfully resolved its lawsuit against Proxycurl. It does not give the settlement terms. LinkedIn news postread 22 November 2026
- Nubela's documentation page now lists an employee profile call, GET /api/v2/employee/profile, at 3 Nubela credits a request, charged even when no data is found. The page states no price for a credit. Nubela documentationread 22 November 2026
Read on 22 November 2026 from Proxycurl's page. We state only what the pages we link showed that day.
How the two differ
Proxycurl returned a profile record for a person. A FoxAPIs enrich_person call resolves a person from a name and a company and returns the links, history and contact candidates it could confirm, with its confidence stated. The shapes overlap on names, social links, work history and education, and differ on location, bio and follower counts, which this call does not return.
Field by field: Nubela's employee profile response against ours
We lose rows here. 9 of the 20 Proxycurl fields have no field of ours. Where a row says we do not return it, we do not.
We could not find Proxycurl's own Person Profile response documentation online. The nearest page Nubela publishes is the employee profile call that replaced it, so that is the list compared here.
| Nubela employee profile field | Ours | What we return (real sample, 19 November 2026) |
|---|---|---|
| id | We do not return it | We return no profile id. |
| slug | Closest field | linkedin_url: The profile address, which contains the slug. We return the whole address, not the slug on its own. |
| profile_pic_url | Closest field | photo_url |
| first_name | Closest field | full_name: One field for the whole name; we do not split it. |
| middle_name | Closest field | full_name: One field for the whole name; we do not split it. |
| last_name | Closest field | full_name: One field for the whole name; we do not split it. |
| full_name | We return it | full_name: Same data, our field name. |
| bio | We do not return it | We do not return a bio. |
| follower_count | We do not return it | We do not return follower counts. |
| following_count | We do not return it | We do not return follower counts. |
| country | We do not return it | We do not return a location. |
| city | We do not return it | We do not return a location. |
| state | We do not return it | We do not return a location. |
| x_handle | We return it | twitter_handle: Same data, our field name. |
| x_profile_url | We return it | twitter_url: Same data, our field name. |
| personal_website | We do not return it | We do not return a personal website. |
| work_experience | Closest field | employment_history: Title, company and start and end dates for each job, with a confidence for each. No company website and no job description. |
| education | Closest field | education: Institution and degree text for each entry, with a confidence for each. No separate major field. |
| work_email_lookup | Closest field | emails: Email candidates labelled by how we came by them (built from the company's address format, or seen in a search). None in the sample was confirmed by delivery. |
| similar_people | We do not return it | We do not return a similar-people list. |
Ours only: github_url and other profile links, phones, news_mentions, identity_verification (why the match was accepted), possibly_someone_else (same-name people set aside) and deeper_dossier.
Source for the Proxycurl column: Nubela documentation page, read 22 November 2026.
What a FoxAPIs call returns
POST /v1/enrich_person
Give it a name and a company. It resolves the person and returns confirmed profile links, employment and education history, email candidates each labelled by how we came by them, phone numbers, recent news about the person, and an identity check that says why the match was accepted and which same-name people were set aside. Costs 100 credits a call.
| Field | Real example (19 November 2026) |
|---|---|
| full_name | Patrick Collison |
| employer | Stripe |
| title | none |
| overall_confidence | 0.45 |
| linkedin_url | (text, not shown here) |
| twitter_url | none |
| github_url | none |
| photo_url | none |
| emails | a list of 5 |
| phones | none |
| employment_history | a list of 2 |
| education | a list of 3 |
| news_mentions | a list of 8 |
| identity_verification | an object with 16 fields |
| possibly_someone_else | a list of 4 |
curl -X POST https://api.foxapis.com/v1/enrich_person \
-H "Authorization: Bearer YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{"name":"Satya Nadella","company":"Microsoft"}'Price at the costliest listed tier
| Proxycurl or FoxAPIs | Price |
|---|---|
| Proxycurl | No price: the service ended on 4 July 2025. source |
| Nubela's current employee profile call | 3 Nubela credits a request, charged even when nothing is found. The page does not state a price for a credit, so we show no dollar figure for it. source |
| FoxAPIs /v1/enrich_person | $0.980 a call: 100 credits a call times the price per credit on the Builder plan, calculated by us. The welcome credits cover about 10 calls, no card. |
Dollar figures for FoxAPIs are computed from plans.json when this page is built; none is typed. We show a dollar figure for Proxycurl only where its own pages gave the numbers.
Start with 1,000 credits
Start with 1,000 credits, no card. They arrive once you confirm your email and expire 90 days after they are added; credits you buy never expire. Then from $10. Type your email and the key appears on this page, once, with the request below filled in.
By continuing you agree to the Terms and the Privacy page.
Key created. It is shown once: copy it now.
Move one call
Before: Nubela's current employee profile request (Proxycurl's own is gone), from its documentation
curl -G https://nubela.co/api/v2/employee/profile \ -H "Authorization: Bearer YOUR_NUBELA_KEY" \ --data-urlencode "first_name=Satya" \ --data-urlencode "last_name=Nadella" \ --data-urlencode "employer_website=https://microsoft.com"
After: the same job on FoxAPIs. Replace YOUR_KEY with the key from the box above.
curl -X POST https://api.foxapis.com/v1/enrich_person \
-H "Authorization: Bearer YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{"name":"Satya Nadella","company":"Microsoft"}'Map first_name and last_name to name, and the employer website to company or domain. A work email cannot be the input here.
Questions before you switch
Is Proxycurl really gone?
Its own page says it is no longer in service, and the founder's post dated 4 July 2025 says it was shut down. Both are linked above.
Does the call return a LinkedIn profile URL?
It returns a profile link in the linkedin_url field when one could be confirmed for the person; in our sample it was filled. It does not return the content of a profile.
Are the emails verified?
No. Emails come back as candidates, each labelled by how we came by them, such as built from the company's address format or seen in a search result. None in our sample had been checked by delivery.
Can I keep the same code?
No. The request takes a name and a company, and the response has a different shape. The migration snippet below shows the request; the table above shows which fields map.
When to stay with Proxycurl
- You need a profile with the free-text description of each job, the company website for each job, the city and country, and follower counts: this call returns title, company and dates for each job and none of the others.
- You look people up by work email or by profile slug: this call needs a name, and takes a company, a title, a profile link, a Twitter handle or a domain to narrow the match.
- You use the similar-people list: this call does not return one.
When a FoxAPIs call is the better fit
- You need something that is running today: Proxycurl is not, and there is no renewal to wait on.
- You want to know how sure the match is, why it was accepted and which same-name people were set aside.
- You want to pay per call from credits you buy once, with no subscription.