Feature Requests

Some customers want to buy different quantities of matches by bundle. For example, 100K of company base verses 50K of company comprehensive bundles. Also, in person, 2mm of M & A and 100K of premium resume.

Provide a flag for phone numbers that are on the "do not call list". A competitor to PDL already offers this.

Nice to have since a 4xx code is supposed to indicate an error on the client's end. Tools like CloudWatch report this as an error. If a request is good but we don't have data to return, it is best to return a 204 (No Content) error code instead of a 404 (Not Found). https://httpstatuses.com/204 https://httpstatuses.com/404 Same is true for Opt-outs. Out-outs in Retrieve API as 404 is confusing. Nice to have it's own unique code as 20x or 4xx for Opt-outs. Further, a no-match with a Retrieve API due to filter_updated flag should have a different code than 404/204. Currently, there is not way to distinguish between: a) no such record in PDL system (a true no-match); b) we have a match but not with your filter flags; c) an opt-out (on retrieve) d) a real HTTP 404 error. **ADDITION on 1.26.24: We should also have: +206 code for we have a match in our system but your required parameters caused a no-match. +207 for Opted-Out

I would like a feature that can provide work history overlap information as part of your API calls. This would help us generate referrals based on overlapping work histories.

Add an input parameter to allow for X number of responses to be returned when making matches in the Enrichment APIs.

customers who use Person Preview Enrichment API need a Bulk Person Preview API to prevent 429 errors.

PE API flag (such as match_on_new) that prevents a match when there is no net new information for specified fields. For example, match_on_new=email and a search input of john.doe@gmail.com would prevent a match if the only email in the array was john.doe@gmail.com .

It would be helpful to limit 200 responses from the Person Enrichment API past the top-level field for required parameters. For example: required: location_country='canada'

A match to the profiles array should have lower likelihood score than a match to the top level profile field such as linkedin_url.

Flag in the profiles array indicating if a social profile is the social profile of a person or that of a company. Customer only has the social profile URL but no other information on whether it's a person or company URL