Multi Field Request

With Verify, the ability to match on one or many input fields is available. Obtain signals on, match to and receive scores on individuals by sending any identifiers you may already have, such as an email address(es), Twitter handle, LinkedIn URL, phone number(s), name and location(address), name, social URLs, MAIDs, and more.

The more contact data inputs you can provide either via API or Batch, the more accurate and precise we can get with our identity resolution capabilities. If your Multi Field Request contains incomplete identifier combinations alongside valid inputs, the valid inputs only will be used to identify and resolve an individual. For example, if a name/address combination does not adhere to what is acceptable alongside a valid email, only the valid email will be used to lookup an individual.

📘

When providing inputs, there’s a few helpful tips to keep in mind:

• To use MD5 emails, be sure to first lowercase and ensure any extraneous characters (e.g. extra spaces or surrounding quotation marks) are stripped off.
• To use postal address, a name is required alongside the input and vise versa.
• To use Placekey, a name is required alongside the input and vise versa.
• Only one name/address (clear text postal or Placekey) combination can be included in the API request
• To use an international phone number, a country code is required.
• There is a maximum of 25 identifiers by type that you may use in your multi field request. A 400 Response will be returned if there are more than 25 identifiers for any given identifier type.

curl -X POST \
  https://api.fullcontact.com/v3/verify.signals \
  -H 'Authorization: Bearer {Your API Key}' \
  -H "Content-Type: application/json" \
  -d '{
  "emails": [
    "[email protected]",
    "[email protected]"
  ],
  "phones": [
    "+17202227799",
    "+13035551234"
  ],
  "location": {
    "addressLine1": "123 Main Street",
    "addressLine2": "Unit 2",
    "city": "Denver",
    "region": "Colorado",
    "regionCode": "CO",
    "postalCode": "80203"
  },
  "placekey": "[email protected]",
  "name": {
    "full": "Bart Lorang",
    "given": "Bart",
    "family": "Lorang"
  },
  "profiles": [{
    "service": "twitter",
    "username": "bartlorang"
    }, {
    "service": "twitter",
    "userid": "5998422"
    }, {
    "service": "linkedin",
    "url": "https://www.linkedin.com/in/bartlorang"
    }, {
    "service": "github",
    "url": "https://www.github.com/lorangb"
    }],
  "maids": ["ape2ch30-pifn-cbvi-30yy-nia-zex7aw5u"],
  "recordId": "customer123",
  "personId": "eYxWc0B-dKRxerTw_uQpxCssM_GyPaLErj0Eu3y2FrU6py1J",
  "li_nonid": "-CmQui5eT6tqBVqQ874WGCv4DNO_taXJOAxVlQ",
  "panoramaId": "294293d141c731300758a10feda14945c111e0abcd04c8208f09ff058781337b"
  }'

If you want to use location or name as an input, both must be present and they must have non-blank values for one of the following field combinations to be eligible for a positive match:

Acceptable minimum combinations for Location

Acceptable minimum combinations for Name

Person Summary Object

When enriching or subscribing to person contacts, Enrich returns a Person Summary object as well as details that include attributes about the person. The details section of the response will be populated based on the Insights Bundles that are enabled for the calling account.

Example Person Summary Object

{
  "fullName": "Bart Lorang",
  "ageRange": "30-39",
  "gender": "Male",
  "location": "Denver, CO, United States",
  "title": "Co-Founder & Managing Director",
  "organization": "V1.vc",
  "twitter": "https://twitter.com/bartlorang",
  "linkedin": "https://www.linkedin.com/in/bartlorang",
  "bio": "CEO & Co-Founder of @FullContact, Managing Director @v1vc_. Tech Entrepreneur, Investor. Husband to @parkerbenson and Father to Greyson Lorang",
  "avatar": "https://d2ojpxxtu63wzl.cloudfront.net/static/a7e6a5aba590d4933e35eaadabd97fd2_44e00e968ac57725a15b32f9ca714827aff8e4818d290cb0c611f2e2585253b3",
  "details": {...}
}

With the Person Summary object sent in the request, FullContact will attempt to enrich the
contact with as much information as available, helping to fill in any missing properties, and then returning the Person Summary. The properties that are returned with values during an enrichment or subscription are dependent upon the data available for the given contact.