FullContact

FullContact is a comprehensive identity resolution platform that provides enriched contact data, person-based insights, and identity verification services, enabling businesses to better understand their customers and improve engagement through accurate, up-to-date contact information.

Power end-to-end data operations for your FullContact API with Nexla. Our bi-directional FullContact connector is purpose-built for FullContact, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to FullContact or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your FullContact workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating a FullContact credential, you need to obtain an API key from your FullContact Developer Dashboard. The API key is required to authenticate with the FullContact API.

To obtain your API key, you need to have a FullContact account with API access enabled. Once you have access to your account, you can retrieve and manage your API keys from the FullContact Developer Dashboard. The API key is sent in the Authorization header with the Bearer prefix (e.g., Bearer {token}) for all API requests to the FullContact API. For detailed information about API key setup and authentication, refer to the FullContact API documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
API Key	Yes	Yes	Authenticating with the FullContact API is accomplished through the use of an API key. You can retrieve and manage your API keys from the Developer Dashboard.

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – FullContact

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter your FullContact API key in the API Key field. This is the API key you obtained from your FullContact Developer Dashboard. The API key is sent in the Authorization header with the Bearer prefix for all API requests to the FullContact API.

   Keep your API key secure and do not share it publicly. The API key provides access to your FullContact account and should be treated as sensitive information. You can retrieve and manage your API keys from the FullContact Developer Dashboard. The API key is sent in the Authorization header with the Bearer prefix for all API requests to the FullContact API. For detailed information about obtaining and managing API keys, see the FullContact API documentation.

4. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the FullContact connector tile, then select the credential that will be used to connect to the FullContact instance, and click Next; or, create a new FullContact credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common FullContact endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

Fetch Company by Domain Name

Fetch companies by submitting a domain name, which will then return information about the company.

• Enter the domain name of the company you want to fetch information for in the Domain Name field. This should be a valid domain name (e.g., example.com).

• The endpoint uses POST requests to https://api.fullcontact.com/v3/company.enrich with a JSON body containing the domain name. The endpoint URL is automatically constructed based on the FullContact API base URL.
• The endpoint does not use pagination and returns company information in a single request.
• The endpoint will return detailed information about the company associated with the specified domain name. The response data is extracted from the root-level object in the API response ($), and Nexla will process the entire response structure.

Domain names should be valid internet domain names without the protocol (e.g., example.com, not https://example.com). The endpoint uses a static URL (iteration.type: static.url) and does not require pagination. The response data path is $, which extracts the entire root-level object from the API response. For detailed information about company enrichment, see the FullContact API documentation.

Fetch Company by Domain Name from Lookup

Fetch companies by submitting domain names in a Nexla lookup table, which will then return information about the company.

• Select the Nexla lookup table that contains domain names from the Lookup for fetching Domain Names dropdown menu. This lookup table should contain a column with domain names that you want to fetch company information for.

• Enter the name of the column in the lookup table that contains the domain names in the Domain Name column name in Lookup field. This should match the exact column name in your lookup table.

• The endpoint uses a two-step process: first, it iterates over the Nexla lookup to retrieve domain names, then it makes POST requests to https://api.fullcontact.com/v3/company.enrich with a JSON body containing the domain name for each domain from the lookup. The endpoint URL is automatically constructed based on the FullContact API base URL.
• The endpoint does not use pagination and returns company information in a single request per domain.
• The endpoint will return detailed information about the companies associated with each domain name found in the lookup table. The response data is extracted from the root-level object in the API response ($), and Nexla will process the entire response structure for each company.

This endpoint requires a Nexla lookup table containing domain names. The endpoint iterates over the lookup table and makes API requests for each domain name found in the lookup. The Domain Name column name should match the exact column name in your lookup table. Domain names should be valid internet domain names without the protocol (e.g., example.com, not https://example.com). The endpoint uses a lookup iteration (iteration.type: data.map.key.queue) followed by a static URL (iteration.type: static.url) for each lookup entry. The response data path is $, which extracts the entire root-level object from the API response. For detailed information about company enrichment, see the FullContact API documentation.

Fetch Person by Email

Fetch person information by submitting an email address, which will then return information about the person.

• Enter the email address of the person you want to fetch information for in the Email Address field. This should be a valid email address (e.g., bart@fullcontact.com).

• The endpoint uses POST requests to https://api.fullcontact.com/v3/person.enrich with a JSON body containing the email address. The endpoint URL is automatically constructed based on the FullContact API base URL.
• The endpoint does not use pagination and returns person information in a single request.
• The endpoint will return detailed information about the person associated with the specified email address. The response data is extracted from the root-level object in the API response ($), and Nexla will process the entire response structure.

Email addresses should be valid email addresses in standard format (e.g., bart@fullcontact.com). The endpoint uses a static URL (iteration.type: static.url) and does not require pagination. The response data path is $, which extracts the entire root-level object from the API response. For detailed information about person enrichment, see the FullContact API documentation.

Fetch Person by Email from Lookup

Fetch person information by submitting email addresses in a Nexla lookup table, which will then return information about the person.

• Select the Nexla lookup table that contains email addresses from the Lookup for fetching Email Addresses dropdown menu. This lookup table should contain a column with email addresses that you want to fetch person information for.

• Enter the name of the column in the lookup table that contains the email addresses in the Email address column name in Lookup field. This should match the exact column name in your lookup table.

• The endpoint uses a two-step process: first, it iterates over the Nexla lookup to retrieve email addresses, then it makes POST requests to https://api.fullcontact.com/v3/person.enrich with a JSON body containing the email address for each email from the lookup. The endpoint URL is automatically constructed based on the FullContact API base URL.
• The endpoint does not use pagination and returns person information in a single request per email.
• The endpoint will return detailed information about the people associated with each email address found in the lookup table. The response data is extracted from the root-level object in the API response ($), and Nexla will process the entire response structure for each person.

This endpoint requires a Nexla lookup table containing email addresses. The endpoint iterates over the lookup table and makes API requests for each email address found in the lookup. The Email address column name should match the exact column name in your lookup table. Email addresses should be valid email addresses in standard format (e.g., bart@fullcontact.com). The endpoint uses a lookup iteration (iteration.type: data.map.key.queue) followed by a static URL (iteration.type: static.url) for each lookup entry. The response data path is $, which extracts the entire root-level object from the API response. For detailed information about person enrichment, see the FullContact API documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

FullContact data sources can also be manually configured to ingest data from any valid FullContact API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

FullContact API endpoints typically follow the pattern https://api.fullcontact.com/v3/{endpoint_path}. The endpoint requires API Key authentication via the Authorization: Bearer {token} header, which is handled automatically by your credential configuration. For detailed information about FullContact API endpoints and available APIs, see the FullContact API documentation.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new FullContact data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.