Leah (formerly ContractPodAi) is an enterprise agentic AI platform for Contract Lifecycle Management (CLM). It combines AI-powered authoring, approval workflows, analytics, and repository management, automatically extracting clauses, dates, obligations, and risk scores from contracts. Its REST API exposes contract data, obligations, audit trails, and workflows for analytics pipelines.
Power end-to-end data operations for your ContractPodAi - Leah CLM API with Nexla. Our bi-directional ContractPodAi - Leah CLM connector is purpose-built for ContractPodAi - Leah CLM, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to ContractPodAi - Leah CLM or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your ContractPodAi - Leah CLM workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
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:
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.
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.
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.
Log in to your Leah CLM tenant as an administrator.
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).
Generate or copy an existing API Bearer Token. The token is a long alphanumeric string that uniquely identifies the integration.
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.
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
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.
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 Prerequisites. 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.
Click the Save button at the bottom of the overlay. Nexla will validate the credential by making a test call to the Leah CLM API before saving. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the ContractPodAi - Leah CLM connector tile, then select the credential that will be used to connect to the Leah CLM tenant, and click Next; or, create a new ContractPodAi - Leah CLM credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common ContractPodAi - Leah CLM endpoints. Each template is designed specifically for the corresponding Leah CLM API endpoint, making data source setup easy and efficient. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.
Get Contracts
Retrieve a paginated list of all contracts in the Leah CLM repository. Use this endpoint to build a comprehensive inventory of contracts including their status, type, key dates, and counterparty information. This is the most common starting endpoint for contract analytics and reporting use cases.
Optionally, configure the following parameters to control what data is returned:
Page Size: Enter the number of contracts to retrieve per page in the Page Size field. The default is 50 and the maximum is 100. Nexla will automatically paginate through all available pages to retrieve the full dataset.
Contract Status Filter: Select a status from the Contract Status Filter pulldown to filter contracts by their current lifecycle status. Available values are: All (default, returns all contracts), Draft, Active, Expired, Terminated, and Pending Approval. Leave blank or select All to retrieve contracts in any status.
This endpoint uses incremental pagination, automatically fetching additional pages until all matching contracts have been retrieved. For large contract repositories, consider using the Contract Status Filter to scope the dataset and reduce processing time.
Get Contract by ID
Retrieve the full details of a single contract by its unique identifier. Use this endpoint when you need to pull complete contract information — including all metadata fields and custom attributes — for a specific contract. This is useful for contract-level detail reports or when building lookup-driven flows where contract IDs are sourced from another dataset.
Enter the unique identifier of the contract you want to retrieve in the Contract ID field. This is a required field. Contract IDs can be obtained from the Get Contracts endpoint or from the Leah CLM UI by navigating to a contract record and copying its ID from the URL or record details.
Contract IDs are unique within your Leah CLM tenant. To retrieve details for multiple contracts, consider using the Get Contracts endpoint to obtain a full list, then use Nexla lookup-based macros to drive individual contract lookups.
Search Contracts
Search contracts using a combination of keyword, date range, and status filters. Use this endpoint when you need a targeted subset of contracts rather than the full repository — for example, to retrieve all active contracts for a specific counterparty, or all contracts expiring within a given date range.
Search Keyword: Optionally enter a keyword or phrase in the Search Keyword field to search across contract titles and metadata. Leave blank to return all contracts matching other filter criteria.
Status Filter: Optionally enter a contract status in the Status Filter field to narrow results to contracts in a particular status (e.g., Active, Draft, Expired). Leave blank to return contracts in any status.
Optionally configure the date range filters to restrict results by effective or creation date:
Start Date: Enter the start of the date range in yyyy-MM-dd format. The default is {now-365} (365 days before the current date). Nexla date/time macros such as {now-365} and {now} are supported — these values are resolved dynamically at the time each data flow run executes.
End Date: Enter the end of the date range in yyyy-MM-dd format. The default is {now} (the current date).
Page Size: Enter the number of results to return per request in the Page Size field. The default is 50.
The Search Contracts endpoint submits a POST request with the filter parameters as a JSON body. Results are limited to a single page per execution; for large result sets, consider using the Get Contracts endpoint with the Status Filter instead.
Get Contract Documents
List all documents — including versions and attachments — associated with a specific contract. Use this endpoint to retrieve document-level metadata for a contract, such as document names, types, and version history.
Enter the unique identifier of the contract whose documents you want to list in the Contract ID field. This is a required field. Contract IDs can be obtained from the Get Contracts endpoint or from the Leah CLM UI.
Get Contract Metadata / AI Extracted Fields
Retrieve all metadata fields for a specific contract, including AI-extracted clauses, key dates, party names, obligations, and risk scores. Use this endpoint to access the full set of structured data that Leah CLM's AI has derived from the contract document — valuable for risk analytics, compliance reporting, and contract intelligence workflows.
Enter the unique identifier of the contract to retrieve metadata for in the Contract ID field. This is a required field. Contract IDs can be obtained from the Get Contracts endpoint or from the Leah CLM UI.
AI-extracted metadata includes fields such as clause types, extracted text, risk flags, key obligation dates, and counterparty details — all derived automatically by Leah's AI engine. The specific fields returned depend on the contract type configuration and AI models active in your tenant.
Get Contract Clauses (AI Extracted)
Retrieve AI-extracted clause data for a specific contract, including clause type, extracted clause text, risk level, and playbook deviation flags. Use this endpoint for detailed clause-level analysis — for example, to identify non-standard clauses, assess risk exposure, or audit clause compliance against your organization's playbook.
Enter the unique identifier of the contract to retrieve clause data for in the Contract ID field. This is a required field. Contract IDs can be obtained from the Get Contracts endpoint or from the Leah CLM UI.
Playbook deviation flags indicate where a contract's clause language differs from your organization's approved clause standards. These flags are particularly valuable for risk review workflows and contract audit use cases.
Get Contract Obligations
Retrieve obligation records for a specific contract, including obligation type, responsible party, due date, and completion status. Use this endpoint to track contractual commitments for a single contract — useful for obligation management dashboards and compliance monitoring.
Enter the unique identifier of the contract to retrieve obligations for in the Contract ID field. This is a required field. Contract IDs can be obtained from the Get Contracts endpoint or from the Leah CLM UI.
Get All Obligations
Retrieve all obligations across all contracts in the tenant, including status, due dates, owners, and associated contract references. Use this endpoint for tenant-wide obligation reporting, overdue obligation tracking, and compliance dashboards that span the entire contract portfolio.
Page Size: Optionally enter the number of obligation records per page in the Page Size field. The default is 50. Nexla will automatically paginate through all available pages to retrieve the complete dataset.
Get Users
Retrieve all users configured in the ContractPodAi tenant, including names, email addresses, roles, and active status. Use this endpoint to synchronize Leah CLM user records with other enterprise systems, or to build user-level access and activity reports.
Page Size: Optionally enter the number of user records per page in the Page Size field. The default is 100. Nexla will automatically paginate through all pages to retrieve the complete user list.
Get Contract Types
Retrieve all configured contract type definitions for the tenant, including names, IDs, and associated template and workflow mappings. Use this endpoint to understand the structure of your contract taxonomy or to build reference data for mapping contract types in downstream systems.
No additional configuration is required for this endpoint. All contract type definitions configured in your Leah CLM tenant will be returned automatically.
Get Workflows
Retrieve all workflow definitions and their current configuration, including stages and approval routing rules. Use this endpoint to document your organization's approval workflows, audit workflow configurations, or build process analytics that map contracts to their governing workflows.
No additional configuration is required for this endpoint. All workflow definitions configured in your Leah CLM tenant will be returned automatically.
Get Workflow Instances
Retrieve active and historical workflow instances for contracts, including the current stage, approvers, and timestamps. Use this endpoint to monitor approval pipeline health, track bottlenecks in the contract approval process, and audit the history of workflow execution for specific contracts.
Page Size: Optionally enter the number of workflow instance records per page in the Page Size field. The default is 50. Nexla will automatically paginate through all pages to retrieve the complete list.
Get Tasks
Retrieve all tasks across contracts, including task type, assignee, due date, priority, and completion status. Use this endpoint to build task management dashboards, track overdue items, or synchronize Leah CLM task records with external project management or ticketing systems.
Optionally, configure the following parameters to control what task data is returned:
Page Size: Enter the number of task records per page in the Page Size field. The default is 50. Nexla will automatically paginate through all pages.
Task Status Filter: Select a status from the Task Status Filter pulldown to filter tasks by completion status. Available values are: All (default), Open, Completed, and Overdue. Leave blank or select All to retrieve tasks in any status.
Get Reminders / Key Date Alerts
Retrieve contract reminders and key date alerts, including renewal dates, expiry notices, and custom milestone alerts. Use this endpoint to build proactive contract renewal pipelines, trigger notifications in downstream systems, or report on upcoming contractual milestones across the portfolio.
Page Size: Optionally enter the number of reminder records per page in the Page Size field. The default is 50. Nexla will automatically paginate through all pages to retrieve the complete list.
Get Counterparties
Retrieve counterparty records — vendors, suppliers, and customers — with names, IDs, and contact details. Use this endpoint to synchronize Leah CLM counterparty records with CRM or ERP systems, or to build a master vendor registry from contract data.
Page Size: Optionally enter the number of counterparty records per page in the Page Size field. The default is 100. Nexla will automatically paginate through all pages to retrieve the complete counterparty list.
Get Audit Trail
Retrieve audit trail events for a specific contract, recording all user actions, status changes, and document modifications. Use this endpoint for compliance reporting, change tracking, and forensic analysis of contract activity.
Enter the unique identifier of the contract to retrieve audit events for in the Contract ID field. This is a required field. Contract IDs can be obtained from the Get Contracts endpoint or from the Leah CLM UI.
Audit trail records include user identity, action type, timestamp, and before/after values for changed fields. These records are immutable and provide a complete chain of custody for each contract.
Get Contract Templates
Retrieve all contract template definitions available in the tenant, including template names, types, and associated clause libraries. Use this endpoint to document your template library, audit template coverage across contract types, or build reference data for template governance reporting.
No additional configuration is required for this endpoint. All contract template definitions in your Leah CLM tenant will be returned automatically.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
ContractPodAi - Leah CLM data sources can also be manually configured to ingest data from any valid Leah CLM API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
Leah CLM API endpoints follow the pattern {base_url}/api/v1/{resource} — for example, https://yourcompany-cloud.contractpod.com/api/v1/contracts to retrieve all contracts. For most list endpoints, the response returns records inside a top-level data array; enter $.data[*] in the Path to Data field to treat each element as a separate record. Date/time macros are useful for Leah CLM's startDate and endDate query parameters used by date-range filters, and lookup-based macros can drive individual contract lookups (e.g., sourcing Contract IDs from a dataset derived from the Get Contracts endpoint). You do not need to include the Authorization header — it is automatically added by Nexla based on your Leah CLM credential; if an endpoint requires a Content-Type or Accept header, add it here (e.g., Accept:application/json).
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new ContractPodAi - Leah CLM data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
