Authorization

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

Close

Prerequisites

Close supports two authentication methods for its API: API Key (HTTP Basic Auth) and OAuth 2.0. API keys are best suited for server-side integrations, internal tools, and scripts. OAuth 2.0 is recommended for user-facing integrations where individual users authorize access on behalf of their own Close accounts.

Obtain a Close API Key

API keys in Close are per-organization and can be created and managed in your Close account settings.

1. Log in to your Close account at app.close.com.

2. Click Settings in the left-hand sidebar.

3. Under Settings, select Developer.

4. In the Developer section, click API Keys.

5. Click the Create New API Key button.

6. Enter a descriptive name for the key (for example, "Nexla Integration") and click Generate.

7. Copy the API key immediately after it is generated. For security reasons, the full key value will not be displayed again after you navigate away from this page.

Important

Store your API key securely. Anyone with access to this key can make API requests on behalf of your organization. If a key is compromised, delete it immediately from Settings > Developer > API Keys and generate a new one.

Additional information about API key management is available in the Close API Key documentation.

Set Up an OAuth 2.0 Application (OAuth 2.0 Method Only)

If you plan to authenticate using OAuth 2.0, you must first create an OAuth app in Close. OAuth 2.0 is recommended when your integration requires access on behalf of individual Close users.

1. Log in to your Close account at app.close.com.

2. Click Settings in the left-hand sidebar.

3. Under Settings, select Developer.

4. Click OAuth Apps, then click the Create App button.

5. Fill in the application form with the following details:

   • App Name: Enter a descriptive name for your integration (for example, "Nexla").
   • Redirect URI: Enter the callback URL for your integration. For Nexla, this is provided in the credential configuration overlay.
   • Description: Optionally, add a brief description of the app's purpose.

6. Click Save to create the app.

7. Copy the Client ID and Client Secret values displayed for your new app. Store the Client Secret securely — it will not be shown again.

Additional information about creating OAuth apps in Close is available in the Create OAuth Apps guide.

Create a Close Credential

• To create a new Close 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 Method

Close credentials in Nexla support two authentication methods: API Key and OAuth 2.0 (3-Legged). Select the method that matches your integration requirements.

Close Authentication Methods

API Key

Authenticate using an API key generated from your Close organization settings. This method uses HTTP Basic Auth with the API key as the username and an empty password. API keys are per-organization and are best suited for server-side integrations, internal tools, and automated scripts.

1. Enter your Close API key in the **API Key** field. This key authenticates Nexla with the Close API on behalf of your organization and should be kept secure. API keys can be generated in **Settings > Developer > API Keys** within your Close account.

OAuth 2.0 (3-Legged)

Authenticate using the OAuth 2.0 three-legged authorization flow, where a user grants Nexla permission to access their Close account. This method is recommended for user-facing integrations. You must first create an OAuth app in Close (Settings > Developer > OAuth Apps) to obtain a Client ID and Client Secret.

1. Enter the **Client ID** for your Close OAuth application in the **Client ID** field. This is the unique public identifier assigned to your OAuth app when it was created in **Settings > Developer > OAuth Apps**.
2. Enter the **Client Secret** for your Close OAuth application in the **Client Secret** field. This private key authenticates your application when requesting tokens and should be kept secure.
3. If your integration requires specific OAuth permission scopes, enter them as a space-separated list in the **Access Scope** field. Leave blank to request the default set of permissions for your application. For details about available scopes, refer to the [Close OAuth documentation](https://developer.close.com/topics/authentication-oauth2/).
4. Click the **Authorize** button to begin the OAuth authorization flow. You will be redirected to Close's authorization page, where you can grant Nexla access to your Close account. After authorization, you will be returned to Nexla and the credential will be configured with the resulting access token.

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.