# EMAIL_DOMAIN_UNAVAILABLE

That domain cannot be registered: it is already in use.

<Callout type="info">
**Category:** [Email delivery](/errors/category/email)
</Callout>

| | |
|---|---|
| HTTP status | `409` Conflict |
| Retry | No |

## When it happens

The domain is already registered, in this account or elsewhere. The answer is the same in every case, so it does not reveal who holds it.

## How to fix it

Check the account's list with `GET …/email-domains`. If you have just deleted it, wait a few minutes and register it again; if it persists, contact support.

## Retry

Do not retry. The outcome is final: sending the same request again gets the same answer.

## Returned by

The operations where this code is most likely. The list is not exhaustive.

- [`POST /v1/accounts/{account_id}/email-domains`](/emails/createAccountEmailDomain)

## Example response

When this error occurs, the API answers `409` Conflict with a JSON body of this shape:

```json
{
  "type": "https://docs.beel.es/errors/EMAIL_DOMAIN_UNAVAILABLE",
  "title": "EMAIL_DOMAIN_UNAVAILABLE",
  "detail": "That domain cannot be registered: it is already in use.",
  "instance": "/v1/<resource>",
  "errors": [],
  "success": false,
  "error": {
    "code": "EMAIL_DOMAIN_UNAVAILABLE",
    "message": "That domain cannot be registered: it is already in use.",
    "details": {}
  },
  "meta": {
    "timestamp": "2026-05-21T10:00:00Z",
    "request_id": "4bf92f3577b34da6a3ce929d0e0e4736"
  }
}
```

The `type` URI is stable and always resolves to this page.

## Message

<Tabs items={["English", "Spanish", "Catalan"]}>
  <Tab value="English">{"That domain cannot be registered: it is already in use."}</Tab>
  <Tab value="Spanish">{"No se puede registrar ese dominio: ya está en uso."}</Tab>
  <Tab value="Catalan">{"No es pot registrar aquest domini: ja està en ús."}</Tab>
</Tabs>

Send the request with `Accept-Language: <es|en|ca>` to receive the message in your preferred language.

## Other errors in this category

<div className="grid grid-cols-2 gap-3 not-prose">
  <Card title="EMAIL_DOMAIN_INVALID" description="The domain is not valid. Provide a full domain name, such as invoices.example.com." href="/errors/EMAIL_DOMAIN_INVALID" />
  <Card title="EMAIL_DOMAIN_LIMIT_REACHED" description="You have reached the maximum number of email domains for your account (‹value›)." href="/errors/EMAIL_DOMAIN_LIMIT_REACHED" />
  <Card title="EMAIL_DOMAIN_NOT_FOUND" description="No email domain with that id belongs to your account." href="/errors/EMAIL_DOMAIN_NOT_FOUND" />
  <Card title="EMAIL_DOMAIN_NOT_READY" description="The domain is still being registered. Try again in a few seconds." href="/errors/EMAIL_DOMAIN_NOT_READY" />
  <Card title="EMAIL_DOMAIN_RESERVED" description="That domain is reserved and cannot be used to send emails." href="/errors/EMAIL_DOMAIN_RESERVED" />
</div>

## Keep exploring

<div className="grid grid-cols-2 gap-3 not-prose">
  <Card title="All Email delivery errors" description="Every code in this category in one table." href="/errors/category/email" />
  <Card title="Error reference home" description="Browse every category or jump to the handling guide." href="/errors" />
</div>

---

Full OpenAPI spec: https://docs.beel.es/api/openapi