Skip to main content

Authorization

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

6Sense

Prerequisites

Before creating a 6Sense credential, you need to obtain your API Token from your 6Sense account. 6Sense uses API Token authentication for all API requests, with the token sent in the Authorization header with the Token prefix.

To obtain your 6Sense API Token, follow these steps:

  1. Sign in to your 6Sense account using your administrator credentials.

  2. Navigate to your account settings or API management section in the 6Sense interface.

  3. Look for the API or API Tokens section in your account settings, or navigate to Settings > API or Account > API Tokens.

  4. If you don't have an API token yet, look for the option to generate or create your API token.

  5. Click Create API Token or Generate Token to create a new API token.

  6. Configure your API token settings:

    • Enter a name for the token (e.g., "Nexla Integration")
    • Review and select the permissions or scopes for the token (if applicable)
  7. Click Create or Generate to create the API token.

  8. Copy the API token immediately after it's generated, as it may not be accessible again after you navigate away from the page.

  9. Store the API token securely, as you will need it to configure your Nexla credential. The API token is sensitive information and should be kept confidential.

The API token is sent in the Authorization: Token {token} header for all API requests to the 6Sense API. The token authenticates your requests and grants access to 6Sense resources based on your account permissions. If your API token is compromised, you should immediately revoke it in your 6Sense account settings and generate a new one. For detailed information about obtaining API tokens, API authentication, and available endpoints, refer to the 6Sense API documentation.

Create a 6Sense Credential

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

New Credential Overlay – 6Sense

6SenseCred.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 Token Authentication

6Sense uses API Token authentication for all API requests. The API token is sent in the Authorization header with the Token prefix to authenticate API requests to the 6Sense API.

  1. Enter your 6Sense API Token in the API Token field. This is the API token you obtained from your 6Sense account settings (Settings > API or Account > API Tokens). The API token is sent in the Authorization: Token {token} header for all API requests to the 6Sense API. The API token is sensitive information and must be kept confidential.

    Your 6Sense API token can be found in your 6Sense account settings under Settings > API or Account > API Tokens. The API token is sent in the Authorization: Token {token} header for all API requests to the 6Sense API.

    If your API token is compromised, you should immediately revoke it in your 6Sense account settings and generate a new one. The API token provides access to your 6Sense account data and should be treated as sensitive information. Keep your API token secure and do not share it publicly.

    For detailed information about obtaining API tokens, API authentication, and available endpoints, see the 6Sense 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.