Skip to main content

Authorization

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

Chameleon

Prerequisites​

Before creating a Chameleon credential in Nexla, ensure that you have the following:

A Chameleon Account​

You need an active Chameleon account with administrator or developer access to your organization's dashboard. The Chameleon REST API operates against the account associated with the secret token you generate, so the data accessible through Nexla is determined by the account that issues the token.

A Chameleon API Secret Token​

Chameleon authenticates REST API requests using an account-specific secret token, which Nexla sends in the X-Account-Secret request header. This token is the server-side API Secret—it is distinct from the public Account Token that is embedded in your installation JavaScript snippet, and it should never be exposed in client-side code.

To generate your API Secret token:

  1. Sign in to your Chameleon Dashboard.

  2. Navigate to Settings > Tokens.

  3. Locate the API Secret (also referred to as your secret token), and generate a new token if one does not already exist.

  4. Copy the token value and store it securely.

    API Secret tokens are account-specific and can only be viewed or copied once at the time of generation. Save the token in a secure location immediately, as you will not be able to retrieve it again later.

Keep your API Secret confidential

Your API Secret grants full access to your Chameleon account data and Experiences. Treat it like a password—do not share it in publicly accessible locations such as client-side code, version control, or support tickets. If a token is exposed, regenerate it from the Settings > Tokens page.

For complete information about Chameleon API authentication, refer to the official Chameleon Authentication documentation.

Create a Chameleon Credential​

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

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​

Chameleon uses API key authentication. Nexla includes your API Secret token in the X-Account-Secret header of each request to the Chameleon REST API at https://api.chameleon.io.

  1. Enter your Chameleon API Secret token in the API Key field. This is the secret token generated from the Settings > Tokens page in your Chameleon Dashboard. This key authenticates Nexla with Chameleon and should be kept secure.

    The value entered here corresponds to the API Secret token, not the public Account Token used in your in-app JavaScript snippet. Using the public Account Token will result in authentication failures.

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.