# The CustomDomain™ services the domain uses

> The CustomDomain™ services the domain uses: CustomDomain™ API reference in the connections group. Covers parameters, request body, responses and error codes.

Source: https://docs.customdomain.ai/docs/api-reference/connections/getConnectionServices

## `GET https://api.customdomain.ai/v1/connections/{id}/services`

Every CustomDomain™ service with whether this domain uses it, computed from stored facts: DNS connect (with the rail that wrote the records and the access CustomDomain™ holds), managed DNS, edge serving, the HTTPS certificate, Power, monitoring, automatic repair, redirects, email records and CAA. `state` is `active`, `pending` (set up, not serving yet), `attention` (in use, and something needs a person), `paused` (automatic repair where CustomDomain™ holds the access but the deployment has not switched repair on, `MONITOR_AUTO_REPAIR`) or `inactive`. An end user's widget token (scope `connect`) reads this only when it is bound to the domain and minted with the connection's own `end_user_ref`; use an API key otherwise.

### Authentication

`widgetJWT`, `apiKey`

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `id` | path | string | yes |  |

### Responses

| Status | Description |
| --- | --- |
| `200` | The services |
| `401` | Error envelope: {code, title, details}. |
| `403` | Error envelope: {code, title, details}. |
| `404` | Error envelope: {code, title, details}. |

### `200` response body

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `connection_id` | string | yes |  |
| `application_id` | string | yes |  |
| `domain` | string | yes |  |
| `status` | string | yes |  |
| `provider` | string | no |  |
| `provider_name` | string | no |  |
| `access` | object | yes |  |
| `services` | array of object | yes |  |
| `active_count` | integer | yes |  |

The full specification is served at `GET https://api.customdomain.ai/v1/openapi.json`.
