Proxycurl Is Dead: What LinkedIn's Scraper Crackdown Means for Your Contact List in 2026

Quick answer: Proxycurl shut down on July 4, 2025 after LinkedIn filed a lawsuit earlier that year. The closure does not prove that every way of saving professional contact information is unlawful, but it does show the risk of building a contact process around bulk extraction, platform circumvention, or a provider whose data source can disappear. In 2026, organizations should know where contact data comes from, whether they are permitted to collect and use it, and how they will maintain the resulting records independently of one extraction service.

Proxycurl's closure matters beyond the customers who used its API. It exposes a larger weakness in contact-data workflows: teams often evaluate the output but ignore the collection method.

If a provider returns a name, job title, company, email address, or phone number, the result looks like an ordinary contact record. The legal, contractual, privacy, and operational questions sit behind that clean row of data.

This article explains those questions in practical terms. It is general information, not legal advice. Organizations should review their own use case, jurisdiction, platform agreements, and data-protection obligations with qualified advisers.

‍

‍

‍

What happened to Proxycurl?

Proxycurl was a business-data API operated by Nubela. On July 4, 2025, its founder published a shutdown announcement stating that LinkedIn had filed a lawsuit against Proxycurl in January 2025. The announcement said the business was closing and referred to a legal settlement with LinkedIn.

That gives us two facts from Proxycurl's own statement:

• LinkedIn filed a lawsuit in January 2025.
• Proxycurl shut down on July 4, 2025.

The announcement also explained that existing customers had been assisted with moving away from the service. For teams that depended on Proxycurl, the immediate problem was not theoretical. An API used in production was no longer available.

The broader lesson is not that one replacement API solves the problem. Replacing one source with another without reviewing how the new provider obtains, updates, licenses, and protects its data repeats the same dependency.

‍

‍

‍

Why "public data" is not a complete answer

People often reduce LinkedIn scraping questions to one sentence: "The profile is public, so it is safe to collect."

That conclusion is too broad.

Public visibility may be relevant to some legal questions, but it does not automatically settle:

• The website's contractual terms
• Restrictions on automated access
• Copyright or database rights
• Privacy and data-protection obligations
• Consent or notice requirements
• Anti-spam and electronic-marketing rules
• The purpose for which the information is reused
• Security and retention requirements

LinkedIn's current User Agreement says members must not use software, scripts, robots, crawlers, browser plugins, add-ons, or other processes to scrape or copy its services, including profiles and other data. It also prohibits bypassing access controls and using unauthorized automated methods to download contacts.

That language is wider than a distinction between public pages and pages behind a login. A profile being visible does not mean LinkedIn has authorized every automated collection method.

The practical conclusion is straightforward: do not treat "public" as a compliance certificate.

‍

‍

‍

Public pages and logged-in access still differ

The distinction between publicly accessible information and information available only after login still matters, but not because one side is automatically allowed.

‍

Publicly accessible information

This is information a person can view without authenticating. Collection may avoid questions related to account credentials or logged-in access controls, but the collector still needs to consider terms, privacy obligations, purpose, scale, and local law.

‍

Information behind login

Logged-in access adds more concerns. Automation may use an account, cookies, session tokens, or credentials. It may also encounter platform controls, rate limits, visibility settings, and information intended for a narrower audience.

‍

Restricted or hidden information

Trying to bypass a technical control, obtain information a user has not made available, or reuse credentials without authorization creates a different level of risk. Teams should not normalize these methods as routine prospecting.

The exact legal analysis depends on facts and jurisdiction. The operational rule is easier: the more a workflow depends on automation, authentication, circumvention, or bulk collection, the more scrutiny it requires.

‍

‍

‍

Does LinkedIn ban users for scraping?

LinkedIn's User Agreement gives the platform the right to restrict, suspend, or terminate accounts that breach the agreement, break the law, or misuse the service. The same agreement prohibits scraping, copying through plugins or automation, bypassing controls, and unauthorized automated contact downloads.

That means account restriction is a real contractual risk. It does not mean every user performing every contact action will receive the same outcome. Enforcement can depend on the activity, scale, detection, history, and other circumstances.

Teams should avoid two unsafe promises:

• "This tool can never get your account restricted."
• "Saving visible information is always illegal."

Neither statement reflects the complexity of the issue. Review the method and the purpose rather than relying on a blanket claim.

‍

‍

‍

What Proxycurl's closure changes for contact teams

The shutdown should change how organizations assess contact-data tools and workflows.

‍

Data provenance becomes a buying requirement

Ask a provider where its information comes from. A vague answer such as "public sources" is not enough for a risk review.

Useful questions include:

• Is the data supplied directly by users, licensed, aggregated, inferred, or scraped?
• Does collection require a logged-in account?
• Are fake or shared accounts involved?
• Does the service bypass rate limits or access controls?
• How often is the information refreshed?
• Can the provider respond to correction or deletion requests?
• What happens to customer data if the provider closes?

The provider may not disclose every technical detail, but it should be able to explain the categories of sources and its responsibilities.

‍

Scale changes the risk profile

Saving the business details of a person you are actively speaking with is not operationally identical to collecting millions of profiles through automated infrastructure.

Scale affects:

• The number of people impacted
• The likelihood of outdated or incorrect records
• Security requirements
• Notice and rights-request processes
• Platform detection and enforcement
• The consequences of a provider failure

A workflow should collect the minimum volume needed for a defined purpose, not the maximum volume a tool can return.

‍

A contact list needs its own source of truth

An extraction provider should not be the only place where relationship data exists. Once an organization has an approved business contact, it needs a maintained record with ownership, status, context, access, and review rules.

Otherwise, teams repeatedly extract the same person, create duplicates, or lose the relationship when an API changes.

For a practical record structure, see Company Contact List Format: What Fields Should Your Team Include?.

‍

‍

‍

A safer decision process for LinkedIn contact collection

"Safer" does not mean guaranteed lawful or immune from platform enforcement. It means the organization has reduced avoidable uncertainty and documented its decision.

‍

1. Define the business purpose

State why the contact is needed. Examples may include following up after an agreed introduction, maintaining a supplier relationship, recording an event connection, or contacting a person who has requested information.

Avoid collecting profiles first and inventing a purpose later.

‍

2. Check the platform's current rules

Review LinkedIn's User Agreement and any terms applying to the account or product being used. Terms can change. A blog post, vendor promise, or old court decision should not replace the current agreement.

‍

3. Identify the collection method

Document whether the workflow is manual, user-initiated, automated, bulk, API-based, browser-based, or dependent on authenticated access. Do not hide the method behind a generic label such as "enrichment."

‍

4. Record the source

Store enough source information to understand where the business details came from and when they were added. This supports verification and helps the organization respond when information changes.

‍

5. Minimize the fields

Collect only what the approved workflow needs. A name, company, role, business email, or phone number may be sufficient. More data creates more maintenance and responsibility.

‍

6. Verify before outreach

Professional profiles change. People move companies, change roles, and remove contact details. Verify that the person, company, and communication channel are still correct before using the record.

‍

7. Apply outreach rules

Contact collection and permission to send marketing communications are not the same question. Follow applicable anti-spam, privacy, and direct-marketing requirements. Provide required notices and honor objections.

‍

8. Set retention and deletion rules

Decide when unused, inaccurate, or no-longer-needed records will be reviewed or removed. A contact database should not grow indefinitely merely because storage is available.

‍

‍

‍

Where ContactBook fits, and where it does not

ContactBook's public LinkedIn extension page says users can save basic contact details, including name, job title, company, and email when visible, from a LinkedIn profile into a ContactBook workspace. It also documents notes and reminders as part of that workflow.

ContactBook can then support contact organization through Groups, tags, Spaces, search, notes, sharing, and permissions, according to its current feature pages.

That product role should not be overstated.

ContactBook does not make every collection method compliant. It does not override LinkedIn's User Agreement, determine whether an organization has a lawful basis, grant permission for marketing outreach, or replace legal review. Users remain responsible for how they access, collect, store, share, and use contact information.

Before using any LinkedIn-related extension, organizations should compare its operation with LinkedIn's current terms and their own policies. If the workflow is unclear, pause and obtain product, privacy, or legal confirmation.

‍

‍

‍

Do not replace Proxycurl with another black box

The fastest response to a provider shutdown is to search for "Proxycurl alternatives." That may restore a broken integration, but it does not solve the underlying governance problem.

Evaluate a replacement across four areas:

Keep the evaluation short enough to use but specific enough to expose uncertainty. If a provider cannot answer the source question, that is information for the buying decision.

‍

‍

‍

Build a contact list that survives source changes

A durable contact list should not be a frozen export of profile data. It should be a maintained business asset.

For each approved contact, record:

• The current business identity and contact method
• The relationship purpose
• The internal owner or responsible role
• The source and date collected
• The appropriate group or category
• The people permitted to access it
• The last verified date
• The retention or review trigger

If an enrichment API, extension, or social platform becomes unavailable, the organization can still manage established relationships. The source may change, but the contact-management process remains.

‍

‍

‍

Frequently asked questions

‍

When did Proxycurl shut down?

Proxycurl announced its shutdown on July 4, 2025. Its founder said LinkedIn had filed a lawsuit against the company in January 2025 and referred to a legal settlement.

‍

Is LinkedIn scraping legal?

There is no universal yes-or-no answer because the analysis depends on the method, data, purpose, jurisdiction, contracts, and other facts. LinkedIn's current User Agreement separately prohibits using software, scripts, crawlers, browser plugins, and other processes to scrape or copy its services.

‍

Can LinkedIn restrict an account for automated scraping?

LinkedIn's User Agreement says it may restrict, suspend, or terminate an account for breaching the agreement, breaking the law, or misusing the services. It also prohibits scraping and unauthorized automated contact downloads.

‍

Is it safe to collect information from a public LinkedIn profile?

Public visibility alone does not guarantee that a collection method or later use is permitted. Review platform terms, privacy requirements, the purpose, the fields collected, and the outreach rules that apply.

‍

Does ContactBook guarantee that LinkedIn contact extraction is compliant?

No such guarantee should be inferred. ContactBook can help save and organize contact details, but organizations remain responsible for their collection method, platform obligations, privacy compliance, and use of the information.

‍

What should former Proxycurl customers check in a replacement?

Check data provenance, access method, contractual permissions, privacy processes, refresh practices, export options, and continuity planning. Do not choose a replacement solely because its API returns similar fields.

‍

How should teams store approved LinkedIn contacts?

Keep them in an authorized contact system with a defined business purpose, owner, source, access group, verification date, and review rule. Avoid leaving relationship data in one employee's browser, spreadsheet, or personal phonebook.

‍

‍

‍

Final thoughts

Proxycurl's shutdown is not merely news about one API. It is a warning about contact workflows built on sources that teams do not understand and cannot control.

In 2026, responsible contact management begins before a record enters the database. Teams need to examine how information is collected, whether they may use it, which fields are necessary, and how the contact will be maintained.

ContactBook can help organize and share approved business contacts after collection. It should be one part of a documented process, not a substitute for platform review, privacy decisions, or legal advice.

‍

‍