FAQs - Identify API
Miscellaneous (but useful) information on the Person Identify API
Have a question you want answered? Ask us!
You can either use the
Suggest Editsbutton in the top right hand corner of this page to ask a question or post your question in our Discussion Board.
What's the difference between the Person Enrichment API, Person Search, Person Retrieve and Identify API?
We have multiple Person-related API's so how are they all different? A quick one-sentence summary of each endpoint is as follows:
Person Retrieve: Directly lookup a specific profile using its PDL ID.
Person Enrichment: Find the single best profile matching some attributes about a particular person
Identify: Find the best selection of profiles associated with a particular set of attributes for a person or related persons
Person Search: Find all the profiles for any number of persons that satisfy some search criteria
Here's a nice table to summarize some of the key differences as well:
| Person Retrieve | Person Enrichment | Person Identify | Person Search | |
|---|---|---|---|---|
| Matching Type | 1:1 | 1:1 | 1:Many | 1:Many |
| Input Cleaning | No | Yes | Yes | No |
| Supported Query Parameters | None - direct profile lookup by ID | Only supported inputs which must be uniquely identifying | Only supported inputs, which do not need to be uniquely identifying | Anything in Person Schema |
| Number of Profiles per Unique Query | 1 | 1 | Up to 20 | No limit |
| Sorting of Returned Profiles | N/A - only 1 profile is returned | N/A - only 1 profile is returned | Sorted by match score | Sorted by profile completeness |
The key takeaway here is that the Identify API sits between our Enrichment and Search API in terms of functionality.
Compared to the Person Enrichment API which returns a single record for a single person, the Identify API supports broader search inputs returning multiple strongly-related profiles. This means the Identify API is ideal for situations where you do not have enough information to uniquely resolve a person and are interested in recovering highly probable candidates, whereas the Person Enrichment API is better suited to targeted enrichment when you have enough uniquely identifying information.
Compared to the Person Search API, the Identify API has standardized input parameters and provides a match score for each returned profile. This means you can use the Identify API to recover a focused selection of highly related profiles, unlike the Person Search API which will return a potentially large demographic cross-section of our person dataset with more loosely related profiles.
Updated 17 days ago