I am happy to share that you can now fetch fresh Search and Employee data from Enrich Layer.
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 user 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_ 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