Feature Requests

Provide PDL users an avenue for pointing out data that is inaccurate in some way and a method improving data quality & coverage. Additionally, this would help the PDL team identify potential trends in data coverage earlier than otherwise would have been the case.

I would like a real-time API that can provide up-to-date information on LinkedIn profiles. This is important because the current data is not always accurate or up-to-date, which is a problem for us.

The need: Customers are asking for the ability to purchase endpoint agnostic API credits. Potential Solution: We give the customer a bank of neutral API credits and the power to allocate those credits to endpoints on their own at their discretion.

Have flags/options in Subject Request API (SR API) to limit API response and not receive the entire batch of opted-out records. For example, 1) subset=mine. Only send ID's in my DL or API subset. 2) release=x. Only send ID's opted out since that release date. release=17 would return opt-outs submitted since launch date of release 17. 3) use a date range. This way a customer can parse daily, weekly or whatever cadence fits their use case.

Allow clients to prioritize or surface to PDL the profiles (URLs) that they are interested in seeing refreshed. PDL would gather the data actively upon request and update them within 1-2 data releases.

Endpoint that using the more_like_this Elasticsearch functionality to return people similar to ones the customer is requesting based on some criterium they define

API to run aggregations against our hosted ES instance

Similar to Person Retrieve, it would be helpful to be able to only be charged for a response if a company has been updated since the last time it was retrieved from a company endpoint.

Allow customers to monitor for updates to fields that are not necessarily changed on a monthly basis like funding, talent flows, and recent exec hires/departures.