# Linksquares

![Image 1 of 1](https://assets.relyanceuat.xyz/images/docs/34757040563597/34757040550029.svg)
LinkSquares is a legal tech company that offers contract analytics and management software, utilizing artificial intelligence and machine learning to extract data from contracts, streamline contract review, and enhance compliance for businesses.

In order to integrate LinkSquares with Relyance AI you will need an **API Key**.

#### In LinkSquares:

1. Login to your LinkSquares account.
2. At the top of the screen, click the matrix icon (the 9 dots) and select **SETTINGS**.
3. Click **API Keys**.
4. Click the **GENERATE API KEY** button.
5. Copy the **API Key** to be used in Relyance.

#### In the Relyance AI application:

1. Login to your Relyance account.
2. Navigate to the **Settings** (bottom-left corner).
3. Select **Integrations**.
4. Search and locate the **LinkSquares** integration card and click on it.
5. Click on the **Add Connection** button on the top right
6. Provide a meaningful name for the integration and click on the **Add** button
7. In the **Overview** section, select the integration features you wish to enable for the integration, review the **Scope and Permission**, and **Endpoint** details and click on **Continue**. For more details, see [Integration Features](/docs/introduction-to-relyance-ai/integration-features/)
8. In the **Connection** section, provide the appropriate values and click on **Continue**,

![Screenshot 2025-11-05 194352.png](https://assets.relyanceuat.xyz/images/docs/34757040563597/40890619358477.png)

![Screenshot 2025-11-05 194409.png](https://assets.relyanceuat.xyz/images/docs/34757040563597/40890619361165.png)

9. In the Authentication section, provide the **API Key, Agreement Type and Agreement tags**
10. If the Data Inspection check box is checked from step 7, In the Data Inspection section, provide the appropriate values and click on **Continue** **Minimum Confidence Level:** This property adjusts the sensitivity of the Data Inspection feature. Lower likelihoods (e.g., unlikely) offer more coverage but may produce false positives, while higher sensitivity (e.g., very likely) provides greater accuracy but less coverage.

![Screenshot 2025-11-05 194422.png](https://assets.relyanceuat.xyz/images/docs/34757040563597/40890619363213.png)

![Screenshot 2025-11-05 194535.png](https://assets.relyanceuat.xyz/images/docs/34757040563597/40890603940621.png)

11. Review the configuration summary from the Completion section and click on Finish.
12. Confirm the integration Status reflects Connected

![Screenshot 2025-11-05 194515.png](https://assets.relyanceuat.xyz/images/docs/34757040563597/40890619372557.png)

<!-- auth-methods:begin (generated from the integration catalog; do not hand-edit) -->

## Authentication methods and fields

Pick one of these under **Authentication Method** on the connection wizard's **Authentication** step. This table is generated from the integration catalog, so it always matches what the form actually asks for.

| Method | Required | Optional |
| --- | --- | --- |
| **Custom** | `API Key` (secret) | `Agreement Type`, `Agreement Tags` |

<!-- auth-methods:end -->

<!-- terraform-examples:begin (generated from the integration catalog; do not hand-edit) -->

## Manage this integration with Terraform

Connections for this integration can be managed as code with the [Relyance Terraform provider](https://registry.terraform.io/providers/Relyance/relyance/latest). Non-secret fields go in `auth.params`; secret fields go in `auth.secrets_wo`, which is write-only — never stored in Terraform state. Rotate secrets by bumping `auth.secrets_wo_version`.

```hcl
resource "relyance_integration_connection" "linksquares" {
  vendor = "linksquares"
  name   = "<your connection name>"

  auth = {
    method = "api-key"
    params = {
      data_storage_location = "us"
    }
    # Secret fields are write-only: sent to Relyance, never stored in state.
    secrets_wo = {
      api_key = var.linksquares_api_key
    }
    secrets_wo_version = 1
  }

  scans = { "data-inspection" = { enabled = true } }
}
```

<!-- terraform-examples:end -->