Ultimate Guide To All 21 Proxycurl APIs: Enrich People & Company Profiles

Ultimate Guide To All 21 Proxycurl APIs: Enrich People & Company Profiles

At Proxycurl, we pride ourselves with the many data enrichment APIs that we offer to our clients to power their applications. Not just the sheer number of it, but the quality of these APIs, in 8 in-depth features which will be covered in this post.

If you heard about us or stumbled upon us for the first time and are curious to find out more, this post will let you know all you need to know and more. Of course, we strive to convince you why our data scraping APIs are the best for your company. At the end of this, we will tell you how you can try out our APIs immediately to see for yourself, which you can straight away do a people search or company search relevant to your company.

However if you are not new here, you are already our beloved existing user or client, this post can serve as a reference of all we can offer you, or to answer some questions that you have regarding our products.

21 APIs That Scrape Profiles Of People, Company, Contact, Jobs

We have various APIs that draw primarily from LinkedIn and some other sources, and return all kinds of data, including the all-valuable contact information (email addresses, phone numbers), and company data such as funding & acquisition information. Either way, here is the full list of our API products and brief notes on what you can use them for, to get profile information and more.

Please find here for our API Documentation for further reference and API examples, including the actual python code samples and results. The following is a brief overview of all our 21 APIs.

Update: Proxycurl API has since been sunset. I am the founder behind Proxycurl, and I am now building NinjaPear. I am retaining this guide because the endpoint taxonomy is still useful for existing readers and for teams maintaining old integrations. Where relevant below, I have added NinjaPear equivalents or nearest alternatives. NinjaPear does not scrape LinkedIn, and gives you B2B data in a similar shape with none of the legal liability.

People Profile APIs

• Person Profile Endpoint - Get structured profile data like profile picture, job history, education, etc.
• Person Lookup Endpoint - Get individuals’ LinkedIn profile URL using their name and company
• Role Lookup Endpoint - Get individuals’ LinkedIn profile URL using their role and company
• Person Profile Picture Endpoint - Get individuals’ LinkedIn profile picture

Closest NinjaPear alternatives:

• Employee API - Person profile enrichment from public web sources, including work history, education, location, and social handles.
• Work Email Lookup - Find verified work email from name + company.
• Supportive for Gmail - Surface person and company profile data inside Gmail threads.

Company Profile APIs

• Company Profile Endpoint - Enrich company profiles with structured data like funding & investments data, locations, industries etc.
• Company Lookup Endpoint - Get a company’s profile URL using their name, website and/or location.
• Employee Search Endpoint - Get the profile URL of employees using their job title
• Employee Listing Endpoint - Get a list of past and present employees of a company
• Employee Count Endpoint - Get the number of employees in a company
• Company Profile Picture Endpoint - Get a company’s LinkedIn profile picture

Closest NinjaPear alternatives:

• Company API - Resolve company name to website, then pull company details, employee count, updates, funding, and logo.
• Company Details - Returns structured company intel including industry, executives, addresses, and public social links.
• Employee Count - Fresh headcount data via real-time web search.
• Company Logo API - Free logo endpoint for any domain.

Contact APIs, Emails & Contact Numbers

• Reverse Work Email Lookup Endpoint - Identify LinkedIn profile of an individual using their work email address
• Work Email Lookup Endpoint - Get work/professional email addresses of individuals using their LinkedIn profile
• Personal Email Lookup Endpoint - Get personal email addresses of individuals using their LinkedIn profile
• Personal Contact Number Lookup Endpoint - Get personal contact numbers of individuals using their LinkedIn profile
• Disposable Email Endpoint - Check and verify if an email address belongs to a disposable email service

Closest NinjaPear alternatives:

• Work Email Lookup - Verified work email lookup with clear credit costs.
• Disposable Email Checker - Free disposable email checking is part of the NinjaPear stack.
• NinjaPear does not position itself around scraping private contact details from LinkedIn profiles. Instead, it enriches from public web data and first-party sources, which is the entire point.

Job Profile APIs

• Job Profile Endpoint - Get structured data of a job profile information posted on LinkedIn including title, location, description, etc.
• Job Listing Endpoint - Get a list of jobs posted by a company on LinkedIn
• Job Listing Count Endpoint - Get a count of number of jobs posted by a company on LinkedIn

Closest NinjaPear alternatives:

• Company Updates and Monitor API - These do not mirror LinkedIn jobs directly, but they do track company activity across blogs, X, and website changes, which is often more actionable for GTM and competitive intelligence teams than raw job-post scraping.

School Profile APIs & More

• School Profile Endpoint - Get structured data & information of a school such as name, location, year founded, website, specialties etc
• Student Listing Endpoint - Get a list of students of a school or university
• Reveal Endpoint - Verify and identify the company profile of an IPV4 address’ owner

For these more specialized endpoints, NinjaPear does not currently provide a one-for-one replacement. The product direction is different now. Instead of building a bigger LinkedIn scraping surface area, NinjaPear is focused on company intelligence, people enrichment from public web sources, customer intelligence, competitor intelligence, and monitoring.

There you go, all our 21 APIs. On their own, some are already very popularly used as they return tons of data points, like the People Profile API and Company Profile API. With the other APIs, they can be used together on top of each other, think of them like Lego blocks, to return some more complex results, according to your application and business needs.

8 In-Depth Features of Our Data Enrichment APIs

Comprehensive & Well-Built APIs to Support Your Applications and Growth

1. Freshness Of API Data

Freshness is an important metric of any data, after all who will want to work based on stale and outdated data? Well, this is where at Proxycurl we give both parties the flexibility and freedom to choose the freshness of data they want from our API requests, specifically these two parameters:

• Profile data <= 29 days old

Even though the parameter is capped at 29 days old, and to some this might still be considered stale data, but on average 88% of the data is fetched in real time whilst the other 12% are cached profiles that we stored as they are frequently queried and popular profiles data. Thus in reality, the data and profile information you get could be much fresher than 29 days old, but definitely not exceeding it.

Because the API is scraping live while using this parameter, it might take 2-3 seconds to complete, not immediately.

• Profile data with no freshness guarantee

This parameter will fetch cached profiles from our LinkDB LinkedIn dataset, which contains more than 401M+ people and company profiles. If the requested profiles do not exist, the APIs will fetch them live. That said, Proxycurl LinkDB dataset is updated very regularly, as often as when there is an API request to scrape a particular profile, that profile will be updated in LinkDB. This keeps LinkDB freshly updated to up to millions of profiles daily. Thus in reality, while using this parameter does not guarantee freshness, the data and profile information returned will still have a high degree of freshness.

For the response time of this parameter, it returns data almost immediately. This is good if you need fast and immediate responses for your UI applications.

NinjaPear equivalent: the current NinjaPear stack takes a different approach. For example, Company Updates discovers and aggregates fresh company activity from blogs and X, while Employee Count returns fresh headcount via real-time web search. Different source model, better legal footing.

2. Huge Amount Of Data Points

Proxycurl APIs return a huge and comprehensive amount of data points, especially for the popular Person Profile API and Company Profile API, including the valuable contact information, skills data, companies funding and acquisition data, employees profile information and more. Here is the exhaustive list of data points returned for both of these APIs. Check out our API documentation for the full coverage.

• People Profile API

first and last name, profile picture, personal phone numbers, personal emails, work emails, occupation, work industry, Github, Facebook & Twitter profiles ID, LinkedIn profile headline & summary, country, city & state, work experience, education, languages, organizations, publications, honors & awards, patents, courses completed, projects, test scores, volunteer work, certifications, connections, activities, articles, groups, skills, inferred salary, gender, birth date, interests, related LinkedIn profiles, LinkedIn recommendations, profile follower count, similarly-name LinkedIn profiles, etc.

A whooping 45 data points on a person alone.

• Company Profile API

company name, description, website, tagline, profile picture, industry, categories, size, HQ & other locations (including country, city, state, street and postal code), company email, company phone number, Facebook & Twitter ID, company type, founded year & date, specialities, stock symbol, IPO status, Crunchbase rank, acquisitions & exits, funding rounds, funding amount, investors count, company LinkedIn updates, LinkedIn profile follower count, similar companies, etc.

A whooping 45 data points on one company alone.

There are many more with our other APIs, check out our full documentation for the rest of them. We scrape these data points from various sources, LinkedIn being a major source of course. We also work with external partners for data points that aren’t available on public profiles like skills data to enrich the profiles you need.

NinjaPear equivalent: if your real use case is not "give me the LinkedIn profile JSON exactly as-is" but rather "give me enough structured B2B data to score, route, enrich, and sell," NinjaPear is honestly the cleaner product direction now. Person Profile gives work history, education, location, social handles, and identity resolution from public web sources. Company Details gives you industry, founders/executives, addresses, employee count, and social links. Company Funding adds investor and funding round data. Same shape where it matters, better sources.

3. Rate Limit

Our rate limit is generally sufficient for each client. Mostly our users are not restricted by our rate limit, but rather the budget available to query huge amounts of API requests. Every account has a rate limit of 300 requests per minute, which equates to 432,000 API requests per day, or $4,320 budget per day minimally ($0.01/credit for each API request). This is a rate we employ based on the usage load of our clients, to ensure that each client is able to query API requests when they need and we are able to support it.

If the pre-set rate limit is still not enough for you, you can consider the Enterprise plan where we can customize the rate limit for your use case. Or for regular accounts, you can use the use_cache=if-present parameter to read data from cache and these requests will not be rate limited.

NinjaPear note: current NinjaPear docs state that paid API endpoints are generally limited to 50 requests per minute per product account, while the free Company Logo API supports 300 requests per minute. Different product, different economics, clearer boundaries.

4. Legal Compliance

This is arguably a critically important consideration, if not the most important, of any data sourcing efforts you embark on. Why? Because any misstep in the compliance of handling data will land you in hot trouble, potentially even crippling your company.

Personal data handling has become an increasingly important issue globally. At Proxycurl we make sure we, and of course our clients are fully-compliant with the major legal compliance standards, being CCPA and GDPR compliant, and in the process of being SOC 2 certified. We abide by the strict standards laid out by these regulations, have rigorous policies in place to safeguard users’ data and help you abide by these legal compliance too. So that you can focus on scaling your business, and let us worry about your data needs.

This section matters even more now than when I first wrote this piece. The whole reason NinjaPear exists is that I no longer want to build on top of LinkedIn scraping risk. NinjaPear does not scrape LinkedIn, and I wrote separately about why that matters: Is scraping LinkedIn legal in 2026?.

5. Size of Dataset

Majority of our APIs plumber for data from any country in the world, including our clients’ favorite APIs, People Profile API & Company Profile API that enrich profiles of people and companies. For some APIs, they are “limited” to certain countries including the US, Canada, UK, Singapore and many more. These APIs are powered by our LinkDB dataset, although restrictive, there are still a whooping more than 401 million people and companies profiles available globally. This size of dataset, I guarantee you, will give your company the necessary kickstart immediately, especially in lead generation, and allow you to scale up quicker than if without it.

For NinjaPear, the model is less about maintaining a giant LinkedIn-derived graph and more about building proprietary company intelligence primitives: customer data, competitor data, company updates, company details, people profiles from public sources, and similar people. Frankly, this is the better business. Less dependency, more defensibility.

6. API Success Rate & Accuracy

Data accuracy is one of the harder metrics to nail, yet a huge differentiating factor if done well. One major factor to this issue is the platform itself from which we scrape the data, for example LinkedIn, any changes to LinkedIn’s structure or data fields and we will need to adapt and keep up to them to ensure our APIs continue to work. And, if a particular profile doesn’t exist, or not accessible, then our APIs will return error, or return a closest-match profile.

A data type where accuracy is particularly important is the contact info, that is the whole purpose of getting contact information, to be able to actually contact the leads. Take an example, Proxycurl Work Email Lookup API has a match rate of more than 45% or 1 in 2 persons, whereas some other vendors might only have a low 13%, or in other words, only 1-2 out of 10 people are contactable from the emails returned by these vendors. Of these 45% of emails, Proxycurl guarantees a deliverability rate of a high 95%.

With NinjaPear, accuracy work shifts upstream. Instead of trying to keep up with LinkedIn HTML changes forever, the product pulls from public web sources and purpose-built pipelines. Less brittle. Also less exciting if you enjoy cat-and-mouse scraping games, which I no longer do.

7. Data From LinkedIn Public Profiles, Not Private

Many of our clients look for LinkedIn data given its wealth of data on people and companies there. On LinkedIn we only scrape for public profiles and not private profiles, as a result we don’t have some information directly from LinkedIn that are privy to private profiles such as skills, contact information, social media profiles etc. These “missing” data however we plumber for them via other channels, or in some cases we work with external parties.

It is difficult enough to scrape data from LinkedIn public profiles, to scrape private profiles is not just a mammoth task but a highly risky one, as you could land yourself in legal trouble with the Goliath which is LinkedIn. There’s a reason why they are "private" profiles, they are meant to stay private, and reserved only for other LinkedIn members who are connected to these profiles. Scraping illegally or erroneously for LinkedIn private profiles would mean eating into their money-making pie, and they definitely wouldn’t sit idly by.

This is exactly the part of the old model that NinjaPear leaves behind.

8. Pricing Model: Flexible & Scalable

Our pricing at Proxycurl offers tons of flexibility, all implemented from the feedback of our clients. The 2 pricing structures are: monthly subscription plans and pay-as-you-go model, based on credit purchase. If you are a regular user with consistent use of a certain volume of API calls, the monthly plans would give the highest value and predictable costs every month, from as low as $0.009/credit to $0.020/credit. If you are not a heavy user, or going for just a one-off usage, our pay-as-you-go plans give you the utmost flexibility depending purely on your usage, from as low as $0.018/credit or just $10 for the lowest purchase.

If you require really large volume monthly, we have an enterprise plan that offers volume discount with minimum commitment of 18 months with a contract. It starts from $2,000/month and the credits expire every month. This is ideal for companies that require huge amount of data and API requests regularly, it would give you the best value, and butler-like service from us.

Current NinjaPear pricing works differently: there is a 3-day free trial with 10 credits included, paid endpoints generally run on explicit credit costs, and pay-as-you-go credits are valid for 18 months. A few examples from the current pricing page:

• Person Profile: 3 credits / call
• Company Details: 3 credits / call
• Company Funding: 2 credits / call + 1 credit per unique investor
• Employee Search: 2 credits / call + 1 credit per employee returned
• Work Email Lookup: 2 credits when email is found, 0.5 credit on miss
• Company Logo, Disposable Email Check, Credit Balance, and several feed endpoints: free

That pricing is more explicit than the old world, which I like.

Get Started With Proxycurl APIs Today

That’s 8 in-depth features of our APIs for you. As powerful as they already are, you can pair up our other product, LinkDB to get even more for your business or applications. LinkDB is our exhaustive dataset of people and companies profiles with more than 401 million profiles for your use. Combining both products, for example, you can surface leads or profiles immediately from LinkDB, and then using our APIs you can enrich these profiles with structured data like contact info, work experience, etc.

That said, if you are reading this today, the practical next step is NinjaPear, not Proxycurl.

If your use case is:

• person enrichment, start with NinjaPear's Person Profile and Work Email endpoints
• company enrichment, start with Website Lookup, Company Details, Employee Count, and Funding
• monitoring accounts, use Company Updates or the Monitor API
• free utility endpoints, grab the Company Logo API and Disposable Email Checker

You can start at NinjaPear, read the docs, or go straight to the pricing page. If you just want to try something immediately, the free trial includes 10 credits and does not require a card.

We look forward to seeing you and talking to you. Meanwhile, check out our other resources and posts too.

Get free credits to try immediately.