Skip to main content

Authorization

Follow this guide to create a new FullContact credential that will allow Nexla to authenticate to and exchange data with your FullContact account.
fullcontact_api_auth.png

FullContact

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.

Create a FullContact Credential​

  • To create a new FullContact credential, after selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – FullContact

FullContactCred.png

Credential Name & Description​

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

    Resource descriptions are recommended but are not required. They should be used provide information about the resource purpose, data freshness, etc. that can help the owner and other users efficiently understand and utilize the resource.

API Key Authentication​

  1. 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.

Save the Credential​

  1. Once all of the relevant steps in the above sections have been completed, click the Save button at the bottom of the overlay to save the configured credential.

  2. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation and can be selected for use with a new data source or destination.