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 of 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 all fresh (related reading: How often is LinkDB updated?).

With this revamp we will scrape the results real-time and return fresh data, if they are not already 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.

Happy searching

We recognized the importance the fresh data returned for API calls involving searches, because who would want to search for and get stale data returned?

I hope this revamp will give you more powers through Proxycurl API, and thus more success in what you're building.

As always, email us at hello@nubela.co if you've any questions, or drop us a text in the live chat.