Proxycurl has shut down, leaving teams that relied on it for LinkedIn profile and company data without a maintained API. Captain Data is a direct alternative for that data: pass a LinkedIn URL, a name, or a domain to a versioned REST API and get back fresh, structured people and company profiles as JSON. This guide maps every Proxycurl endpoint to its Captain Data equivalent and walks through migrating your code. One thing to know up front: Captain Data returns profile and firmographic data — not email or phone.
#Why Proxycurl shut down
Proxycurl (operated by Nubela) wound down and publicly announced its shutdown. For anyone running Proxycurl in production, the question is no longer whether to migrate but where to — to a maintained, compliant data provider that won't disappear mid-integration.
#What Captain Data replaces — and what it doesn't
Captain Data covers Proxycurl's core people- and company-data endpoints — profile enrichment, search, resolve/lookup, and employee listing — in real time, from 750M+ profiles. What it does not do is return personal or work email addresses or phone numbers. If your Proxycurl usage depended on the Contact API or email/phone lookups, keep Captain Data for profile and firmographic data and pair it with a dedicated contact-data provider for that piece.
#Endpoint mapping: Proxycurl → Captain Data
Here is how each Proxycurl endpoint maps to a Captain Data equivalent:
- Person Profile → People Enrichment (POST /v1/people/enrich): a LinkedIn profile URL returns a structured profile — name, headline, role, company, experiences, education, skills.
- Company Profile → Company Enrichment (POST /v1/companies/enrich): a LinkedIn company URL or domain returns firmographics — industry, headcount, HQ, funding, locations.
- Person Search → People Search (POST /v1/people/search): find people with Sales-Navigator-compatible filters (title, company, location).
- Company Search → Company Search (POST /v1/companies/search): find companies by industry, size, location, and keywords.
- Person Lookup (resolve) → Find People (POST /v1/people/find): resolve a person by full name and optional company to their LinkedIn URL and a stable uid.
- Company Lookup (resolve by domain/name) → Find Company (POST /v1/companies/find): resolve a company to its LinkedIn URL and uid.
- Employee Listing / Employee Search → Find Employees (GET /v1/companies/{uid}/employees): list employees at a company with name, title, location, and profile URL.
- Contact API / email & phone lookups → not offered by Captain Data. It focuses on profile and firmographic data; use a dedicated contact-data provider for emails and phone numbers.
#How to migrate in four steps
- Get an API key. Create a Captain Data key and start with 100 free credits — no card required. Explore the endpoints.
- Swap the base URL and auth. Point requests at the Captain Data endpoints and send your API key in place of Proxycurl's auth header.
- Map the fields. Align your response parsing to Captain Data's JSON using the endpoint mapping above — most profile and company fields have direct equivalents.
- Test and roll out. Validate on a sample, then update pagination and credit handling (enrichment 1 credit, resolve 2, search 1 request + 1 per result) before cutting over.
#Frequently asked questions
Is Proxycurl still available?
No. Proxycurl has shut down and no longer serves customers, so existing integrations need to migrate to a maintained provider.
What is the best Proxycurl alternative?
For profile and company data through a versioned REST API, Captain Data is a direct alternative — real-time enrichment, search, resolve, and employee listing from 750M+ profiles. See the full Captain Data vs Proxycurl comparison.
Does Captain Data return emails or phone numbers like Proxycurl's contact endpoints?
No. Captain Data provides profile and firmographic data — not personal or work email addresses or phone numbers. For contact data, pair it with a dedicated provider.
How much does it cost to migrate?
You can start free with 100 credits. Pricing is usage-based (enrichment 1 credit, resolve 2, search 1 request + 1 per result), so you can validate the migration before committing to volume.
Ready to migrate? Get an API key and see the full Captain Data vs Proxycurl comparison.