No results found.
Log In
No results found.

Multi Field Request

curl -X POST \
  https://api.fullcontact.com/v3/permission.create \
  -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" : [ "adkkjre" , "alkdjfakd" ]
}'

Using FullContact Consent, the ability to read, match, store and manage consent using one or many input fields is available.

Possible identifier combinations include one or many of the following:

  • Mobile ad identifiers (MAIDs)
  • Email address(es);
  • Twitter handle;
  • Linkedin URL;
  • Phone number(s);
  • Name and location(address);
  • Name and Placekey;
  • Social URLs, IDs and/or usernames (except Facebook and Instagram)
  • NonIDs

These identifiers will then be stored within a private database such that you can lookup any individual using any identifier previously provided in order to locate and return any/all consent information about the requested individual.

Input Fields
maids list Queryable One or many mobile ad identifiers of the contact.
email string Queryable One email addresses of the contact. Can accept cleartext, an MD5 or SHA-256 hash representation of the email address to query. Be certain to lowercase and trim the email address prior to hashing. There is a limit of 10 hashed emails.
emails array Queryable One or many email addresses of the contact. Can accept cleartext, an MD5 or SHA-256 hash representation of the email address to query. Be certain to lowercase and trim the email address prior to hashing.
phone string Queryable Phone number of the contact. For international numbers a country code is required.
phones array Queryable One or many phone numbers of the contact. For international numbers a country code is required.
profiles object Queryable URLs, IDs and usernames to the profiles on the social platform.
name.full string Queryable Full name of the contact (givenName, familyName). Only queryable when provided in conjunction with postal address.
name.given string Queryable The given name (first name) of the individual. Only queryable when provided in conjunction with postal address.
name.family string Queryable The family name (last name) of the individual. Only queryable when provided in conjunction with postal address.
location.addressLine1 string Queryable The first address line for each location. Only queryable when provided in conjunction with name.
location.addressLine2 string Queryable The second address line for each location. Only queryable when provided in conjunction with name.
location.city string Queryable The city of each location. Only queryable when provided in conjunction with name.
location.region string Queryable The region of each location. This is often the state or province. Only queryable when provided in conjunction with name.
location.regionCode string Queryable The region code of each location. Only queryable when provided in conjunction with name.
location.postalCode string Queryable The postal or ZIP code for each location. Can accept Zip + 4 or Zip. Only queryable when provided in conjunction with name..
placekey string Queryable The universal standard identifier for any physical place. Only queryable when provided in conjunction with name.
li_nonid string Queryable The LiveIntent pre-authenticated digital nonID.