# Avalara

![avalara_logo.png](https://assets.relyanceuat.xyz/images/docs/16172075443853/16171858528397.png)
Avalar is a cloud-based SaaS platform that helps businesses of all sizes achieve compliance with transactional taxes, including VAT, sales and use, excise, communications, and other tax types.

In order to integrate Avalara with Relyance AI you will need your **Avalara** **Username** and **Avalara** **Password**.

#### In the Relyance AI application:

1. Login to your Relyance account.
2. Navigate to the **Settings** Menu in the bottom left-hand side.
3. Select **Integrations**.
4. Click on the **Vendors and Data Stores** filter.
5. Find the **Avalara** integration card and click it to open its connections.
6. Under **Authentication Method**, choose **Custom**.
8. Paste the **Avalara** **Username** and **Avalara** **Password** into their respective fields.

![Avalara-1.png](https://assets.relyanceuat.xyz/images/docs/16172075443853/16172096664973.png)

9. Click **Authenticate**.
10. At this point, you should see the following result on the **Vendor** Integrations page:

![Avalara-2.png](https://assets.relyanceuat.xyz/images/docs/16172075443853/16172072962189.png)

11. Congratulations, you are now connected to **Avalara**.

<!-- 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** | `Avalara Username`, `Avalara Password` (secret) | — |
| **Custom - Sandbox** | `Avalara username`, `Avalara password` (secret), `For Testing Sandbox` | — |

<!-- 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`.

### Username & password

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

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

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

### Username & password — Custom - Sandbox

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

  auth = {
    method = "username-password-sandbox"
    params = {
      username = "<username>"
      sandbox = "true"
      data_storage_location = "us"
    }
    # Secret fields are write-only: sent to Relyance, never stored in state.
    secrets_wo = {
      password = var.avalara_password
    }
    secrets_wo_version = 1
  }

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

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