We have received feedback that the Employee Listing Endpoint leans towards being a little obtuse in how it can be used to solve problems. For example, the following steps are what you need to identify Software Engineers working at Apple with Proxycurl today:
- Call Employee Listing Endpoint, which would cost ~300K credits, or ~$3000.
- Make ~300K calls to our Person Profile Endpoint to enrich the profile IDs returned in step 1. Which would cost another ~300K credits or ~$3000.
- Identify the software engineers out of 100k enriched profiles.
I concede that the current method is too cumbersome, and some changes have been made to make this more efficient.
You can now paginate through the API results with the
page_size parameter instead of returning all past and/or present employees.
By adding the
page_size parameter, you will limit the total results (and maximum cost) of the Employee Listing API call.
You can now search for employees that match a particular role by appending the
role_search parameter to the Employee Listing endpoint.
Check out the new parameters in the Employee Listing API Endpoint API documentation.