> Enrich.chat gives AI agents verified work emails and mobiles. To use it from an agent, read https://enrich.chat/agents.md . This is the Markdown version of https://enrich.chat/blog/proxycurl-alternative/

# The best Proxycurl alternatives in 2026: LinkedIn URL in, contact data out

Proxycurl shut down in July 2025 after LinkedIn sued it. We compared seven replacements on input, contact data, legal exposure and price, and mapped every endpoint you used.

By Enrich.chat Editorial. Updated October 15, 2026.

**Short answer:** Proxycurl shut down on [July 4, 2025](https://nubela.co/blog/goodbye-proxycurl/), after [LinkedIn sued it and Nubela, the company behind it,](https://www.courtlistener.com/docket/69575588/linkedin-corporation-v-nubela-pte-ltd/) over scraping with fake accounts. If you sent Proxycurl LinkedIn URLs to get emails and phone numbers, Enrich.chat is the closest swap: same URL in, work email and mobile out with a status on each, no LinkedIn login, and credits spent only on matches. For bulk profile datasets, People Data Labs or Coresignal fit better.

## Key takeaways

- Proxycurl shut down on July 4, 2025, after LinkedIn sued it and Nubela, the company behind it, on January 24, 2025. The court entered judgment on July 25, 2025.
- LinkedIn also won a consent judgment against ProAPIs, a second LinkedIn data API, on September 16, 2026. Scraper-based APIs remain a platform risk.
- Proxycurl's Starter plan was $49 a month for 2,500 credits with a 12-month commitment. A work email cost 3 credits.
- Enrich.chat takes the same LinkedIn URL, never logs in to LinkedIn, and spends credits only on matches.
- For most code, the migration is a rename: linkedin_profile_url becomes linkedin_url.

## The verdict

For teams that sent LinkedIn URLs to Proxycurl to get emails and phone numbers, **Enrich.chat** is the simplest swap: same URL in, contact data out with a status on each field, no LinkedIn login, credits spent only on matches.

- Best overall: Enrich.chat (LinkedIn URL in, email and mobile out, credits for matches only)
- Best for bulk records: People Data Labs (Full work history on each record, charged per match)
- Best for tracking job changes: Crustdata (Watchers alert you when a person changes roles)
- Public profiles at volume: Bright Data (Pay per delivered record, no contact data)

## Proxycurl alternatives at a glance

|  | Enrich.chat | People Data Labs | Coresignal | Crustdata | Enrich Layer | Bright Data | Apify actors |
| --- | --- | --- | --- | --- | --- | --- | --- |
| Takes a LinkedIn URL | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Returns a work email | Yes: status on each | Partial: Pro plan | Partial: not EEA or UK | Yes: add-on | Yes | No | Partial: some actors |
| Returns a mobile number | Yes: line type on each | Partial: Pro plan | No | Yes: add-on | Yes: personal numbers | No | Partial: some actors |
| Says it never scrapes behind a login | Yes: never logs in | Not stated | Yes | Not stated | Yes | Yes: public data only | Partial: some need cookies |
| Bills only for matches | Yes: misses cost 0 credits | Yes | Yes | Yes | Yes | Yes | Partial: plus start fees |
| Free tier | Yes: 10 lookups a day | Yes: 100 credits a month | Partial: 7-day trial | Partial: $20 in credits | Partial: trial credits | Yes: 5,000 records a month | Yes: $5 a month |
| No annual contract needed | Yes: billed monthly | Yes | Yes | Yes | Partial: 12-month plans | Yes | Yes |
| Starting price | Free, then $29 a month | $98 a month | $49 a month | Credit packs | $10 for 100 credits | $1.50 per 1,000 records | $4 per 1,000 profiles |

## The 7 best Proxycurl alternatives, ranked

Ranked for teams that sent LinkedIn URLs to Proxycurl and need contact data back. Prices come from each vendor's own site, checked October 15, 2026.

### Enrich.chat

Contact data for AI agents and apps. Send the LinkedIn URL you already have and get a work email and a mobile back, each with a status.

- Best for: Teams that used Proxycurl for contact data and want credits spent only on matches
- Pricing: Monthly plans from $29 for 100,000 credits: 10 credits per email, 250 per mobile
- Strength: Takes the LinkedIn URL you store and never logs in to LinkedIn
- Strength: Every email has a status and every mobile a line type
- Strength: Credits are spent only on matches, with unlimited seats and no annual contract
- Strength: Works in ChatGPT, Claude, Cursor or code with one prompt
- Watch out for: No personal emails, posts or full job history
- Watch out for: A mobile costs 250 credits, 25 times an email
- Watch out for: Company lookups take a domain, not a LinkedIn company URL

### People Data Labs

A large person and company dataset behind an enrichment API. Pass a LinkedIn URL in the profile field.

- Best for: Products that need full work history on many records
- Pricing: From $98 a month for 350 credits ([PDL pricing](https://www.peopledatalabs.com/pricing/person), Oct 15, 2026)
- Strength: Charges per match, not per call
- Strength: Records include work history, addresses and social profiles
- Strength: Bulk files on enterprise plans
- Watch out for: Emails and phones need the Pro plan
- Watch out for: Enterprise plans are annual contracts

### Coresignal

Employee, company and job data collected from public web sources, sold by API or as datasets.

- Best for: Data teams building their own index or analytics
- Pricing: From $49 a month for 2,500 credits; an employee record is 20 credits ([Coresignal pricing](https://coresignal.com/pricing/), Oct 15, 2026)
- Strength: Says it does not scrape behind login walls
- Strength: Collects by profile URL or shorthand name
- Strength: Webhooks and full datasets for bulk use
- Watch out for: Business email only, no mobiles, none for EEA or UK people
- Watch out for: 20 credits per employee record adds up

### Crustdata

People and company API with watchers that alert you to job changes and new matches.

- Best for: Products that track people over time
- Pricing: Credit packs: person enrich 1 to 9 credits, search 0.03 credits a result ([Crustdata pricing](https://crustdata.com/pricing), Oct 15, 2026)
- Strength: Watchers for job changes and new matches
- Strength: Billed per matched person
- Strength: Email and phone as per-request add-ons
- Watch out for: No dollar price per credit on the pricing page
- Watch out for: The Contact Enrich endpoint needs an enterprise plan

### Enrich Layer

People and company API with Proxycurl-style endpoints, parameters and credit packs.

- Best for: Teams that want the smallest code change from Proxycurl
- Pricing: $10 for 100 credits pay as you go; a person profile is 1 credit ([Enrich Layer pricing](https://enrichlayer.com/pricing), Oct 15, 2026)
- Strength: Endpoint names and flags close to Proxycurl's
- Strength: Charges only for successful requests
- Strength: Personal emails and numbers as add-ons
- Watch out for: Subscriptions are 12-month commitments
- Watch out for: A forced fresh fetch costs 9 extra credits

### Bright Data

Web data platform with a LinkedIn Scraper API for public profiles, companies, posts and jobs.

- Best for: Public profile fields and posts at high volume
- Pricing: $1.50 per 1,000 records pay as you go ([Bright Data](https://brightdata.com/products/web-scraper/linkedin), Oct 15, 2026)
- Strength: Bills only for delivered records
- Strength: Won a 2024 ruling against Meta over logged-off scraping
- Strength: Profiles, companies, posts and jobs
- Watch out for: No work emails or mobiles in its LinkedIn records
- Watch out for: Depends on public pages LinkedIn works to block

### Apify LinkedIn actors

A marketplace of LinkedIn scrapers built by independent developers and run on the Apify platform.

- Best for: One-off pulls and prototypes
- Pricing: From $4 per 1,000 profiles, $10 with email search ([HarvestAPI actor](https://apify.com/harvestapi/linkedin-profile-scraper), Oct 15, 2026)
- Strength: Low cost per profile
- Strength: Actors for profiles, posts and Sales Navigator
- Strength: No-cookie actors exist
- Watch out for: Some actors ask for your LinkedIn cookies, which risks your account
- Watch out for: Each actor has its own author, price and upkeep

## What happened to Proxycurl?

Proxycurl shut down on July 4, 2025, five months after LinkedIn sued it in federal court. [LinkedIn filed the case on January 24, 2025](https://www.courtlistener.com/docket/69575588/linkedin-corporation-v-nubela-pte-ltd/) in the Northern District of California. It named Proxycurl LLC of Wyoming, Nubela Pte. Ltd. of Singapore, founder and CEO Steven Goh, and Proxycurl's chief technology officer, Bach Le.

[LinkedIn's complaint](https://storage.courtlistener.com/recap/gov.uscourts.cand.443258/gov.uscourts.cand.443258.1.0.pdf) alleged that Proxycurl ran a network of fake accounts to scrape member data while logged in, "registering hundreds if not thousands of new accounts per day." It brought six claims, including breach of contract, fraud and a Computer Fraud and Abuse Act claim. [LinkedIn's newsroom](https://news.linkedin.com/2025/linkedin-takes-legal-action-to-defend-member-privacy) framed the suit as enforcing its User Agreement against scraping and fake accounts.

Proxycurl chose not to fight. In [his goodbye post on July 4](https://nubela.co/blog/goodbye-proxycurl/), Goh wrote that there was "no winning in fighting this." He cited the American Rule on legal fees and Microsoft's deep pockets, and called Proxycurl a business of about $10M in revenue. The [court docket](https://www.courtlistener.com/docket/69575588/linkedin-corporation-v-nubela-pte-ltd/) shows a judgment entered on July 25, 2025. Three days later, [LinkedIn announced](https://news.linkedin.com/2025/LinkedInWinsLegalBattleToProtectMemberData) that it had resolved the case. [Social Media Today reported](https://www.socialmediatoday.com/news/linkedin-wins-legal-case-data-scrapers-proxycurl/756101/) that, per LinkedIn, the permanent injunction requires Proxycurl to delete the LinkedIn data it obtained without permission and to stop accessing LinkedIn.

**Figure 1: Timeline of LinkedIn's cases against Proxycurl and ProAPIs.** Six dated events. LinkedIn sued Nubela and Proxycurl on January 24, 2025. Proxycurl shut down on July 4, 2025. The court entered judgment on July 25, 2025, and LinkedIn said on July 28, 2025 that the case was resolved. LinkedIn sued ProAPIs on October 2, 2025, and ProAPIs consented to a final judgment on September 16, 2026.

*Proxycurl closed three weeks before the court entered judgment. ProAPIs settled almost a year after LinkedIn sued it. Sources: [Nubela docket](https://www.courtlistener.com/docket/69575588/linkedin-corporation-v-nubela-pte-ltd/), [Proxycurl shutdown post](https://nubela.co/blog/goodbye-proxycurl/), [LinkedIn Newsroom](https://news.linkedin.com/2025/LinkedInWinsLegalBattleToProtectMemberData), [ProAPIs docket](https://www.courtlistener.com/docket/71527603/linkedin-corporation-v-proapis-inc/).*

LinkedIn then went after a second LinkedIn data API. On October 2, 2025, it [sued ProAPIs](https://www.courtlistener.com/docket/71527603/linkedin-corporation-v-proapis-inc/). LinkedIn alleged that ProAPIs charged customers up to $15,000 a month for scraped data, [The Record reported](https://therecord.media/linkedin-sues-data-scraping-company). On September 16, 2026, the court signed a [final judgment on consent](https://storage.courtlistener.com/recap/gov.uscourts.cand.457309/gov.uscourts.cand.457309.36.0.pdf). ProAPIs denied liability. It is now permanently barred from accessing LinkedIn through fake accounts or scraping, and it certified that it deleted the LinkedIn data it held.

## Why does it matter how a Proxycurl alternative gets its data?

The collection method decides whether your provider survives the next lawsuit. Proxycurl closed while LinkedIn's case was still open, and ProAPIs can no longer sell LinkedIn data. Customers of both had to find a new source.

[LinkedIn's User Agreement](https://www.linkedin.com/legal/user-agreement) bans software that scrapes or copies profiles. Its [help center](https://www.linkedin.com/help/linkedin/answer/a1341387) warns that members who use such tools risk having their accounts restricted or shut down. LinkedIn also says it keeps improving its defenses against scraping. Providers fall into three groups, and each carries a different risk:

- **Logged-in scrapers** drive LinkedIn accounts, either their own or yours. This is the conduct the Proxycurl and ProAPIs complaints describe. Some Apify actors, such as [this Sales Navigator scraper](https://apify.com/curious_coder/linkedin-sales-navigator-search-scraper), ask you to paste your LinkedIn cookies, which puts your own account at risk.
- **Logged-out scrapers** read public pages without an account. Courts have been friendlier here. In January 2024, [a federal judge granted Bright Data summary judgment](https://www.courtlistener.com/docket/66706470/meta-platforms-inc-v-bright-data-ltd/) on Meta's breach of contract claim over its logged-off scraping.
- **Enrichment APIs** answer from their own records. You send a LinkedIn URL as a lookup key, and nobody logs in to LinkedIn for you. Enrich.chat works this way: it never logs in to LinkedIn or uses anyone's account.

Ask every vendor how it collects LinkedIn profile data, and get the answer in writing. LinkedIn has now won judgments against [hiQ Labs in 2022](https://www.courtlistener.com/docket/6071320/hiq-labs-inc-v-linkedin-corporation/), Proxycurl in 2025 and ProAPIs in 2026. For the account risk of browser-based tools, see our review of [LinkedIn MCP servers](https://enrich.chat/blog/linkedin-mcp/).

## What should a Proxycurl replacement do?

A good replacement takes the LinkedIn URL you already store and returns the contact fields you used, with no LinkedIn login. Most teams used Proxycurl as a bridge from a profile URL to an email, a phone number and a current title. Check five things before you switch:

1. **LinkedIn URL in.** Your CRM, Sales Navigator exports and Clay tables already key people by profile URL. Re-keying them by name and company adds work and more room for a wrong match.
2. **Contact data out.** Profile JSON alone does not book meetings. Confirm the API returns a work email and a mobile number, not only a title.
3. **A status on every field.** Contact data goes stale. Enrich.chat returns a status on each work email (verified, catch_all or unknown) and a line type on each mobile (mobile or unknown). A line type describes the number, not who owns it or whether it is live. To test addresses you already hold, use the free [catch-all checker](https://enrich.chat/tools/catch-all-checker/).
4. **Misses cost nothing.** Profile URL lookups miss some people. With default settings, [Proxycurl's Person Lookup](https://web.archive.org/web/20250114154921/https://nubela.co/proxycurl/docs/openapi-3.0.yaml) charged 2 credits even when it returned null. Pick a vendor that bills only when it finds something.
5. **No annual lock-in.** [Proxycurl's monthly and annual plans](https://web.archive.org/web/20250531112541/https://nubela.co/proxycurl/pricing) both carried a 12-month commitment. When a vendor can close, a year-long commitment is a risk you carry.

The comparison table at the top of this page scores each alternative on these points. For a wider field, see our list of the [best LinkedIn email finders](https://enrich.chat/blog/best-linkedin-email-finder/).

## How do Proxycurl endpoints map to Enrich.chat?

Most Proxycurl calls become one Enrich.chat GET request with a renamed parameter: `linkedin_profile_url` becomes `linkedin_url`. The table lists each Proxycurl endpoint and its credit cost from [Proxycurl's archived API spec](https://web.archive.org/web/20250114154921/https://nubela.co/proxycurl/docs/openapi-3.0.yaml), next to the Enrich.chat call from [agents.md](https://enrich.chat/agents.md).

| Proxycurl endpoint | Enrich.chat call | Parameters and changes |
| --- | --- | --- |
| Person Profile 1 credit | `GET /v1/person` | Pass `linkedin_url` and `fields=profile`. Returns current role, seniority, location and company, not posts or job history. |
| Personal Email Lookup 1 credit per email | `GET /v1/email` | Pass `linkedin_url`. Returns the work email with a status, not personal addresses. |
| Personal Contact Number Lookup 1 credit per number | `GET /v1/mobile` | Pass `linkedin_url`. Adds `mobile.line`: mobile or unknown. |
| Work Email Lookup 3 credits | `GET /v1/email` | Pass `linkedin_url`. Answers in the same request, so drop `callback_url`. Status is verified, catch_all or unknown. |
| Company Profile 1 credit | `GET /v1/company` | Pass `domain`, not a LinkedIn company URL. |
| Person Lookup 2 credits | `GET /v1/person` | Pass `name` and `company`. Uses credits only on a match. |
| Reverse Email Lookup 3 credits | `GET /v1/person` | Pass `email`. Returns the same person object as a URL lookup. |
| Role Lookup and Employee Listing 3 credits per result | `GET /v1/company/people` | Pass `domain` and `title` to list people at one company. |
| Person Search 3 credits per result | `GET /v1/search` | Pass `q` in plain English, plus filters such as title, seniority and country. |

Proxycurl's paths all sat under `nubela.co/proxycurl/api/`, for example `v2/linkedin` for Person Profile and `contact-api/personal-contact` for phone numbers. Figure 2 maps the five most used.

**Figure 2: Proxycurl endpoints mapped to Enrich.chat calls.** Five Proxycurl endpoints on the left, each with an arrow to the Enrich.chat call that replaces it: Person Profile to GET /v1/person, Personal Email Lookup to GET /v1/email, which returns a work email only, Personal Contact Number to GET /v1/mobile, Work Email Lookup to GET /v1/email, and Company Profile to GET /v1/company, which takes a domain.

*The five Proxycurl endpoints most teams called, and the Enrich.chat call that replaces each. The dashed row has no exact match: Enrich.chat returns work emails, not personal ones. Sources: [Proxycurl's archived API spec](https://web.archive.org/web/20250114154921/https://nubela.co/proxycurl/docs/openapi-3.0.yaml), [Enrich.chat agents.md](https://enrich.chat/agents.md).*

Enrich.chat has two gaps for former Proxycurl users. It does not return personal emails, LinkedIn posts or full job history. It returns the current role, company, work email and mobile, with a status on the email and mobile. And company lookups take a domain, so read `company.domain` from the person response before you call `/v1/company`. The [LinkedIn URL to contact API](https://enrich.chat/api/linkedin-to-contact/) page shows the full response.

### The same lookup in Python

This replaces a Proxycurl Person Profile call that asked for contact fields. It handles the two responses that catch most migrations: 429 for rate limits and 402 when the free lookups run out.

```
# Before (offline since July 4, 2025)
# GET https://nubela.co/proxycurl/api/v2/linkedin?linkedin_profile_url=...

# After
import os
import time
import requests

# Optional: a paid key from enrich.chat/account/ lifts the free limit
KEY = os.environ.get("ENRICH_KEY")
HEADERS = {"Authorization": "Bearer " + KEY} if KEY else {}

def enrich(linkedin_url):
    params = {"linkedin_url": linkedin_url, "fields": "email,mobile"}
    while True:
        r = requests.get("https://enrich.chat/v1/person", params=params,
                         headers=HEADERS, timeout=30)
        if r.status_code == 429:              # too fast: wait, then retry
            time.sleep(int(r.json().get("retry_after", 2)))
            continue
        if r.status_code == 402:              # free limit reached
            raise RuntimeError(r.json().get("upgrade_url"))
        r.raise_for_status()
        return r.json()                       # {"found": false} uses 0 credits

p = enrich("linkedin.com/in/jane-doe-ops")
if p.get("found"):
    email, mobile = p.get("work_email") or {}, p.get("mobile") or {}
    # status: verified, catch_all or unknown. line: mobile or unknown.
    print(email.get("value"), email.get("status"))
    print(mobile.get("value"), mobile.get("line"))
```

No API key is needed: each IP address gets 10 free lookups a day. For more, log in at [enrich.chat/account/](https://enrich.chat/account/) with your email, pick a plan and pay through checkout. Your key, which starts with `pp_`, appears on that page. Send it as `Authorization: Bearer pp_...`. Keep batches at 5 requests a second or less.

## How much did Proxycurl cost, and what do alternatives cost now?

Proxycurl's Starter plan cost $49 a month for 2,500 credits, or $0.020 a credit, with a 12-month commitment. That is from its [pricing page as archived in May 2025](https://web.archive.org/web/20250531112541/https://nubela.co/proxycurl/pricing). Pay-as-you-go packs started at $10 for 100 credits. A work email cost 3 credits, so $0.06 on Starter.

| Lookup | Enrich.chat, 2026 | Proxycurl Starter, 2025 |
| --- | --- | --- |
| Person profile | 5 credits | 1 credit ($0.02) |
| Work email | 10 credits, about $0.0029 on Growth | 3 credits ($0.06) |
| Mobile or personal number | 250 credits, about $0.0725 on Growth | 1 credit per number ($0.02) |
| No match found | 0 credits | Free on most endpoints; Person Lookup billed anyway |
| Commitment | Monthly plan, cancel anytime, no annual contract | 12 months on monthly and annual plans |

Enrich.chat is sold as monthly credit plans: Growth $29 for 100,000 credits, Scale $90 for 500,000 credits, Pro $299 for 2,500,000 credits. The dollar figures above assume you use every credit on Growth. On that basis it costs more per mobile than Proxycurl's Starter rate and less per work email, and a lookup that finds nothing uses 0 credits. See [Enrich.chat pricing](https://enrich.chat/pricing/) for details.

Here is what the other alternatives charged when we checked on October 15, 2026:

- [People Data Labs](https://www.peopledatalabs.com/pricing/person): a free plan of 100 credits a month with contact fields hidden, then Pro from $98 a month for 350 credits. Our [People Data Labs pricing guide](https://enrich.chat/blog/people-data-labs-pricing/) breaks this down.
- [Coresignal](https://coresignal.com/pricing/): the Mini plan is $49 a month for 2,500 credits. One multi-source employee record costs 20 credits, so Mini covers about 125 records.
- [Crustdata](https://crustdata.com/pricing): $20 in free credits, then credit packs. A base person profile is 1 credit, a work email adds 1 and a phone adds 2. The page does not list a dollar price per credit.
- [Enrich Layer](https://enrichlayer.com/pricing): pay-as-you-go packs run from $10 for 100 credits to $1,000 for 46,297 credits, the same packs Proxycurl sold. A person profile is 1 credit.
- [Bright Data](https://brightdata.com/products/web-scraper/linkedin): 5,000 free LinkedIn records a month, then $1.50 per 1,000 records, or $499 a month for 384,000 records.
- [Apify's HarvestAPI actor](https://apify.com/harvestapi/linkedin-profile-scraper): $4 per 1,000 profiles, or $10 per 1,000 with email search. You pay from your [Apify plan](https://apify.com/pricing), and the free plan includes $5 of usage a month.

## When is another Proxycurl alternative the better choice?

Choose another tool when you need data Enrich.chat does not return, or a dataset rather than lookups. Each of these has a real edge, based on its own docs as of October 15, 2026:

- **People Data Labs** when you need full work history, addresses and social profiles on many records. Its [enrichment API](https://docs.peopledatalabs.com/docs/input-parameters-person-enrichment-api) takes a LinkedIn URL in the `profile` field, and [PDL charges per match](https://docs.peopledatalabs.com/docs/reference-person-enrichment-api). Bulk files come with enterprise plans.
- **Crustdata** when you track people over time. Its watchers alert you to job changes and new matches, billed from 0.5 credits per new result, per its [pricing page](https://crustdata.com/pricing). Its [Contact Enrich docs](https://docs.crustdata.com/person-docs/contact/enrich) say people with no match are free.
- **Coresignal** when you build your own index. It sells employee, company and job datasets, and its [Collect endpoint](https://docs.coresignal.com/employee-data/api/collect) takes a profile URL. Its [Contact Enrichment API](https://docs.coresignal.com/employee-data/api/contact-enrichment-api) returns business emails only, and none for people in the EEA or UK.
- **Enrich Layer** when you want the smallest code change. Its [Person Profile endpoint](https://enrichlayer.com/docs/api/v2/people-api/person-profile) takes a `profile_url` and keeps Proxycurl-style flags such as `use_cache` and `personal_contact_number`. Its [about page](https://enrichlayer.com/about) says it does not collect data behind login walls. Its docs also offer forced fresh fetches for 9 extra credits, so ask how those work.
- **Bright Data** when you need public profile fields, posts and jobs at volume, and no contact data. Its [LinkedIn Scraper API](https://brightdata.com/products/web-scraper/linkedin) bills only for delivered records.
- **Apify** for one-off pulls and prototypes. Pick an actor marked no-cookie, and never paste your LinkedIn session cookies into a third-party tool.

If you only need phone numbers, our guide to [finding a phone number from a LinkedIn profile](https://enrich.chat/blog/find-phone-number-from-linkedin/) compares the options.

## How do you migrate off Proxycurl in an afternoon?

Swap the base URL and the parameter, map the statuses, then test on your own URLs before you move traffic. Work through this checklist:

1. Search your code for `nubela.co/proxycurl` and `linkedin_profile_url` to find every call.
2. Change the base URL to `https://enrich.chat/v1` and the parameter to `linkedin_url`.
3. Ask only for the fields you use with `fields=email,mobile,profile`. Mobiles cost the most.
4. Replace the Work Email webhook (`callback_url`) with a normal request. The answer comes back in the same call.
5. Map the statuses. Treat `catch_all` emails as risky, and store `mobile.line` with each row.
6. Update error handling. [Proxycurl returned 403](https://web.archive.org/web/20250114154921/https://nubela.co/proxycurl/docs/openapi-3.0.yaml) when credits ran out. Enrich.chat returns 402 with an `upgrade_url` that points to [/account/](https://enrich.chat/account/), and 429 with `retry_after`.
7. Run 10 of your old Proxycurl URLs through the free tier, and compare each field with what you stored.
8. When the free tier is not enough, pick Growth, Scale or Pro on your [account page](https://enrich.chat/account/) and add the key to your requests.
9. Honor removals. People can opt out at [enrich.chat/opt-out](https://enrich.chat/opt-out/), and you stay responsible for TCPA, CAN-SPAM and GDPR rules.

You can also run the test without code. Paste this into ChatGPT, Claude or Cursor with a few URLs you used to send to Proxycurl:

```text
Use www.enrich.chat to enrich these LinkedIn URLs with work email, mobile, title and company. Flag catch_all emails as risky and tell me the total credits_used: [paste LinkedIn URLs]
```

Your agent reads the instructions, calls the API and returns a table. To try one profile in the browser first, use the free [LinkedIn email and phone finder](https://enrich.chat/tools/linkedin-email-finder/).

## Frequently asked questions

### Why did Proxycurl shut down?

Proxycurl shut down on July 4, 2025, after LinkedIn sued it and Nubela, the company behind it, in January 2025. [LinkedIn's complaint](https://storage.courtlistener.com/recap/gov.uscourts.cand.443258/gov.uscourts.cand.443258.1.0.pdf) alleged that Proxycurl used fake accounts to scrape member profiles while logged in. Founder Steven Goh [wrote](https://nubela.co/blog/goodbye-proxycurl/) that there was no winning a fight against LinkedIn and Microsoft. The court entered judgment on July 25, 2025, and LinkedIn said the injunction requires Proxycurl to delete the LinkedIn data it collected.

### Is Proxycurl coming back?

No. The Proxycurl team now runs NinjaPear, a B2B data company at nubela.co, and LinkedIn says [the court order](https://www.socialmediatoday.com/news/linkedin-wins-legal-case-data-scrapers-proxycurl/756101/) bars Proxycurl from accessing LinkedIn. NinjaPear is not a drop-in replacement. [Its Person Profile endpoint](https://nubela.co/docs) takes a work email, a first name plus employer website, or a website plus role, not a LinkedIn URL, and it charges 3 credits even when no data is found.

### Is it legal to use a LinkedIn scraper API?

It depends on how the data is collected, and this is not legal advice. [LinkedIn's User Agreement](https://www.linkedin.com/legal/user-agreement) bans scraping, and LinkedIn has won judgments against [hiQ Labs](https://www.courtlistener.com/docket/6071320/hiq-labs-inc-v-linkedin-corporation/) (2022), Proxycurl (2025) and [ProAPIs](https://storage.courtlistener.com/recap/gov.uscourts.cand.457309/gov.uscourts.cand.457309.36.0.pdf) (2026). Courts have been more open to logged-out scraping of public pages: [Bright Data won summary judgment](https://www.courtlistener.com/docket/66706470/meta-platforms-inc-v-bright-data-ltd/) on Meta's contract claim in 2024. Tools that log in with fake accounts or your cookies carry the most risk.

### Is there a free Proxycurl alternative?

Yes, several have free tiers. Enrich.chat gives every IP address 10 lookups a day with no signup, enough to test your old Proxycurl URLs. [People Data Labs](https://www.peopledatalabs.com/pricing/person) offers 100 free credits a month but hides contact fields. [Bright Data](https://brightdata.com/products/web-scraper/linkedin) includes 5,000 LinkedIn records a month, and [Apify's free plan](https://apify.com/pricing) includes $5 of usage a month. We checked each free tier on October 15, 2026.

### Can I still get an email and phone number from a LinkedIn URL?

Yes. Send the URL to an enrichment API that indexes people by LinkedIn URL. With Enrich.chat, GET /v1/person?linkedin_url=...&fields=email,mobile returns the work email with a status of verified, catch_all or unknown, and the mobile with a line type of mobile or unknown. Credits are spent only when a field is found. See our guide to [finding a phone number from LinkedIn](https://enrich.chat/blog/find-phone-number-from-linkedin/).

### Is there a drop-in replacement for Proxycurl's API?

[Enrich Layer](https://enrichlayer.com/docs/api/v2/people-api/person-profile) is the closest in shape: its endpoints, parameters such as profile_url and use_cache, and its pay-as-you-go credit packs mirror Proxycurl's. Other alternatives need a small rewrite. Moving to Enrich.chat usually means renaming linkedin_profile_url to linkedin_url, changing the base URL, and handling 402 and 429 responses, as the migration table on this page shows.

## Sources

1. [LinkedIn Corporation v. Nubela Pte. Ltd., No. 3:25-cv-00828, docket](https://www.courtlistener.com/docket/69575588/linkedin-corporation-v-nubela-pte-ltd/)
2. [Complaint, LinkedIn Corporation v. Nubela Pte. Ltd.](https://storage.courtlistener.com/recap/gov.uscourts.cand.443258/gov.uscourts.cand.443258.1.0.pdf)
3. [Proxycurl Shuts Down. Thank you.](https://nubela.co/blog/goodbye-proxycurl/)
4. [LinkedIn takes legal action to defend member privacy](https://news.linkedin.com/2025/linkedin-takes-legal-action-to-defend-member-privacy)
5. [LinkedIn Wins Legal Battle to Protect Member Data](https://news.linkedin.com/2025/LinkedInWinsLegalBattleToProtectMemberData)
6. [LinkedIn Wins Legal Case Against Data Scrapers](https://www.socialmediatoday.com/news/linkedin-wins-legal-case-data-scrapers-proxycurl/756101/)
7. [LinkedIn Corporation v. ProAPIs Inc., No. 5:25-cv-08393, docket](https://www.courtlistener.com/docket/71527603/linkedin-corporation-v-proapis-inc/)
8. [Final Judgment on Consent, LinkedIn Corporation v. ProAPIs Inc.](https://storage.courtlistener.com/recap/gov.uscourts.cand.457309/gov.uscourts.cand.457309.36.0.pdf)
9. [LinkedIn sues data scraping company](https://therecord.media/linkedin-sues-data-scraping-company)
10. [hiQ Labs, Inc. v. LinkedIn Corporation, No. 3:17-cv-03301, docket](https://www.courtlistener.com/docket/6071320/hiq-labs-inc-v-linkedin-corporation/)
11. [Meta Platforms, Inc. v. Bright Data Ltd., No. 3:23-cv-00077, docket](https://www.courtlistener.com/docket/66706470/meta-platforms-inc-v-bright-data-ltd/)
12. [Proxycurl API pricing (archived May 31, 2025)](https://web.archive.org/web/20250531112541/https://nubela.co/proxycurl/pricing)
13. [Proxycurl OpenAPI 3.0 spec (archived January 14, 2025)](https://web.archive.org/web/20250114154921/https://nubela.co/proxycurl/docs/openapi-3.0.yaml)
14. [User Agreement, section 8.2](https://www.linkedin.com/legal/user-agreement)
15. [Prohibited software and extensions](https://www.linkedin.com/help/linkedin/answer/a1341387)
16. [Person data pricing](https://www.peopledatalabs.com/pricing/person)
17. [Person Enrichment API reference](https://docs.peopledatalabs.com/docs/reference-person-enrichment-api)
18. [Input parameters, Person Enrichment API](https://docs.peopledatalabs.com/docs/input-parameters-person-enrichment-api)
19. [Pricing](https://coresignal.com/pricing/)
20. [Contact Enrichment API](https://docs.coresignal.com/employee-data/api/contact-enrichment-api)
21. [Collect: Employee API](https://docs.coresignal.com/employee-data/api/collect)
22. [Crustdata pricing](https://crustdata.com/pricing)
23. [Person Contact Enrich](https://docs.crustdata.com/person-docs/contact/enrich)
24. [Pricing](https://enrichlayer.com/pricing)
25. [About Enrich Layer](https://enrichlayer.com/about)
26. [Person Profile Endpoint](https://enrichlayer.com/docs/api/v2/people-api/person-profile)
27. [LinkedIn Scraper API](https://brightdata.com/products/web-scraper/linkedin)
28. [Apify pricing](https://apify.com/pricing)
29. [LinkedIn Profile Scraper + Email (No Cookies)](https://apify.com/harvestapi/linkedin-profile-scraper)
30. [Linkedin Sales Navigator Scraper](https://apify.com/curious_coder/linkedin-sales-navigator-search-scraper)
31. [NinjaPear API documentation](https://nubela.co/docs)

## Try this prompt

Replace your Proxycurl lookups

```text
Use www.enrich.chat to enrich these LinkedIn URLs with work email, mobile, title and company, and flag catch_all emails as risky: [paste LinkedIn URLs]
```

## Related

- [LinkedIn URL to Email and Mobile API](https://enrich.chat/api/linkedin-to-contact/)
- [People Data Labs pricing](https://enrich.chat/blog/people-data-labs-pricing/)
- [Clearbit alternatives (2026): what to use now that Clearbit is HubSpot-only](https://enrich.chat/alternatives/clearbit/)