# Remove Power (drop the origin, clear config, tear down the cert)

> Remove Power (drop the origin, clear config, tear down the cert): CustomDomain™ API reference in the power group. Covers parameters, request body and responses.

Source: https://docs.customdomain.ai/docs/api-reference/power/disableConnectionPower

## `DELETE https://api.customdomain.ai/v1/connections/{id}/power`

Clears the forward and the root path access, drops the origin and tears down the certificate. Clearing a forward is checked like any redirect change: on a domain whose `www` redirect is on, the visit that went to the forward now goes to the `www` name, and when that would come back (`www` forwards to the root) the call is refused with `422` `redirect_loop` and nothing is changed, the origin included. The `www` redirect itself is not cleared here (`PATCH /connections/{id}` turns it off).

### Authentication

`widgetJWT`, `apiKey`

### Parameters

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

### Responses

| Status | Description |
| --- | --- |
| `204` | Power removed |
| `401` | Error envelope: {code, title, details}. |
| `404` | Error envelope: {code, title, details}. |
| `409` | `conflict`: the domain's forward or root path access is set and the domain is being removed. |
| `422` | `redirect_loop`: taking the forward off would send a visit round a circle through the `www` redirect. |
| `503` | `redirects_busy`: another change to this workspace's forwarding is still being saved (redirect changes of one workspace are made one at a time), and this one waited for it in vain. Nothing was changed; send it again after the `Retry-After` seconds. `service_unavailable`: edge serving is off in this deployment, so a forward cannot be set. |

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