# PandaDoc

![PandaDoc_Logo.png](https://assets.relyanceuat.xyz/images/docs/34929268794765/34929268791309.png)
PandaDoc is a document automation and electronic signature platform utilized by businesses to streamline the creation, editing, and signing of various types of documents, such as contracts, proposals, and invoices. Integrating PandaDoc with your workflow will enable you to seamlessly manage document generation and approval processes within your existing systems.

In order to integrate PandaDoc with Relyance AI you will need an **API Key** and **Folder paths**.

#### In PandaDoc:

1. Login to your PandaDoc account.
2. Go to [https://app.pandadoc.com/a/#/settings/api-dashboard/configuration](https://app.pandadoc.com/a/#/settings/api-dashboard/configuration)
3. On this page in the **API keys** section, generate and copy your production **API Key**.

#### In the Relyance AI application:

![Screenshot 2025-11-05 220856.png](https://assets.relyanceuat.xyz/images/docs/34929268794765/40895918414861.png)
1. Login to your Relyance AI account.
2. Navigate to the **Settings** (bottom-left corner).
3. Select **Integrations**.
4. Search and locate the **PandaDoc** 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**,
    1. **Connection Name**: This property allows you to update the integration specified in Step 6. If you have multiple integrations for the same vendor, you may want to assign distinct names to each. This helps streamline filtering by **Discovery Source** across the **Inventory**, **Visual** **Maps**, **Assets**, and **Data Flow Analysis** pages.
    2. **Rescan Frequency**: This property allows you to configure how often Relyance executes scans against this Vendor connection.
    3. **Business Atlas Associations** (required): the business entities or products that newly discovered third parties, services and assets from this integration are attributed to. Choose at least one from the **Select Associations** dropdown — the wizard will not advance past this step without one. For more details, see [Business Atlas](/docs/other-settings/business-atlas-overview/).
9. In the **Authentication** section, provide the following information retrieved from the **PandaDoc** section and click on **Authenticate**. - **API Key**
    - **Path of the folders containing contracts delimited by; (Eg: folder1; folder2)**
10. Review the configuration summary from the **Completion** section and click on **Finish.**

![Screenshot](https://assets.relyanceuat.xyz/images/docs/34929268794765/34929268792205.png)

![Screenshot 2025-11-05 221318.png](https://assets.relyanceuat.xyz/images/docs/34929268794765/40895918417805.png)

![Screenshot](https://assets.relyanceuat.xyz/images/docs/34929268794765/34929298434317.png)

11. Confirm the integration Status reflects **Connected**

<!-- 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), `Path of the folders containing contracts delimited by ;` | — |

<!-- 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" "pandadoc" {
  vendor = "pandadoc"
  name   = "<your connection name>"

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

  scans = { "contract-scan" = { enabled = true } }
}
```

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