Client support
Postal-address inputs are not yet accepted by the Python SDK. Use the REST API
or MCP tool for address matching.
Choose a lookup shape
Each record must satisfy one of these lookup shapes:
If a record contains a
minerva_pid, it takes precedence over all other lookup
fields. A linkedin_url is used as the direct identifier only when no
minerva_pid is present. Any additional fields are still validated and must
belong to the same person.
Person matching
Provide either afull_name containing a first and last name, or both
first_name and last_name. Include every accurate email, phone, and address
available; more evidence can improve match confidence.
Addresses and phones
An address can be supplied asfull_address, or as parsed fields. Parsed
addresses require address_line_1 plus either zipcode or both city and
state. Do not mix full_address with parsed address fields. Phones must be
10-digit US numbers, optionally formatted with the +1 country code.
Matching and returned fields
match_condition_fields is a quality gate: it filters a resolved match based
on fields present in the resulting profile. It does not replace the identifying
information above.
return_fields only controls which enrichment fields are returned. It does not
affect how a person is identified.