# Airship

![Airship-logo.svg](https://assets.relyanceuat.xyz/images/docs/34521865016973/34521850110733.svg)
Airship is a SaaS platform for customer engagement, lifecycle marketing, and analytics and data solutions. It allows companies to generate custom messages to consumers via push notifications, SMS messaging, and similar, and provides customer analytics services.

In order to integrate Airship with Relyance AI you will need an **App Key** and **Master Secret**.

#### In Airship:

1. Login to your Airship account.
2. Select an existing project or create a new one.
3. Once in the project, click Settings from the top navigation bar.
4. On the settings page, copy the App Key and Master Secret from the right-side info box.

![Airship-1.png](https://assets.relyanceuat.xyz/images/docs/34521865016973/34521850111501.png)

![Airship-2.png](https://assets.relyanceuat.xyz/images/docs/34521865016973/34521850111885.png)

![Airship-3.png](https://assets.relyanceuat.xyz/images/docs/34521865016973/34521865000461.png)

#### In the Relyance AI application:

![Screenshot 2025-11-06 225323.png](https://assets.relyanceuat.xyz/images/docs/34521865016973/40929350973453.png)
1. Login to your Relyance AI account.
2. Navigate to the **Settings** (bottom-left corner).
3. Select **Integrations**.
4. Search and locate the **Airship** 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 **Airship** section and click on **Authenticate**. - App Key
    - Master Secret
    - **Airship's European cloud site**
10. Review the configuration summary from the **Completion** section and click on **Finish.**

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

![Screenshot 2025-11-06 225441.png](https://assets.relyanceuat.xyz/images/docs/34521865016973/40929377927309.png)

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

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

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

## If the connection reports Connected but returns nothing

These are the ways this integration comes back empty without reporting an error. Generated from the integration catalog, so it tracks what the connection actually asks for.

1. **A credential rotated at the vendor is not picked up here.** **App Key** and **Master Secret** are stored when you save the connection, so regenerating the value at the vendor breaks the next scan until it is re-pasted here. Recording the expiry on the connection means Relyance warns you before it lapses.
2. **Check the address fields before suspecting the credentials.** **Airship's European cloud site** identifies which tenant, region or host to talk to. A wrong value there fails authentication and looks exactly like a bad secret.

<!-- failure-modes: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" "urbanairship" {
  vendor = "urbanairship"
  name   = "<your connection name>"

  auth = {
    method = "app-credentials"
    params = {
      data_storage_location = "us"
    }
    # Secret fields are write-only: sent to Relyance, never stored in state.
    secrets_wo = {
      app_key = var.urbanairship_app_key
      app_secret = var.urbanairship_app_secret
      is_european_site = "false"
    }
    secrets_wo_version = 1
  }

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

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