Getting Started with Identity Streme

Step 1: If you already have an account, start by logging in. If you don’t have an account, start by creating one in the FullContact Platform.

Doing so will allow you to access the FullContact Platform, which has some helpful tools to get started interacting with FullContact’s services, which you can read more about in the FullContact Platform Overview. Additionally, having an account will allow you to generate an API Key, which is required to interact with our APIs.

Navigate to the “API Keys” menu and click “GENERATE NEW API KEY”. Follow the prompt, giving your API key a name.

Note: Copy your API key and store it somewhere secure. You will not be able to see the whole key again. No longer have access to the full key? Don’t worry! You can generate a new one using the same process.

Be sure to keep this key secure and only share through secure and appropriate channels when necessary. If someone gains access to your API key, they will be able to incur unwanted charges against your account. You can delete keys at any time should you accidentally expose them to the world.

Step 2: Now that you have generated your API key, let’s resolve a person via the API. In this step, we will be sending data to the FullContact in the form of a multi-field identifier.

A Simple Resolve

In this step, contact identifiers were sent to FullContact. In this particular case, we provided all of Bart's known emails to FullContact's API, which was able to locate Bart in our Identity Graph, generate a unique personID and assign it to the calling account.

curl -X POST \
    https://api.fullcontact.com/v3/identity.resolve \
    -H 'Authorization: Bearer {Your API Key}' \
    -H 'Content-Type: application/json' \
    -d '{
    "emails": [
        "[email protected]",
        "[email protected]"
        ]
    }'

{
    "personIds": [
        "eYxWc0B-dKRxerTw_uQpxCssM_GyPaLErj0Eu3y2FrU6py1J"
    ]
}

Now let’s try to map a custom identifier, known as a recordID, to a lookup input record. Again we’ll provide a multi field identifier as well as a recordID we’d like to associate with our input record. Any further interactions with FullContact services can reference the recordID in lieu of contact fragments.

A Simple Map

curl -X POST \
  https://api.fullcontact.com/v3/identity.map \
  -H 'Authorization: Bearer {Your API Key}' \
  -H 'Content-Type: application/json' \
  -d '{
    "emails": [
      "[email protected]",
      "[email protected]"
    ],
    "recordId": "customer123"
  }'

{
   "recordIds": [
       "customer123"
   ]
}

Step 3: Fetch additional insights with either new identifier.
Once the PersonID and/or RecordID have been mapped to the person's multi field input record, they can be used to enrich the profile further with Insights Bundles.

NOTE: When a personID/recordID is generated with anonymous information (MAID, Hashed Email, etc.), only anonymous data can be returned in the Insights Bundles associated with your account.

curl -X POST \
  https://api.fullcontact.com/v3/person.enrich \
  -H 'Authorization: Bearer {Your API Key}' \
  -H 'Content-Type: application/json' \
  -d '{"personId": “eYxWc0B-dKRxerTw_uQpxCssM_GyPaLErj0Eu3y2FrU6py1J”}'

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

curl -X POST \
  https://api.fullcontact.com/v3/person.enrich \
  -H 'Authorization: Bearer {Your API Key}' \
  -H 'Content-Type: application/json' \
  -d '{"recordId": "customer123"}'

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

Step 4: Next Steps with Resolve

Jump into the Resolve a Customer Record API call to see an example with more potential inputs, or check out one of our libraries below.

Client Libraries

Client Libraries have been written for FullContact’s Enrich & Resolve APIs in GO, Java 8, Java 11+ and Python.

Customers can streamline the use of our Enrich & Resolve APIs by utilizing basic parts of our code, reducing the amount of code needed to write and enable within your products and solutions in order to effectively and efficiently utilize each API.

Our libraries are available in the following languages:

Prefer batch data uploads? Please Reach out to a sales representative to learn more. Alternatively, check out the Identity Streme Bulk Load Recipe!