LinkSquares is an AI-powered contract lifecycle management (CLM) platform trusted by 1,200+ organizations to draft, negotiate, execute, and analyze agreements at scale. Its LinkAI engine automates the full lifecycle — drafting, redlining, execution, renewal, and post-signature intelligence. It offers two API modules: Analyze (contract metadata, terms, tags, hierarchies) and Finalize (agreement versions and workflows).
Power end-to-end data operations for your LinkSquares API with Nexla. Our bi-directional LinkSquares connector is purpose-built for LinkSquares, 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 LinkSquares or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your LinkSquares 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
To connect Nexla to the LinkSquares API, you will need a LinkSquares API key. LinkSquares API keys are managed by administrators within the LinkSquares application and are tied to a specific user account and company.
LinkSquares administrators can generate API keys from within the application settings. Best practice is to use a dedicated service account rather than a personal user account for API integrations (for example, linksquares_api@companydomain.com). The service account must be configured as an Analyze or Finalize Administrator, depending on which LinkSquares products your integration will access.
To generate an API key:
Sign in to your LinkSquares account and open the app selector to navigate to Settings.
In the Settings menu, select API Keys.
Click the Generate API Key button to create a new key.
Copy the generated API key immediately and store it in a secure location, such as a password manager. This key grants access to your organization's agreement data and should be kept confidential.
Each API key is associated with a single user email address. If you need to create more than one API key, each key must be tied to a separate email address. To deactivate a compromised key, sign in to LinkSquares, navigate to Settings > API Keys, and disable the key. A replacement key can be generated immediately after.
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.
LinkSquares uses API key authentication. The API key is transmitted in the x-api-key request header with every API call. Nexla handles this automatically once the credential is configured.
Enter the base URL for the LinkSquares API in the Base URL field. For most organizations using the production environment, this value is https://api.linksquares.com.
Enter your LinkSquares API key in the API Key field. This is the key generated in Prerequisites.
The LinkSquares API enforces a rate limit of 15 requests per second, with a burst allowance of 30 requests. If your integration exceeds this limit, API calls will fail with a "Rate exceeded" error. Nexla manages request pacing automatically, but keep this limit in mind when designing high-volume integrations.
Click the Save button at the bottom of the overlay to save the configured credential. 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.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the LinkSquares connector tile, then select the credential that will be used to connect to the LinkSquares instance, and click Next; or, create a new LinkSquares 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 LinkSquares endpoints. 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. Click on an endpoint to see more information about it and how to configure your data source for this endpoint.
Retrieve Finalize Users
This endpoint retrieves a paginated list of all users in your LinkSquares Finalize workspace, including their names, email addresses, and role information. Use this endpoint when you need to audit user access, synchronize user directories, or identify available assignees for agreement workflows.
No additional parameters are required for this endpoint. Nexla will automatically paginate through all available users, fetching 100 records per page.
The response data is extracted from the users array in each paginated response.
This endpoint retrieves activity log entries and comments for a specific Finalize agreement. Use this endpoint when you need to audit agreement history, track negotiation activity, or export comments for reporting purposes.
Enter the unique identifier of the agreement whose activity logs you want to retrieve in the Agreement ID field. Agreement IDs can be found in the LinkSquares Finalize interface or by first using the List Agreements (Finalize) or List Agreements (Finalize v2) endpoint to retrieve available agreements and their corresponding IDs.
This endpoint returns all activity log entries for the specified agreement in a single response (no pagination). Each entry includes the action type, user, timestamp, and any associated comments.
This endpoint retrieves all attachments associated with a specific agreement in LinkSquares Analyze. Use this endpoint when you need to inventory supporting documents, exhibits, or supplementary files linked to a contract.
Enter the unique identifier of the agreement whose attachments you want to retrieve in the Agreement ID field. Agreement IDs can be found in the LinkSquares Analyze interface or by first using the Retrieve All Agreements endpoint to obtain a list of agreements and their IDs.
The response data is extracted from the attachments array in the response. Each attachment record includes the file name, type, size, and a reference URL.
This endpoint retrieves profile information about the user associated with the API key used for authentication. Use this endpoint to verify credential configuration, retrieve the authenticated user's ID, or confirm which user account is associated with the current API key.
No additional parameters are required. The response returns the full user profile for the authenticated user, including name, email address, and role details.
This endpoint retrieves detailed information about a single agreement in LinkSquares Analyze by its unique ID. Use this endpoint when you need the full metadata, extracted terms, tags, and status for a specific contract.
Enter the unique identifier of the agreement you want to retrieve in the Agreement ID field. You can obtain agreement IDs from the LinkSquares Analyze interface or by using the Retrieve All Agreements endpoint to list available agreements.
The full agreement object is returned, including all extracted Smart Values (terms), tags, types, and document metadata.
This endpoint retrieves a list of all agreements in LinkSquares Analyze with support for optional filtering, sorting, and cursor-based pagination. Use this endpoint to export your full agreement catalog, synchronize agreement metadata with external systems, or build reporting pipelines over your contract portfolio.
No additional parameters are required to retrieve all agreements. Nexla will automatically paginate through all available agreements using cursor-based pagination, following the next_cursor value returned in each response.
Agreement data is extracted from the data array in each response page. Each record includes agreement metadata, extracted terms, tags, and document information.
The Analyze API supports filtering agreements by date, type, tags, and other attributes through query parameters. For advanced filtering options, use the Configure Manually option to add custom query parameters to the API URL. Additional details are available in the LinkSquares Analyze API Sample Use Cases.
Retrieve Agreement Hierarchy
This endpoint retrieves the parent-child relationship hierarchy for a specific agreement in LinkSquares Analyze. Use this endpoint when you need to understand the structural relationships between agreements, such as master service agreements and their associated statements of work or amendments.
Enter the unique identifier of the agreement whose hierarchy you want to retrieve in the Agreement ID field. Agreement IDs can be obtained from the LinkSquares Analyze interface or by using the Retrieve All Agreements endpoint.
The response returns the full hierarchy object, showing parent and child agreement relationships associated with the specified agreement.
This endpoint retrieves the processing status of an agreement file upload in LinkSquares Analyze. Use this endpoint after initiating an agreement upload to confirm that the document has been successfully received and processed by the platform.
Enter the unique upload identifier in the Upload ID field. This ID is returned by the LinkSquares API when an agreement file upload is initiated (for example, after creating agreement metadata via the Create Agreement Metadata destination endpoint).
The response includes the current processing status of the upload, such as whether the document is still being analyzed or has been fully processed and indexed.
This endpoint retrieves the terms (Smart Values) associated with a specific agreement in LinkSquares Analyze, with support for cursor-based pagination. Use this endpoint to extract structured contract data—such as effective dates, expiration dates, payment terms, governing law, and other AI-extracted fields—for reporting, compliance, or downstream processing.
Enter the unique identifier of the agreement whose terms you want to retrieve in the Agreement ID field. Agreement IDs can be obtained from the LinkSquares Analyze interface or by using the Retrieve All Agreements endpoint.
Nexla will automatically paginate through all terms using cursor-based pagination, following the next_cursor value in each response. Term data is extracted from the terms array in each page.
Terms in LinkSquares Analyze represent the structured, AI-extracted data fields (Smart Values) from your agreements. The specific terms available depend on your LinkSquares configuration and the contract types in your portfolio. For additional information, refer to the LinkSquares Analyze API Sample Use Cases.
Retrieve All Tags
This endpoint retrieves a list of all tags available in your LinkSquares Analyze account. Use this endpoint to obtain the complete tag catalog for your organization, which can be used for filtering, categorization, or synchronization with external systems.
No additional parameters are required. All tags are returned in a single response (no pagination), extracted from the tags array.
Each tag record includes the tag name, ID, and any associated metadata used for agreement classification in LinkSquares Analyze.
This endpoint retrieves a paginated list of agreement templates available in LinkSquares Finalize, with optional filtering by template name, kind, and creation date. Use this endpoint to discover available templates for agreement creation, audit your template library, or synchronize template metadata with external systems.
No additional parameters are required to retrieve all templates. Nexla will automatically paginate through available templates, fetching 100 records per page. Template data is extracted from the templates array in each response page.
Each template record includes the template name, ID, kind (type of template), and creation date, which can be used to identify the correct template when creating new agreements via the Finalize API.
This endpoint retrieves a paginated list of agreements in LinkSquares Finalize, with optional filtering by name, status, template, or date. Use this endpoint to export your Finalize agreement catalog, monitor active agreements, or build reporting pipelines over your pre-signature contract workflow.
No additional parameters are required. Nexla will automatically paginate through all available Finalize agreements, fetching 25 records per page. Agreement data is extracted from the agreements array in each response page.
Each agreement record includes the agreement name, status, associated template, creation date, and other workflow metadata specific to the Finalize environment.
This endpoint retrieves detailed information about a single agreement in LinkSquares Finalize by its unique ID, with support for optional included fields. Use this endpoint when you need the complete record for a specific Finalize agreement, including its status, current version, associated questions, and workflow details.
Enter the unique identifier of the Finalize agreement you want to retrieve in the Agreement ID field. Agreement IDs can be obtained from the LinkSquares Finalize interface or by using the List Agreements (Finalize) or List Agreements (Finalize v2) endpoint.
The full agreement object is returned, including its status, version history, template reference, and any associated metadata.
This endpoint retrieves available status information for agreements in LinkSquares Finalize by status ID. Use this endpoint to look up status definitions, determine valid status transitions, or synchronize status metadata with external workflow systems.
Enter the unique identifier of the status you want to retrieve in the Status ID field. Status IDs correspond to the agreement lifecycle stages defined in your LinkSquares Finalize configuration (for example, Draft, In Review, Executed).
The response returns the status definition object, including the status name, description, and any associated workflow rules.
This endpoint retrieves all versions of a specific agreement in LinkSquares Finalize v2, with support for pagination. Use this endpoint to track the revision history of a contract, compare versions, or audit changes made during negotiation.
Enter the unique identifier of the Finalize agreement whose version history you want to retrieve in the Agreement ID field. Agreement IDs can be obtained from the LinkSquares Finalize interface or by using the List Agreements (Finalize v2) endpoint.
Nexla will automatically paginate through all available versions, fetching 25 records per page. Version data is extracted from the agreement_versions array in each response page. Each version record includes the version number, status, upload date, and file reference.
This endpoint retrieves detailed information about a specific version of a Finalize agreement. Use this endpoint when you need the metadata, status, or file reference for a particular revision of a contract.
Configure the following required fields:
Agreement ID: Enter the unique identifier of the Finalize agreement. Agreement IDs can be obtained from the LinkSquares Finalize interface or by using the List Agreements (Finalize v2) endpoint.
Version ID: Enter the unique identifier of the specific version you want to retrieve. Version IDs can be obtained using the List Agreement Versions endpoint.
The response returns the full version object, including the version number, file reference, status, and any associated metadata.
This endpoint retrieves a paginated list of agreements in LinkSquares Finalize using the v2 API, with optional pagination and filtering parameters. Use this endpoint when you need access to the most current Finalize agreement data structures, including additional fields and capabilities introduced in the v2 API.
No additional parameters are required. Nexla will automatically paginate through all available Finalize v2 agreements, fetching 100 records per page. Agreement data is extracted from the agreements array in each response page.
Each agreement record includes the agreement name, status, current version reference, template reference, creation date, and other v2-specific metadata.
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.
LinkSquares data sources can also be manually configured to ingest data from any valid LinkSquares 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.
LinkSquares API source endpoints use the GET method against the base URL https://api.linksquares.com—for example, https://api.linksquares.com/analyze/v1/agreements to retrieve all Analyze agreements, https://api.linksquares.com/analyze/v1/agreements/{'{agreement_id}'}/terms to retrieve agreement terms, or https://api.linksquares.com/finalize/v2/agreements to list Finalize agreements. The API enforces a rate limit of 15 requests per second with a burst allowance of 30 requests; Nexla manages request pacing automatically. You do not need to add the x-api-key authentication header, since Nexla adds it automatically based on your LinkSquares credential.
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 LinkSquares 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.
Click the + icon on the Nexset that will be sent to the LinkSquares destination, and select the Send to Destination option from the menu. Select the LinkSquares connector from the list of available destination connectors, then select the credential that will be used to connect to the LinkSquares organization, and click Next; or, create a new LinkSquares credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common LinkSquares endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
Link Agreements in Finalize
This endpoint links related agreements together within the LinkSquares Finalize workflow. Use this endpoint when you need to associate agreements—for example, linking an amendment to its parent agreement or connecting related contracts in your Finalize workspace.
The request body should include the IDs of the agreements to be linked. Nexla sends the Nexset data as a JSON payload to the LinkSquares Finalize API. Ensure the Nexset contains the required fields for the link relationship as defined by the LinkSquares Finalize API schema.
This endpoint uses a POST method and sends data as a single record per API call (batch mode is disabled).
This endpoint sets or updates the owner of a Finalize agreement. Use this endpoint when you need to assign agreement ownership programmatically—for example, as part of an onboarding workflow that routes new agreements to the appropriate account manager or legal reviewer.
This endpoint requires the following configuration:
Agreement ID: Enter the unique identifier of the Finalize agreement whose owner you want to set. This value is used in the API URL path. Agreement IDs can be obtained from the LinkSquares Finalize interface or by using the List Agreements (Finalize) source endpoint.
The request body should include the user ID of the new agreement owner. Nexla sends the Nexset data as a JSON payload using a PATCH method. Ensure the Nexset contains the required owner field as defined by the LinkSquares Finalize API.
This endpoint updates the name of a Finalize agreement. Use this endpoint when you need to rename agreements programmatically—for example, as part of a standardization workflow that applies consistent naming conventions across your contract portfolio.
This endpoint requires the following configuration:
Agreement ID: Enter the unique identifier of the Finalize agreement you want to rename. This value is used in the API URL path. Agreement IDs can be obtained from the LinkSquares Finalize interface or by using the List Agreements (Finalize) source endpoint.
The request body should include the new agreement name. Nexla sends the Nexset data as a JSON payload using a PATCH method. Ensure the Nexset contains the updated name field as defined by the LinkSquares Finalize API.
This endpoint creates metadata for a new agreement in LinkSquares Analyze, including the agreement name, file name, type, tags, and terms. The API returns a presigned URL that can be used to upload the actual agreement file. Use this endpoint as the first step in a multi-step agreement ingestion workflow.
The request body should include the agreement metadata fields. The required and optional fields are defined by the LinkSquares Analyze API and typically include:
Name: The display name of the agreement as it will appear in LinkSquares Analyze.
File Name: The file name of the document to be uploaded (including the file extension, such as .pdf or .docx).
Type: The agreement type as configured in your LinkSquares account (e.g., Master Service Agreement, NDA, SOW).
Tags: Optional tags to apply to the agreement for categorization and filtering.
Terms: Optional pre-populated term values (Smart Values) to associate with the agreement.
The API response includes a presigned S3 URL that must be used to upload the agreement file within a limited time window. The upload status can be checked using the Get Upload Status source endpoint after the file has been uploaded.
For complete information about the Analyze API agreement ingestion workflow and the required request body structure, refer to the LinkSquares Analyze API Sample Use Cases.
Create Agreement Attachment
This endpoint adds an attachment to an existing agreement in LinkSquares Analyze. The API returns a presigned URL that can be used to upload the attachment file. Use this endpoint to programmatically associate supplementary documents—such as exhibits, amendments, or supporting materials—with an existing contract.
This endpoint requires the following configuration:
Agreement ID: Enter the unique identifier of the Analyze agreement to which the attachment will be added. This value is used in the API URL path. Agreement IDs can be obtained from the LinkSquares Analyze interface or by using the Retrieve All Agreements source endpoint.
The request body should include the attachment metadata (such as file name and type) as defined by the LinkSquares Analyze API. The API response includes a presigned URL for uploading the attachment file.
This endpoint updates an existing agreement in LinkSquares Analyze with new metadata, tags, or status information. Use this endpoint to programmatically modify agreement properties—for example, updating term values, reassigning tags, or changing the agreement status as part of an automated contract management workflow.
This endpoint requires the following configuration:
Agreement ID: Enter the unique identifier of the Analyze agreement you want to update. This value is used in the API URL path. Agreement IDs can be obtained from the LinkSquares Analyze interface or by using the Retrieve All Agreements source endpoint.
The request body should include only the fields you want to update. Nexla sends the Nexset data as a JSON payload using a PATCH method, so only the fields present in the payload will be modified. Unspecified fields will retain their current values.
The LinkSquares Analyze API supports updating terms (Smart Values), name, type, notes, tags, and parent-child hierarchies. For complete information about the update agreement endpoint and supported fields, refer to the LinkSquares Analyze API Sample Use Cases.
Create Agreement (Finalize)
This endpoint creates a new agreement in LinkSquares Finalize using a template or file upload. Use this endpoint when you need to initiate the contract drafting and negotiation workflow from an external system, such as submitting a new request for legal review from a CRM, ERP, or other business application.
The request body should include the agreement details required by the Finalize API, such as the template ID, agreement name, and any pre-populated field values. Nexla sends the Nexset data as a JSON payload using a POST method.
The API response includes the new agreement ID and initial status, which can be used to track the agreement's progress through the Finalize workflow using the Get Agreement (Finalize) source endpoint.
This endpoint uploads an attachment file to an existing agreement in LinkSquares Finalize. Use this endpoint to programmatically add supporting documents, exhibits, or reference files to a Finalize agreement during or after the drafting process.
This endpoint requires the following configuration:
Agreement ID: Enter the unique identifier of the Finalize agreement to which the attachment will be added. This value is used in the API URL path. Agreement IDs can be obtained from the LinkSquares Finalize interface or by using the List Agreements (Finalize) source endpoint.
The request body should include the attachment metadata as defined by the LinkSquares Finalize API. Nexla sends the Nexset data as a JSON payload using a POST method.
This endpoint updates agreement details in LinkSquares Finalize, including status, completion flag, and question answers. Use this endpoint to programmatically advance an agreement through its workflow stages, mark it as complete, or update intake form responses from an external system.
This endpoint requires the following configuration:
Agreement ID: Enter the unique identifier of the Finalize agreement you want to update. This value is used in the API URL path. Agreement IDs can be obtained from the LinkSquares Finalize interface or by using the List Agreements (Finalize) source endpoint.
The request body should include only the fields you want to update. Nexla sends the Nexset data as a JSON payload using a PATCH method. Supported update fields include status, completion flag, and question (token) answer values.
The Finalize API also supports updating token answers programmatically via PATCH, allowing you to modify specific intake form data fields directly through the API. For complete information, refer to the LinkSquares Finalize API Technical Overview.
Upload Agreement Version
This endpoint uploads a new version of a Finalize agreement with an updated status and version file reference. Use this endpoint when you need to submit a revised contract document as part of the negotiation workflow—for example, after incorporating redlines from a counterparty.
This endpoint requires the following configuration:
Agreement ID: Enter the unique identifier of the Finalize agreement for which a new version is being uploaded. This value is used in the API URL path. Agreement IDs can be obtained from the LinkSquares Finalize interface or by using the List Agreements (Finalize) source endpoint.
The request body should include the new version details, such as the status and version file reference, as defined by the LinkSquares Finalize API. Nexla sends the Nexset data as a JSON payload using a POST method.
This endpoint creates and finalizes a new version of a Finalize agreement using the v2 API, with a version file and status. Use this endpoint when you need to create agreement versions using the most current Finalize API capabilities, which offer additional fields and improved version management compared to the v1 endpoint.
This endpoint requires the following configuration:
Agreement ID: Enter the unique identifier of the Finalize agreement for which a new version is being created. This value is used in the API URL path. Agreement IDs can be obtained from the LinkSquares Finalize interface or by using the List Agreements (Finalize v2) source endpoint.
The request body should include the version details as defined by the LinkSquares Finalize v2 API. Nexla sends the Nexset data as a JSON payload using a POST method.
This endpoint marks the upload of an agreement version as complete in LinkSquares Finalize v2. Use this endpoint as the final step in a multi-step version upload workflow after the version file has been successfully uploaded to the presigned URL provided by the Create Agreement Version (Finalize v2) endpoint.
This endpoint requires the following configuration:
Agreement ID: Enter the unique identifier of the Finalize agreement. This value is used in the API URL path.
Version ID: Enter the unique identifier of the specific agreement version to mark as complete. Version IDs are returned by the Create Agreement Version (Finalize v2) endpoint and can also be retrieved using the List Agreement Versions source endpoint.
The request body should include any completion metadata as defined by the LinkSquares Finalize v2 API. Nexla sends the Nexset data as a JSON payload using a PATCH method.
This endpoint creates a new agreement in LinkSquares Finalize using the v2 API, with support for an optional file, template, tokens (field values), answers, and tables. Use this endpoint when you need to create agreements using the most current Finalize API capabilities, which provide a richer set of options for agreement initialization compared to the v1 endpoint.
The request body should include the agreement creation details as defined by the LinkSquares Finalize v2 API. Optional fields include a file reference, template ID, pre-populated token (field) values, question answers, and table data. Nexla sends the Nexset data as a JSON payload using a POST method.
The API response includes the new agreement ID and initial status, which can be used to track the agreement's progress through the Finalize workflow using the Get Agreement (Finalize) or List Agreements (Finalize v2) source endpoints.
LinkSquares destinations can be manually configured to send data to any valid LinkSquares API endpoint. Manual configuration provides maximum flexibility when you need to use endpoints not covered by pre-built templates, add custom query parameters, or apply additional customizations to the API request. 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, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.
LinkSquares write operations use POST to create resources (for example, https://api.linksquares.com/analyze/v1/agreements to create an Analyze agreement, or https://api.linksquares.com/finalize/v2/agreements to create a Finalize v2 agreement) and PATCH to update them (for example, https://api.linksquares.com/analyze/v2/agreements/{'{agreement_id}'}). The API accepts JSON (application/json) for all write operations. You do not need to add the x-api-key authentication header, since Nexla adds it automatically based on your LinkSquares credential.
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To begin sending data to the configured LinkSquares endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to the LinkSquares API until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.
