---
title: "Leave the end user's email address on a connection"
method: PUT
path: "/connections/{id}/end-user-email"
tags: ["Connections"]
---

# Leave the end user's email address on a connection

`PUT /connections/{id}/end-user-email`

## Request

- Base URL: `https://api.customdomain.ai/v1`
- URL: `https://api.customdomain.ai/v1/connections/{id}/end-user-email`
- Auth: one of:
  - HTTP bearer
  - HTTP bearer

The widget's optional "Get DNS updates by email" field. After a domain is set up, the end user can leave an address so they hear if its records ever need to change (one email, with the new records, sent on the platform's behalf).

A widget token for the connection's own application can set an address only while the connection has none: when one is already there (the platform's, or an earlier one) the answer is `409`, so a browser can never overwrite what the platform gave. An API key replaces any earlier address. The address is never echoed back and never logged.

Test domains refuse the call.

## Path parameters

- `id` string, required

## Request body

- object
  - `email` string, email, required

## Response `204`

Stored (or dropped while the feature is off)

## Other responses

- `400`: Error envelope: {code, title, details}.
- `401`: Error envelope: {code, title, details}.
- `403`: Error envelope: {code, title, details}.
- `404`: Error envelope: {code, title, details}.
- `409`: 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)