For the complete documentation index, see llms.txt. This page is also available as Markdown.

Delphix Data Control Tower (DCT)

Connection Requirements

1 - Domain

The hostname of your Delphix Data Control Tower (DCT) gateway, entered without a scheme or trailing slash (e.g. gateway.example.com). The connector builds requests as https://<domain>/dct/<api_version>/....

2 - API Key

Option A - From the DCT UI (DCT 23.0.0 or later): log in to DCT, click your account name in the top-right corner, and choose Regenerate API Key.

Option B - Via API request: using an existing API key, create a new account with a generated key by sending POST https://<domain>/dct/<api_version>/management/accounts with body { "username": "secure-key", "generate_api_key": true } and the existing key in the Authorization: apk <key> header. The response returns the new account's id and token — the token is the new API key. This is useful for scripted or headless provisioning.

With either option, paste the resulting key here in the <id>.<token> format (e.g. 2.vCfC0Mnp...) — without the apk prefix. Prefer a dedicated service account key for this integration; do not reuse the initial bootstrap key (it should be deleted after setup).

3 - API Version

The DCT REST API version segment used in the request path. Leave as the default unless your DCT instance requires a different version. (default: v3)

4 - Is Secure

Choose this if your connection is going to be over HTTPS (optional, default: True).

5 - Fetch Users

Optional. When enabled, DCT accounts are also collected as users. Devices (environment hosts) are always collected. (default: False)

6 - Proxy

Proxy url. (optional)

7 - Timeout

The amount of time (in seconds) to wait for API responses. (default: 30)

Default Values

  • API Version: v3

  • Is Secure: True

  • Fetch Users: False

  • Timeout: 30

Last updated

Was this helpful?