vs
JobsPipe vs Proxycurl.
Proxycurl was the developer-friendly LinkedIn profile and company enrichment API - and it has wound down. JobsPipe is a focused jobs-data API, so it is only an alternative for the hiring-data slice, not profile enrichment.
What Proxycurl is
Proxycurl, built by Nubela, was a developer-first enrichment API sourced largely from LinkedIn. Its core surfaces were person enrichment (resolve a LinkedIn profile URL or email to a person record), company enrichment (resolve a domain or company page to firmographics and headcount), and a jobs endpoint that returned a company's LinkedIn job listings. It was popular with developers because it was self-serve, credit-priced, and well-documented.
Proxycurl has wound down, leaving customers looking for alternatives. The product centered on LinkedIn-derived person and company profile data, so its closest replacements are other profile-enrichment vendors. JobsPipe does not rebuild that profile surface - it is honestly only an alternative for the jobs and hiring-data slice that some teams used Proxycurl's jobs endpoint for.
Historically credit-based and self-serve, priced per enrichment lookup with a small free trial of credits. With the product wound down, those plans are no longer a path forward and former customers are migrating off.
Developers who needed LinkedIn-derived person and company enrichment - sales tooling, CRM enrichment, recruiting and sourcing products, identity resolution. The narrow slice JobsPipe speaks to is teams who used Proxycurl's jobs endpoint for company job listings and hiring signals.
Where Proxycurl wins
- Person-level LinkedIn profile enrichment - resolving a profile URL to work history, skills, and contact data, which JobsPipe deliberately does not do.
- Company enrichment from LinkedIn - firmographics, headcount, and employee-count signals tied to a LinkedIn company page.
- Self-serve, credit-based developer experience while it operated - clean docs and fast integration for enrichment workflows.
Where JobsPipe wins
- It is still here and self-serve - API key in 30 seconds, free tier covers 5,000 requests/month, no sales call and no credit card.
- Jobs data is the product, not a LinkedIn-mirrored endpoint - every normalized posting (title, parsed compensation, resolved location, posted_at, full description, apply_url) across 30+ ATS and job-board sources, deduplicated.
- Upstream-ATS sourcing rather than LinkedIn scraping - cleaner legal posture and fewer of the access risks that came with a LinkedIn-derived product.
- Real-time webhooks on new postings and per-source scoping by ATS, so you can build hiring-signal triggers on the raw data yourself.
Side-by-side
| Axis | Proxycurl | JobsPipe |
|---|---|---|
| Status | Wound down - no longer a path forward | Active, self-serve |
| Primary product | LinkedIn profile and company enrichment | Jobs data and hiring-signal intent |
| Jobs coverage | LinkedIn job listings endpoint | First-class, source-attributed across 30+ sources |
| Profile enrichment | Yes, the core product | No, not a goal |
| Data source | Largely LinkedIn-derived | Upstream ATS and job boards |
| Pricing model | Credit-based per lookup | Flat-rate, scales by request tier |
| Real-time delivery | Pull-only endpoints | Webhooks on new postings |
When to pick which
You need LinkedIn person or company profile enrichment - and since Proxycurl has wound down, that means a different profile-data vendor, not JobsPipe. JobsPipe does not try to replace the profile-enrichment surface.
The part of Proxycurl you relied on was the jobs and hiring-data slice - company job listings or hiring signals. JobsPipe gives you that directly as raw, normalized, source-attributed postings to build your own product or signal on.
FAQ
Is JobsPipe a Proxycurl replacement?+
Only for the jobs and hiring-data slice. Proxycurl's core was LinkedIn profile and company enrichment, and JobsPipe does not rebuild that. If you used Proxycurl's jobs endpoint for company job listings or hiring signals, JobsPipe is a direct, cleaner replacement for that part.
Proxycurl shut down - what do I use for LinkedIn profile enrichment now?+
For person and company profile enrichment you will need another enrichment vendor (for example People Data Labs or a similar provider), not JobsPipe. We are honest about this: JobsPipe is jobs-data, not profile-data. We can only replace the jobs portion of what Proxycurl did.
Why is JobsPipe sourced from ATSs instead of LinkedIn like Proxycurl was?+
We go upstream to the ATS where each job was first posted (Workday, Greenhouse, Lever, Ashby, and dozens more) rather than mirroring LinkedIn. That gives a cleaner legal posture and avoids the access fragility that comes with a LinkedIn-derived product - part of why a LinkedIn-centric API can be hard to sustain.
Can I build hiring-intent signals from JobsPipe like I did with Proxycurl's jobs data?+
Yes - that is a core use case. You get every individual posting with timestamps and company attribution, so you can derive hiring-velocity and role-mix signals yourself, with full control over the methodology and a free tier to evaluate it on your own accounts.
Try JobsPipe free - 5,000 requests/month, every source we cover, no credit card.
Get a free API key
