---
title: "List connections"
method: GET
path: "/connections"
tags: ["Connections"]
---

# List connections

`GET /connections`

## Request

- Base URL: `https://api.customdomain.ai/v1`
- URL: `https://api.customdomain.ai/v1/connections`
- Auth: one of:
  - HTTP bearer
  - HTTP bearer
  - OAuth 2 (authorization code, authorization URL `https://api.customdomain.ai/oauth/agent/authorize`, token URL `https://api.customdomain.ai/oauth/agent/token`, scopes: `domains:read`)

With an API key: every connection across the tenant's applications (optional `?app_id=` and `?status=` filters). With an `app`-scoped widget JWT or a delegated agent token: the calling application's connections (`app_id` is ignored; the scope is fixed to that application). A `connect`-scoped widget JWT (an end user's) is refused with `403`.

**The response is paginated and always bounded.** `limit` defaults to 500 and is clamped to 1000; `next_cursor` is present **only** when more rows remain. To read every connection, follow `next_cursor` until it is absent. Counting rows client-side is not required; see `GET /connections:count`.

A `status` outside the enum is rejected with **400** (it used to reach the database and surface as a 500).

A delegated agent token needs `domains:read`.

## Query parameters

- `app_id` string
- `status` 'pending' | 'propagating' | 'live' | 'failed'
- `limit` integer
- `cursor` string

## Response `200`

Connections

- object
  - `connections` Connection[], required
    - `id` string, required
    - `application_id` string, required
    - `domain` string, required
    - `host` string: subdomain label; empty means the apex
    - `provider_id` string: detected / applied DNS provider
    - `setup_type` 'automatic' | 'manual' | 'async' | 'mcp', required: How a connection reaches live.
    - `status` 'pending' | 'propagating' | 'live' | 'failed', required
    - `managed` boolean: `true` when the connection opted into **managed mode**: the control plane holds a durable, encrypted async grant and can re-apply (`POST /v1/connections/{id}:reapply`) or revert (`DELETE /v1/connections/{id}`) the template server-side without re-consent. Omitted (treated as `false`) for the default use-once connection.
    - `created_at` string, date-time, required
    - `sandbox` boolean: `true` when the connection belongs to a test mode application. Its DNS is simulated, nothing real is read, written or served, and it counts for nothing (no free domain, quota, billing or metering). Copied from the application at create and never changed. Omitted (treated as `false`) on a real connection.
    - `last_checked_at` string, date-time: When the propagation poller last examined this connection. Omitted until the first check.
    - `www_redirect` boolean: Serve an apex↔www redirect. Echoed from create.
    - `override_spf` boolean: Replace an existing SPF record instead of merging into it, where the provider supports it. Echoed from create.
    - `validate_dmarc` boolean: Stored and echoed from create; not acted on yet.
    - `validate_caa` boolean: Whether the Let's Encrypt CAA records are part of the desired record set. Echoed from create.
    - `monitor` boolean: Whether the domain is enrolled in drift monitoring. Echoed from create, where it defaults to true when omitted, and honoured: the drift watch is registered when the connection goes live only if this is true. Connections created before the flag was honoured read true (they were monitored unconditionally, and were backfilled), so this is false only where a caller explicitly opted out.
    - `batch_id` string: The multi-domain session this connection was created in. Omitted for a standalone connect.
    - `end_user_ref` string: The integrator's own identifier for the end user who connected this domain. Omitted for a console/direct connect.
    - `retried_at` string, date-time: When a human (or the create-path resume, or real edge traffic) last asked for this connection to be re-verified. The retry clock is max(created_at, retried_at): a revived connection gets a fresh window from here, not from its original creation. Absent when it was never retried.
    - `routing` ConnectionRouting
      - `mode` 'edge' | 'custom', required: `edge`: records point at the CustomDomain™ edge. `custom`: at your own infrastructure.
      - `cname_target` string: For `custom`: the hostname subdomains and ALIAS-capable roots point at.
      - `apex_ipv4` string[]: For `custom`: the addresses roots get on DNS providers with no ALIAS-style record.
      - `set_at` string, date-time, required: When this routing was recorded for the domain.
    - `records_source` 'integrator': Present as `integrator` when the connection's desired record set was supplied through `PUT /v1/connections/{id}/records` rather than authored by us. Omitted for the usual server-synthesized or Domain Connect template-materialized set. Such a connection cannot use the Domain Connect rail, which applies our published templates at the provider.
    - `created_via` '' | 'widget' | 'console' | 'api' | 'agent' | 'mcp': Where the connection was created, recorded once at create and never changed. `widget`: an end user's connect-scoped widget token (the embedded widget in your product). `console`: the CustomDomain™ console. `api`: an API key, or an app-scoped token, from your server. `agent`: a delegated agent access token. `mcp`: the MCP server. Empty for connections created before this was recorded. A trusted server-side caller may name its surface with the `X-CustomDomain-Client` request header (`console` or `mcp`); the header is a label only and grants nothing.
    - `secure_root_domain` boolean: The edge also issues/secures the registrable apex alongside this subdomain connection. Omitted (treated as `false`) when unset.
    - `redirect_to` string, uri: URL the edge 301s this host to (Power redirect target). Omitted when the connection is not a redirect.
    - `power_root_path_access` string[]: URL paths the edge may static-serve at the root (Power root-path access). Omitted when none are configured.
    - `error_code` string: The last failure reason recorded for this connection, from whichever path failed, not only the background poller. It is persisted by: the propagation poller / `:recheck` verification (e.g. `propagation_timeout`, `setup_incomplete`, `pending_expired`, `domain_already_connected`); the foreground apply on `POST /connections/{id}/apply` (e.g. `dns_write_failed`, `ProviderAuthenticationError`, `spf_merge_failed`, `apex_not_supported`, `forwarding_not_supported`); the OAuth callback (which also records `forwarding_not_supported`); and the Domain Connect async callback (both e.g. `provider_unavailable`, `ProviderAuthenticationError`, `apply_failed`, `internal_error`, or the provider's own `error` parameter). Rejected request validation (`400`) is deliberately NOT recorded here: a malformed request is not a connection failure. Omitted when healthy or never failed; cleared when the connection next verifies.
    - `error_message` string: Human-readable detail for `error_code`. Populated on the same paths and cleared alongside it. Omitted when there is none.
    - `write_rail` 'api_key' | 'sign_in' | 'domain_connect' | 'domain_connect_async' | 'route53_role' | 'provider_account' | 'managed_dns': The rail that last wrote this connection's records. Omitted when no rail wrote them (a manual setup, or a connection from before this was recorded). It decides what removing the domain can do with the records (`GET /connections/{id}/removal`).
    - `provider_account_id` string: The connected provider account whose credential wrote this connection's records and, when the account's access is `continuous`, keeps them (repairs and removal). Omitted when none.
    - `removal_started_at` string, date-time: Set while the domain is being removed: the records are being taken out and the connection is deleted when that finishes. The domain no longer serves from this moment. Omitted otherwise.
  - `count` integer, required: Rows in THIS page, not the tenant total.
  - `next_cursor` string: Present only when further rows remain. Pass it back as `?cursor=` to fetch the next page.

## Other responses

- `400`: Error envelope: {code, title, details}.
- `401`: Error envelope: {code, title, details}.
- `403`: Error envelope: {code, title, details}.

---

[API](https://skmtc.dev/customdomain/apis/customdomain-control-plane-api.md) · [All operations](https://skmtc.dev/customdomain/apis/customdomain-control-plane-api/llms.txt) · [OpenAPI document](https://skmtc.dev/customdomain/apis/customdomain-control-plane-api/revisions/34d89cb7a7cd?raw)