Edges vs Proxycurl
Proxycurl went offline on July 4, 2025. Here is the LinkedIn Actions API that replaces it.
Proxycurl shut down on July 4, 2025.
Proxycurl, Nubela’s LinkedIn profile and company enrichment API, went fully offline on July 4, 2025. LinkedIn (Microsoft) sued Nubela in LinkedIn Corp. v. Nubela, alleging the product relied on scraping behind fake accounts. The service did not come back. Every integration still pointing at nubela.co/proxycurl is calling a dead host.
If your enrichment job, CRM mapping, or credit balance still depends on those person and company pulls, you need a replacement — not another vendor that collects data the same way. Price is not the deciding factor once the last one is gone. How the data is collected is.
A LinkedIn product that works by looking like a user, fetching the page, and parsing HTML inherits LinkedIn’s enforcement risk. That is the architecture the lawsuit described.
Edges is a LinkedIn Actions API — 70+ documented actions, structured JSON, SOC 2 Type II. You call an endpoint; we manage the session pool for reads. Messaging and engagement run on a seat you connect, not a farm of throwaway profiles. That does not make anyone immune to LinkedIn’s terms — you still own how you use the API — but it is a different product than the one that just disappeared.
Who this comparison is for
You still have Proxycurl-shaped enrichment in production — person and company lookups behind nubela.co — and the host stopped answering on July 4, 2025. You need a mapped replacement this week, not another scraper that will repeat the same legal story.
At a glance
The axes that matter when you’re picking between us.
| Topic | Edges | Proxycurl |
|---|---|---|
| Status (Aug 2026) | Live. 100+ customers, 99%+ uptime, 100M requests / month. | Offline since July 4, 2025. LinkedIn Corp. v. Nubela; service did not return. |
| Scope | 70+ LinkedIn actions: profiles, companies, signals, Sales Navigator, engagement. | Was profile and company enrichment only. Adjacent workflows required other tools. |
| Live latency | p50 1.2s · p99 2.4s on a profile extract. | Not applicable — the API is gone. |
| Pricing model | Usage-based credits from $39.99 down to $1.49 per 1,000 records. One balance across every action. | Per-credit by endpoint family. Plans are no longer sold. |
| Collection model | Action API. Reads on a managed session pool. Outreach on a seat you connect — not a fake-account farm. | The lawsuit alleged scraping behind fake LinkedIn accounts. That architecture is what enforcement targeted. |
| Compliance posture | SOC 2 Type II, DPA, dedicated security page, enterprise tier for regulated buyers. | Nubela is in litigation with LinkedIn/Microsoft. No remaining vendor review to run. |
| Sales Navigator | First-class: saved searches, lead lists, account lists, smart links via API. | Never shipped. There is no remaining Proxycurl path for Sales Navigator. |
Map your Proxycurl endpoints to Edges
Proxycurl’s catalog was a set of person and company lookup endpoints. Edges exposes the same jobs as named actions under POST /v1/actions/{slug}/run/live. Drop the Proxycurl base URL, keep the LinkedIn URL or company domain as input, and read a typed Profile or Company object back.
| Proxycurl endpoint | Job | Edges action |
|---|---|---|
| Person Profile · GET /api/v2/linkedin | Profile by LinkedIn URL | linkedin-extract-people |
| Company Profile · GET /api/linkedin/company | Company by URL or domain | linkedin-extract-company |
| Person Lookup | Resolve a person from name / company / identifier | linkedin-search-people → extract |
| Company Lookup | Resolve a company from domain or name | linkedin-extract-company |
| Employee Listing | People who work at a company | linkedin-search-company-employees |
| Role Lookup | Find a title at a given company | salesnavigator-search-people |
| Person Search | People search with filters | linkedin-search-people |
| Company Search | Company search with filters | linkedin-search-companies |
| Work / personal email lookup | Contact fields on a profile | linkedin-extract-contact |
| Profile picture | Image URL on the person record | linkedin-extract-people · profile_image_url |
Pick the right one
Choose Edges when
You need the person and company pulls Proxycurl used to serve, plus a path to Sales Navigator, signals, and engagement on the same REST API so you do not buy a second vendor in twelve months. SOC 2 Type II, p50 1.2s live reads, credits from $39.99 down to $1.49 per 1,000 records.
Consider Proxycurl when
You cannot. Proxycurl is fully offline as of July 4, 2025. Keep cached payloads only as a diff fixture while you dual-run Edges in staging — there is no remaining production path through Nubela.
Which replacement by role
The enrichment engineer, the AI SDR platform, and procurement are not replacing the same thing. Pick the path that matches the calls you actually still have.
- // enrichment / data engineering
Replace the person and company pulls
You had Proxycurl in the warehouse or CRM enrich job. Map GET /api/v2/linkedin and the company endpoint to linkedin-extract-people and linkedin-extract-company, diff against the last payloads you stored, cut over. This is the one-day path.
linkedin-extract-peoplelinkedin-extract-companylinkedin-extract-contact - // AI SDR / sales product
Do not buy another enrichment-only API
The next ticket after “get the profile” is always “watch for a job change” or “send the invite.” Proxycurl could not do those. Edges can, on the same key. If you replace Proxycurl with another point-lookup vendor you will run this search again in a year.
linkedin-extract-peoplesalesnavigator-search-peoplelinkedin-connect-profile - // recruiting / talent
Search and lists, not just a URL in
Role lookup and employee listing were the Proxycurl calls that felt closest to sourcing. On Edges those are first-class people and Sales Navigator searches — filters, cursors, typed rows — not a one-shot HTML parse.
linkedin-search-peoplesalesnavigator-search-peoplelinkedin-search-company-employees - // legal / procurement
Ask how the data is collected
The lawsuit was about fake accounts and scraping, not about JSON. Ask every remaining vendor whether they operate identities they do not own, whether they are SOC 2 Type II, and whether you can run a DPA. Price is the easy column; architecture is the one that just took Proxycurl off the internet.
SOC 2 Type IIDPA99%+ uptime
One-day migration checklist
Most enrichment-only stacks cut over in a day of engineering, then dual-run overnight. Adjacent work (Sales Navigator, signals, messaging) is new surface Proxycurl never had — schedule that as a second sprint, not as a blocker for the profile/company cutover.
- 01
Inventory the Proxycurl calls you still make
Grep for nubela.co, proxycurl, and the person/company endpoint paths. Note input shape (LinkedIn URL vs email vs domain) and the fields you actually persist. Ignore fields you stored and never read.
- 02
Map each call to an Edges action
Use the table above. Profile URL → linkedin-extract-people. Domain → linkedin-extract-company. Employee lists and role lookups usually become a search action plus an extract. Confirm credit cost per action in the library before you size the first invoice.
- 03
Get an API key and hit live in staging
POST /v1/actions/{slug}/run/live with X-API-Key. Same-day first call — no partner application, no OAuth dance with LinkedIn. p50 1.2s · p99 2.4s on a live read.
- 04
Diff fill rate on the fields you ship
Run a few hundred ICP profiles through both the last Proxycurl payloads you cached and Edges. Compare full_name, headline, job_title, company_name, location, experiences. Where a field name differs, write the mapping once.
- 05
Flip production traffic, then delete the dead client
Route new lookups to Edges. Keep the Proxycurl SDK in the repo only until you have proven parity on your critical fields — then remove it. There is no remaining production path through Nubela.
- 06
Only then add what Proxycurl could not do
Sales Navigator saved searches, scheduled extracts for job-change timing, and engagement run on the same key and credit balance. Do not block the enrichment cutover on those; they are the reason you will not need a second vendor in twelve months.
FAQ
Why did Proxycurl shut down?
LinkedIn (Microsoft) sued Nubela in LinkedIn Corp. v. Nubela, alleging Proxycurl scraped LinkedIn behind fake accounts. Proxycurl shut down on July 4, 2025 and did not come back. The public lesson is architectural: a LinkedIn data product whose collection model looks like “pretend to be a user, fetch the page, parse the HTML” inherits LinkedIn’s enforcement risk. Price is not the column that decided this.
Is Proxycurl still working?
No. The service has been fully offline since July 4, 2025. Calls to nubela.co/proxycurl do not return production data. If your logs still show Proxycurl requests, they are failing — migrate the person and company pulls; do not wait for a restart.
Will Edges get sued too?
Nobody who touches LinkedIn data can promise immunity from LinkedIn’s terms — including us. What we can say: Edges is an action API, not a fake-account scraper. Reads run on a managed session pool; messaging and engagement run on a seat you connect. We are SOC 2 Type II. You still own how you use the API and should run your own legal review. Edges is not related to LinkedIn and is not an official LinkedIn product.
Is Edges a drop-in replacement for Proxycurl’s person and company endpoints?
For the enrichment jobs, yes. GET /api/v2/linkedin (person profile) maps to linkedin-extract-people; the company profile endpoint maps to linkedin-extract-company; employee listing and role lookup become search actions. Input is still a LinkedIn URL or company domain; output is typed JSON. See the mapping table on this page and the library for credit cost per call.
How does Edges pricing compare to what Proxycurl used to charge?
Proxycurl priced per credit per endpoint family. Edges uses one credit balance across all 70+ actions, from $39.99 down to $1.49 per 1,000 records. A 50,000-profile month sits in the $15.99 per 1,000 band — about $800 before identity fees — and Sales Navigator or signals share that balance instead of adding a second vendor. Model it on the pricing page before you commit.
Does Edges support Sales Navigator?
Yes. Saved searches, lead lists, account lists, and smart links are first-class actions — coverage Proxycurl never shipped. Older articles that said “skip the official API, use Proxycurl” are out of date: Proxycurl is gone. See /sales-navigator-api.
How long does a migration from Proxycurl to Edges take?
Enrichment-only stacks often cut over in a day: inventory the remaining Proxycurl calls, map them to Edges actions, hit live in staging, diff fill rate on the fields you persist, flip production. Use cached Proxycurl payloads as the diff fixture — you cannot dual-run against a live Nubela host anymore. Adjacent work (Sales Nav, signals, messaging) is a second sprint, not a blocker.
Can we run Proxycurl and Edges in parallel during migration?
Not against a live Proxycurl API — it is offline. Parallel means: keep the last payloads you stored, route new lookups to Edges, and compare field fill on your ICP. Once parity is proven, delete the Nubela client. There is no remaining reason to keep the SDK.
Where are the API docs?
docs.edges.run — OpenAPI spec, authentication, TypeScript/Python/Go samples, and the actions catalog with credit costs per call. The mapping table on this page is the shortest path from a Proxycurl endpoint name to an Edges action slug.
Build on Edges
Credits-based pricing, SOC 2 Type II, and a growing catalog of LinkedIn actions — see Pricing and Enterprise for scale.
// go deeper
// other comparisons
Edges is not related to LinkedIn and is not an official LinkedIn product.