# Telesign

![Telesign_Logo.svg](https://assets.relyanceuat.xyz/images/docs/15874941040269/16165773626253.svg)
Telesign provides digital identity and programmable communications APIs to prevent fraud and enable omnichannel engagement.

Telesign does not have a public API that reports PI. In this case, Relyance has a **Static** connection type that derives PI from the vendor API documentation.

#### In the Relyance AI application:

![Telesign-1.png](https://assets.relyanceuat.xyz/images/docs/15874941040269/16165979386509.png)
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 **Vendor Integration** tab.
5. Find the **Telesign** integration card and click it to open its connections.
6. Under **Authentication Method**, choose **Static**.
8. Click **Authenticate**.
9. At this point, you should see the following result on the **Vendor** Integrations page:

![Telesign-2.png](https://assets.relyanceuat.xyz/images/docs/15874941040269/16166094599821.png)

10. Congratulations, you are now connected to **Telesign**.

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

  auth = {
    method = "no-credentials"
    params = {
      data_storage_location = "us"
    }
  }

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

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