Skip to content
ScrapeField
Get a key

Leaving Proxycurl

Proxycurl shut down on 4 July 2025 after LinkedIn sued it in January. If you are still looking for a replacement, here is how we compare.

ScrapeField compared with Proxycurl (2025)
ScrapeFieldProxycurl (2025)
StatusOperatingShut down 4 July 2025
Surfaces5 — LinkedIn is one of them, capped at a minority of revenueLinkedIn only
CredentialsWe never take yours, for any reasonn/a
RetentionCached for a stated time; no database of profilesHeld a large profile database

Checked 3 October 2026 against each vendor’s own pricing page. Rechecked quarterly — tell us if something here is out of date and we will fix it.

Migrating a profile lookup

// Proxycurl
const res = await fetch(
  "https://nubela.co/proxycurl/api/v2/linkedin?url=" + profileUrl,
  { headers: { Authorization: `Bearer ${key}` } },
);
const p = await res.json();

p.full_name
p.occupation
p.follower_count
p.city
// ScrapeField
const res = await fetch(
  `https://api.scrapefield.com/v1/linkedin/profile?url=${encodeURIComponent(profileUrl)}`,
  { headers: { Authorization: `Bearer ${key}` } },
);
const { data, meta } = await res.json();

data.full_name
data.headline
data.follower_count
data.location

The shape is close enough that most integrations are a rename. Three differences worth knowing before you start:

  • Everything is under data, with meta beside it carrying the request id, the credits charged and whether the answer came from cache.
  • Fields use LinkedIn’s own words: headline rather than occupation, and location as the profile prints it (“Berlin, Germany”) rather than split into parts.
  • A field we cannot see is null, never 0. And LinkedIn stops counting connections at 500, so connection_count is 500 for “500+” — we do not invent the rest.

Questions

How do I know you will not disappear too?

You do not, and anyone who tells you otherwise is selling. What we can tell you is the structure: LinkedIn is one of five surfaces and is capped at a minority of revenue, and we hold no stored corpus of people. The honest version is that a single-surface LinkedIn business is one lawsuit from zero, which is exactly why we are not one.

What about the fields Proxycurl had that you do not?

Experience, education and skills are on the profile. Anything we cannot get, we do not have and will not pretend to — if that breaks your use case, better to find out on this page than after you have integrated.

Try it before you decide

Every endpoint has a playground that runs against the live API with no key and no account — real routing, real validation, real errors. If the response shape does not fit your code, you will know in about a minute.

Open the docsSee the credit table