Fresh Data Is Here for Person, Company & Employee Search API Endpoints

I am happy to share that you can now fetch fresh Search and Employee data from Proxycurl.

Since the Search API revamp that happened earlier this year, we've had many of our customers using the product and giving us valuable feedback, along with two of our existing products that are related to this update: the Employee Listing Endpoint and Employee Search Endpoint.

And one recurring feedback is that it'd be good if users can decide the data freshness themselves.

And as always, we heard and we improved the products.

I'm glad to share that you can now use the same use_cache parameter, the same one as our Person Profile Endpoint, to determine the freshness of data returned.

What's our current state?

Currently the API endpoints are powered by LinkDB, our database of close to 500 million public LinkedIn profiles, i.e. when an API call is made, we sieve through the database and return the data from it.

However LinkDB is not always fresh, and thus results returned by these endpoints might not be fresh all the time (related reading: How often is LinkDB updated?).

With this revamp we will scrape the results in real time and return fresh data, if they are not already fresh yet, and if you use the use_cache=if-recent parameter (next section).

So what are the new updates?

Usage

Using the use_cache parameter,

• if-present (default value): returns results without any freshness guarantee
• if-recent: will make a best effort to return results of profiles <=29 days

For the use_cache=if-recent parameter, page_size value of your API call must not be more than 10. If it is >10, it'll return a 400 error.

Credit cost

The default value, use_cache=if-present, will not consume any extra credit.

The use_cache=if-recent parameter is a premium parameter and will cost additional credits.

• Good news is if you're on a Growth plan or larger, it costs only 1 extra credit.
• If you're not on the Growth plan or larger, it'll cost 2 extra credits.

Don't worry about invalid profiles because we won't charge credits for those.

A quick 2026 note on Proxycurl

Proxycurl has since been sunset. I was the founder behind Proxycurl, and I am now building NinjaPear. I am leaving this post up because the product update was real and useful at the time, but if you're building something new today, you should be looking at NinjaPear instead.

NinjaPear does not scrape LinkedIn. It pulls B2B data from public web sources and first-party infrastructure, which gives you data that is richer in many cases, in a similar JSON-first shape, without the same legal liability that comes with LinkedIn-dependent systems.

What to use now instead

If you came here looking for the old Proxycurl Search, Employee, Person, or Company workflows, NinjaPear is the modern replacement path.

For person and employee enrichment, start with Employee API endpoints on NinjaPear. The closest equivalent is the Person Profile endpoint, which returns work history, education, location, and social handles from public sources.

For company lookups, the Company API gives you:

• Website Lookup
• Company Details
• Employee Count
• Company Updates
• Company Funding
• Company Logo

If your old use case was search plus enrichment, the practical NinjaPear flow is:

1. Resolve a company name to a website with Company Website Lookup.
2. Pull company details or employee count.
3. Enrich a person with Person Profile or find a verified work email.
4. Monitor the company for fresh updates if timing matters.

That last part matters a lot more than most people think. Back when I was building Proxycurl, a lot of demand for "fresh profile data" was really demand for fresh buying signals. NinjaPear leans into that directly with company updates, employee count, funding, customer, and competitor data.

Happy searching

We recognized the importance of fresh data returned for API calls involving searches, because nobody wants to search and get stale data back.

I hope this revamp gave users more power through Proxycurl API at the time, and if you're building now, I think NinjaPear is the better path forward.

As always, if you've any questions, email us at [email protected] or drop us a text in the live chat.