FullContact Platform

Multi Field Request

With Enrich, the ability to match on one or many input fields is available. Lookup and enrich 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 and Placekey identifier, social URLs, IDs and/or usernames (except Facebook and Instagram), Mobile Advertising IDs (MAIDs) and most recently released as acceptable inputs customer record IDs and person IDs using Resolve API. These identifiers will then be used to locate and return any additional information we may have within the Insights Bundles enabled for your account.

The more contact data inputs you can provide either via API or Batch, the better. By providing more contact inputs, 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 enrich 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 vice versa.
• To use Placekey, a name is required alongside the input and vice 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.

Example API Request

curl -X POST \
  https://api.fullcontact.com/v3/person.enrich \
  -H 'Authorization: Bearer {Your API Key}' \
  -H "Content-Type: application/json" \
  -d '{
  "emails": [\
    "bart@fullcontact.com",\
    "bart.lorang@fullcontact.com"\
  ],
  "phones": [\
    "+17202227799",\
    "+13035551234"\
  ],
  "location": {
    "addressLine1": "123 Main Street",
    "addressLine2": "Unit 2",
    "city": "Denver",
    "region": "Colorado",
    "regionCode": "CO",
    "postalCode": "80203"
  },
  "placekey": "226@5z4-zvy-ffz",
  "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"
}'

Input Fields

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 response will be populated based upon the Insights Bundles that are enabled.

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": {...}
}