This week, I am happy to come to you with updates on a new API endpoint and further refinements to Proxycurl API.
Introducing Employee Search API Endpoint
You can now search for Employees of any target company with the Employee Search API Endpoint. This new API endpoint is a good way, for example, to list all software engineers working at Apple.
Click here to see the API documentation for the Employee Search API Endpoint.
Reveal API will no longer charge credits for residential IP addresses
Most visits to your website are IP addresses from residential networks. The biggest complaint we got from customers was that most queries returned an empty response. That is because this traffic is coming from a residential network, and there is no way we can discern the employer of this individual behind the home or mobile IP.
With the latest update, Reveal API will no longer charge credits if you are querying an IP address that belongs to a residential network. So give Reveal API a try and uncover the businesses visiting your website!
Improved results for Company and Person Lookup Endpoint
Previously, customers have said that when our Lookup endpoints are wrong, they look so blatantly wrong that it makes no sense for us to return them. With this update, we added heuristics to significantly reduce the rate of false positives for both the Person and the Company Lookup Endpoints.
On top of that, we significantly improved Company Lookups by domains. Our internal test showed that the domain lookup tuning resulted in a 66% improvement.
We added profile enrichment to Employee Listing Endpoint.
I often get feedback that the two-step process to fetch and enrich employees first via our Employee Listing Endpoint and then enrichment via the Person Profile Endpoint is very cumbersome. For example, to fetch full profiles of employees of a company with 1000 employees would mean that our customer needs to make 1001 API calls.
I am happy to share that we added inline profile enrichment within Employee Listing Endpoint. You can get a list of full profiles instead of LinkedIn Profile URLs by adding the enrich_profiles=enrich parameter to the Employee Listing Endpoint today.
Check out the API documentation for the Employee Listing Endpoint for more information.
There is a lot more to come. Follow us on Twitter for API status and improvement updates if you have not done so already!