> ## Documentation Index
> Fetch the complete documentation index at: https://developers.entri.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Entri Unify Configuration

> Configuration reference for the showUnify() call.

## Overview

`entri.showUnify(config)` takes a single config object made up entirely of the existing [Connect](/connect/configuration) and [Sell](/sell/overview) keys. There are no Unify-specific keys. Any key you already pass to `connectDomain()` or `purchaseDomain()` is valid here, and Entri forwards the relevant ones into whichever flow the user selects.

This means you don't redefine your setup for Unify. Your authentication, DNS records, and branding carry over from the flows you already use.

## How the config is routed

When the user picks "Connect a domain," Entri applies the Connect-side keys (the same ones `connectDomain()` accepts). When the user picks "Buy a new domain," Entri applies the Sell-side keys (the same ones `purchaseDomain()` accepts). Shared keys such as your application credentials and branding apply to both paths.

Both paths are always presented. There is no key to show only "buy" or only "connect." A partner who needs a single path should call `connectDomain()` or `purchaseDomain()` directly instead of `showUnify()`.

## DNS monitoring

Every domain that completes the flow, whether purchased or connected, is added to [Entri Monitor](/monitor/overview) automatically. You don't pass the `monitor: true` flag that the standalone `connectDomain()` and `purchaseDomain()` calls require. Enrollment is included with `showUnify()`.

To opt out, pass `monitor: false` in the config. Domains that complete that flow are not enrolled:

```js theme={null}
entri.showUnify({
  applicationId: "YOUR_APPLICATION_ID",
  token: "GENERATED_JWT",
  monitor: false, // don't enroll domains from this flow in Entri Monitor
  dnsRecords: [
    // ...
  ],
});
```

## Shared keys

These keys behave the same way they do in the Connect and Sell flows. See the [Connect configuration reference](/connect/configuration) for the full list and field-level detail.

| Key             | Type     | Description                                                          |
| --------------- | -------- | -------------------------------------------------------------------- |
| `applicationId` | `string` | Your Entri application ID.                                           |
| `token`         | `string` | Short-lived JWT generated by your backend.                           |
| `dnsRecords`    | `array`  | The records Entri applies once the domain is connected or purchased. |

## New UI and white-label

Entri Unify is built on Entri's new UI. The unified modal, including the selection screen where the user chooses to buy or connect a domain, is themed through the same `whiteLabel` object you already pass for Connect. There is no separate Unify theming object.

The routed Connect flow uses this same UI, so the white-label properties that apply are the ones documented for the new Connect UI. That list is the single source of truth, so rather than repeat it here, refer to it directly:

<Card title="New UI white-label reference" icon="palette" href="/connect/new-ui">
  The full set of `whiteLabel` properties supported by the new UI
</Card>

### Selection screen

The selection screen, where the user chooses to buy or connect a domain, is themed by the same `whiteLabel` branding properties as the rest of the flow. Your `logo`, `logoBackgroundColor`, `removeLogoBorder`, `hideCompanyLogo`, and `hideEntriLogo` settings all apply here, and `hideCompanyName` switches the heading from "Add a domain to {appName}" to a neutral "Add a domain." These are the same properties documented in the new UI reference above, so there is nothing extra to configure for branding.

The screen's text, including the heading, the subtitle, and the "Buy a new domain" and "Connect a domain" card labels, is provided and localized by Entri. It is not currently overridable through `customCopy`.

## Example

```js theme={null}
entri.showUnify({
  applicationId: "YOUR_APPLICATION_ID",
  token: "GENERATED_JWT",
  dnsRecords: [
    // ...records applied after the user connects or purchases a domain
  ],
});
```