Find Person API is one of our most robust APIs because it takes a person’s name and full address, or just the city and state, postal code, or state. So, you can do a search like:
As you can imagine, a search for Joe Smith in Washington will yield too many results. The exact count is part of the count_person response attribute. However, the actual person entities returned are limited to 100. The main reason is that the data should not be used for lead generation purposes. It can, however, be used for lead enrichment use cases.
For example, Find Person API helps lead enrichment by finding the right person using the name and location and appending additional information. However, we want to avoid someone using a common name or last name with a state-level search to get all the records for lead generation use cases. This is why we have a limit of 100 entities.
If the use case is specifically for lead enrichment and the limit of 100 records is not sufficient, we recommend the following:
- Alter the location to be more specific. If the full address is not available, a city should suffice. By default, Find Person API searches within a 25-mile radius to find the person of interest, so any additional information will not narrow down the search.
- For the name input, if there is a middle initial or middle name, add that too (e.g., name=Kushal J Shah).
- Of course, the lead might not be real, hence not found.
If these recommendations still do not help and your use case is one of lead verification or enrichment, contact us at firstname.lastname@example.org. We can work with you to appropriately adjust the query, depending on your needs.