Skip to main content

Authorization

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

Clazar

Prerequisites​

The Clazar connector authenticates using the OAuth2 client credentials flow (also known as the two-legged or server-to-server flow). In this flow, Nexla exchanges a Client ID and Client Secret for a short-lived access token, which is then used to authorize API requests. No interactive user sign-in is required, making this flow well suited for automated, machine-to-machine data integrations.

Before creating a credential, ensure that you have the following.

A Clazar Account with API Access​

You must have an active Clazar account with permission to manage API credentials. API access is configured within your Clazar workspace, and the ability to generate API keys is typically reserved for administrators. For complete details about Clazar's API capabilities, refer to the Clazar developer documentation.

A Clazar Client ID and Client Secret​

Nexla requires a Client ID and Client Secret to authenticate with the Clazar API. These credentials are generated from within the Clazar application.

  1. Sign in to your Clazar account at https://app.clazar.io.

  2. Open the Settings area of the application, and navigate to the API Keys (developer credentials) section.

  3. Click the option to create a new API key or credential.

  4. Provide a descriptive name for the credential (for example, "Nexla Integration") so that it can be easily identified later.

  5. Generate the credential. Clazar will display a Client ID and a Client Secret for the new key.

    Copy the Client Secret immediately and store it securely. For security reasons, Clazar does not display the secret again after the key is created. If the secret is lost, you must generate a new API key.

  6. Record both the Client ID and Client Secret for use when creating the Nexla credential below.

API keys grant access to your marketplace data, listings, contracts, and offers. Treat the Client Secret like a password, restrict access to authorized team members, and rotate keys periodically in accordance with your organization's security policies.

Create a Clazar Credential​

  • To create a new Clazar 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 to provide information about the resource purpose, data freshness, etc. that can help the owner and other users efficiently understand and utilize the resource.

Authentication Settings​

Clazar uses the OAuth2 client credentials flow to authenticate API requests. Provide the Client ID and Client Secret generated in your Clazar account to allow Nexla to obtain access tokens and exchange data with the Clazar API.

  1. Enter the Client ID generated in your Clazar account in the Client ID field. This is the unique public identifier assigned to your application and is used to identify Nexla to the Clazar API.

  2. Enter the Client Secret generated in your Clazar account in the Client Secret field. This is the confidential password provided alongside the Client ID and is used together with it to obtain an access token.

    The Client Secret is stored securely and is never displayed after the credential is saved. To update an expired or rotated secret, generate a new API key in Clazar and edit the credential with the new values.

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.