Skip to main content

Authorization

Follow this guide to create a new ContractPodAi - Leah CLM credential that will allow Nexla to authenticate to and exchange data with your Leah CLM tenant.
contractpodai_api_auth.png

ContractPodAi - Leah CLM

Prerequisites​

Leah CLM (formerly ContractPodAi) uses Bearer token authentication for its REST API. Before creating a credential in Nexla, you will need two pieces of information from your Leah CLM tenant:

  1. Your tenant Base URL — the root URL of your Leah CLM cloud instance, for example https://yourcompany-cloud.contractpod.com. This URL is unique to your organization and can be found in your browser's address bar when you log in to your Leah CLM account.

  2. An API Bearer Token — a secure token that authorizes API access to your tenant. Bearer tokens are issued by your Leah CLM tenant administrator and are managed within the platform's Admin settings.

Obtain an API Bearer Token​

API tokens are configured and issued by a Leah CLM tenant administrator. The steps below describe the general process for obtaining an API token from your Leah CLM tenant. Contact your Leah CLM administrator or Leah CLM support if you need assistance with token generation.

  1. Log in to your Leah CLM tenant as an administrator.

  2. Navigate to Admin > API Settings (the exact path may vary by tenant configuration — consult your Leah CLM administrator for the specific location of API token management in your deployment).

  3. Generate or copy an existing API Bearer Token. The token is a long alphanumeric string that uniquely identifies the integration.

  4. Store the token securely. Treat the Bearer token as you would a password — it grants full API access to your tenant data. Do not share it or commit it to source control.

Important

The API Bearer Token provides access to all contract data, metadata, obligations, and user records accessible via the Leah CLM API. Restrict token access to authorized integration users only, and rotate tokens periodically in accordance with your organization's security policies.

For additional information about Leah CLM's integration capabilities and API access, refer to the Leah Integrations page or contact Leah CLM support.

Create a ContractPodAi - Leah CLM Credential​

  • To create a new ContractPodAi - Leah CLM credential, after selecting the data source 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.

Bearer Token (API Key) Authentication​

ContractPodAi - Leah CLM uses a single authentication method: a Bearer token (API key) passed in the Authorization request header for all API calls. Configure the following fields:

  1. Enter the base URL of your Leah CLM tenant in the Base URL field. This is the root URL of your cloud instance, for example https://yourcompany-cloud.contractpod.com. Do not include a trailing slash or any path segments — Nexla will append the required API paths automatically.

  2. Enter your API Bearer Token in the API Bearer Token field. This is the secure token obtained from your Leah CLM tenant administrator as described in the Prerequisites section above. The token will be sent as Authorization: Bearer <token> with each API request.

    The API Bearer Token field is treated as a secure (password-type) field. Once saved, the token value will not be displayed again in the credential settings. Store a copy of the token in a secure location before saving.

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. Nexla will validate the credential by making a test call to the Leah CLM API before saving.

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