---
url: https://ibee.ai/docs/tools/email-service
last_updated: 2026-10-19
---

> For clean Markdown of any page, append .md to the page URL. For a complete documentation index, see https://ibee.ai/docs/llms.txt (full text of every page: https://ibee.ai/docs/llms-full.txt). For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://ibee.ai/docs/_mcp/server.

# Email Service

> Email Service sends transactional email, such as receipts and password resets, from your own domain. Choose a plan, add and verify your domain, register senders, create an API key, and send over HTTPS or SMTP. Includes limits, errors, suppressions and signed webhooks.

**Email Service** is a sending service that lets your application send transactional email, such as order confirmations, password resets and alerts, from a domain you own, like `acme.com`. Your application sends each message with one HTTPS request (or over SMTP), and the portal shows what happened to it: delivered, bounced, or marked as spam.

> **Info**
>
> Email Service is turned on per organization. If **Email Service** isn't under **Tools** in your sidebar, [contact support](/docs/support/contact-support) to request access.

## When to use it

| You need to…                                                                           | Use                               | Notes                                                                |
| -------------------------------------------------------------------------------------- | --------------------------------- | -------------------------------------------------------------------- |
| Send email from your own app or website code                                           | **HTTPS API** (`POST /v1/emails`) | Fastest to set up from code; returns an ID you can track             |
| Send from software that only speaks SMTP (a CMS, an identity provider, a mail library) | **SMTP relay**                    | Same domains, senders, limits and logs as the API                    |
| Receive email, or give people mailboxes                                                | Not Email Service                 | Email Service only sends. A sender address is not an inbox.          |
| Manage domains, senders and keys from code                                             | The portal                        | Domains, senders, keys, suppressions and webhooks have no public API |

Email Service is built for **transactional** email: messages a person expects because of something they did. Send only to people who asked for your email.

## How it works

1. **Choose a plan** for the workspace. Until a plan is active, Email Service shows only the plan page.
2. **Add your domain** and publish the DNS records the portal shows at your DNS provider. IBEE checks them and marks the domain **Active**.
3. **Register senders**: the exact From addresses you will use, such as `orders@acme.com`.
4. **Create an API key** and send. Delivery results appear under **Emails** and, optionally, at your webhook.

## Before you begin

* **Role:** an organization **Owner** or **Admin** to choose the plan and create API keys; anyone with write access to the workspace (Owner, Admin, Technical) to add domains and senders. See [Team members & access roles](/docs/platform-fundamentals/team-members-access-roles).
* **Identity verification** of your own account, for every change. See [Verify your identity](/docs/getting-started/account-setup/verify-your-identity).
* **Access to your domain's DNS settings** at your DNS provider (for example Cloudflare, GoDaddy or Route 53).
* **Funds for the plan.** Plans have a monthly price and are billed to your organization.

To open Email Service, open a workspace and click **Email Service** under **Tools**. Once a plan is active, the page has eight tabs: **Overview**, **Emails**, **Metrics**, **Domains**, **Logs**, **API keys**, **Webhooks** and **Settings**.

## Choose a plan

### Open the plan page

Open **Email Service**. Until the workspace has a plan, this is the only page.

### Pick a plan

Under **Choose plan**, the table lists each plan's **Emails per month**, **Domains** and **Price**. Every plan includes API and SMTP sending, webhooks, delivery logs and metrics, bounce and complaint suppression, and DKIM signing on your domain. For more than the largest plan, use **Talk to Sales**.

### Activate it

Click **Activate plan**. When the plan is active, the eight tabs appear.

Recipients beyond your plan's monthly allowance are billed separately. **Settings** shows your **Plan allowance**, **Domain limit**, and this month's **Used**, **Included this month** and **Remaining**, with **Upgrade plan**.

## Add and verify your domain

### Add the domain

In **Overview** or **Domains**, click **Add domain**. Under **Sending root domain**, enter a domain you control, such as `acme.com`, without `@` or `https://`. Click **Continue to DNS authentication**.

### Wait for the records

The domain opens on its own page with four steps: **Choose domain**, **Add DNS records**, **Verify connection** and **Register sender**. The **Add DNS records** step fills in by itself once IBEE has prepared the records.

### Add the records at your DNS provider

Add each record exactly as shown. The table gives each record's **Purpose**, **Type**, **Name**, **Value** and **Priority**, with copy buttons. **Copy setup instructions** copies them all and **Download DNS records** saves them to a file. Click **I've added the DNS records** when you're done.

### Verify the connection

Click **Verify connection**. The page updates by itself while IBEE checks.

> **Warning**
>
> Don't change your domain's nameservers or delete its website or mailbox records. Only **add** the records shown.

What the records do, in plain terms:

| Record                                                                     | Usually                                                                                                 | What it proves                                                                                                             |
| -------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| **DKIM** (DomainKeys Identified Mail)                                      | A `TXT` record on `<selector>._domainkey.acme.com`, or `CNAME` records on `<token>._domainkey.acme.com` | Mail from IBEE really is signed for your domain                                                                            |
| **Return-Path**                                                            | A `CNAME` record on `send.acme.com`                                                                     | Bounces come back to IBEE, so bounced addresses are suppressed                                                             |
| **DMARC** (Domain-based Message Authentication, Reporting and Conformance) | A `TXT` record on `_dmarc.acme.com` with `v=DMARC1; p=none;`                                            | Tells receiving servers what to do with mail that fails the checks. IBEE doesn't wait for it before activating the domain. |

Tips for the DNS provider:

* Names are relative to your domain. If your provider adds `acme.com` to the name by itself, don't type it twice.
* Leave the TTL (how long other servers may cache the record) at your provider's default.
* On Cloudflare, set each `CNAME` to **DNS only** (grey cloud). Proxied records can't be verified.

**How long it takes:** new records can take from a few minutes to many hours to be visible. IBEE re-checks by itself every minute for the first 12 minutes, then every 10 minutes, then every hour, for about 72 hours in total. After that, click **Verify connection** again.

### Domain status

| Status                   | What it means                                                    | What to do                                                     |
| ------------------------ | ---------------------------------------------------------------- | -------------------------------------------------------------- |
| **Setting up**           | IBEE is preparing the domain                                     | Wait                                                           |
| **Needs DNS setup**      | A delegated subdomain is waiting for its NS (nameserver) records | Add the NS records at your DNS provider                        |
| **Checking nameservers** | IBEE is checking that delegation                                 | Wait                                                           |
| **Configuring email**    | IBEE is setting up email authentication                          | Wait                                                           |
| **Verification pending** | IBEE is waiting to see your DNS records                          | Check the records, then wait or click **Verify connection**    |
| **Active**               | Verified: you can register senders and create API keys           | Continue                                                       |
| **Retrying**             | A check failed                                                   | Fix the records the page points to, then click **Retry setup** |
| **Suspended**            | Sending from this domain is stopped                              | [Contact support](/docs/support/contact-support)               |
| **Cancelled**            | Setup was cancelled                                              | Add the domain again if you still need it                      |
| **Removing**             | The domain is being removed                                      | Wait                                                           |

**To remove a domain:** open it, go to **Settings** and click **Remove domain** (or use the remove icon in **Domains**), type the domain name, and confirm. Afterwards, delete its records at your DNS provider.

## Register senders

A sender is an exact From address your application may use. The API rejects any From address that isn't a registered sender on an **Active** domain.

### Open the domain's senders

Open an **Active** domain and go to the **Register sender** step or the **Senders** tab.

### Add the sender

Click **Add sender**. Enter the **Sender name**: only the part before `@`, such as `orders` (1–64 lowercase letters, digits, `.`, `_`, `+` or `-`). Optionally add a **Display name** such as `Acme Orders` and a **Reply-To** address.

The saved **Display name** and **Reply-To** are used by **Send test email** in the portal. The API doesn't apply them: send `fromName` and `replyTo` with each request.

To stop using a sender, click its remove icon and confirm **Remove sender**. The row stays as **Disabled**; **Re-enable** brings it back.

## Create an API key

An Email Service **API key** lets your application send. It works only in its workspace and only for the domains you pick. Platform API tokens can't send email, and an Email API key can't manage anything else.

### Open API keys

In **Email Service**, open **API keys** and click **Create API key**.

### Fill in the key

* **Name**: for example `production-app` (up to 80 characters).
* **Permission**: **Sending access** (send), **Sending + read** (send, and read a message's status), or **Read only** (read status, can't send).
* **Domains**: one or more **Active** domains in this workspace, up to 50. **Select all** picks every one.
* **Expires**: **Never** (default), **30 days**, **90 days** or **1 year**.

Click **Create API key**.

### Save the key

The **Save your API key** dialog shows the key **once**. Click **Copy API key**, store it on your application server (never in browser code), tick **I saved the key in a safe place**, and click **Done**.

The organization **API Tokens** page also has an **Email Tokens** tab. **Create Email Token** makes a send-only key for **one** domain, with **Token expiration** of **No expiration**, **7 days**, **30 days**, **90 days** (default) or **1 year**. See [API Tokens](/docs/tools/api-tokens).

**To revoke a key:** click **Revoke** on its row and confirm **Revoke key**. Requests with it fail at once; messages already accepted still go out. Turn on **Show revoked and expired** to see inactive keys.

## Send an email

Send a `POST` request to the send endpoint. The **Send your first email** step on **Overview** shows ready-made cURL, Node.js and Python samples with the address for your account:

```http
POST https://ibee-email-send-api-prod.bifrosts.workers.dev/v1/emails
```

### Headers

| Header            | Required            | Value                                                                                                                     |
| ----------------- | ------------------- | ------------------------------------------------------------------------------------------------------------------------- |
| `Authorization`   | Yes                 | `Bearer <api-key>`                                                                                                        |
| `Content-Type`    | Yes                 | `application/json`                                                                                                        |
| `Idempotency-Key` | No, but recommended | A unique ID for this message, 8–256 characters of letters, digits, `.`, `_`, `:` and `-`. Makes retries safe (see below). |

### Body

| Field         | Required                | Description                                                                          |
| ------------- | ----------------------- | ------------------------------------------------------------------------------------ |
| `from`        | Yes                     | A registered sender, such as `orders@acme.com`, or `"Acme Orders <orders@acme.com>"` |
| `to`          | Yes                     | One address, or a list of up to 50                                                   |
| `subject`     | Yes                     | 1–200 characters                                                                     |
| `text`        | One of `text` or `html` | Plain-text body, up to 100,000 characters                                            |
| `html`        | One of `text` or `html` | HTML body, up to 250,000 characters                                                  |
| `fromName`    | No                      | Display name for the From address (longer than 120 characters is cut)                |
| `replyTo`     | No                      | One address or a list                                                                |
| `cc`, `bcc`   | No                      | One address or a list. `to`, `cc` and `bcc` together: at most 50 unique addresses    |
| `attachments` | No                      | Up to 20 items of `{"filename": "...", "content": "<base64>"}`, 40 MB in total       |
| `headers`     | No                      | Up to 50 extra headers, as `{"Name": "value"}`                                       |
| `tags`        | No                      | Up to 50 items of `{"name": "...", "value": "..."}`                                  |
| `scheduledAt` | No                      | An ISO 8601 time in the future, up to 30 days ahead                                  |

### Examples

**`cURL`**

```bash title="cURL"
curl https://ibee-email-send-api-prod.bifrosts.workers.dev/v1/emails \
  -H "Authorization: Bearer $IBEE_EMAIL_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: order-1042-confirmation" \
  -d '{
    "from": "orders@acme.com",
    "fromName": "Acme Orders",
    "to": "buyer@example.com",
    "replyTo": "support@acme.com",
    "subject": "Your order is confirmed",
    "text": "Thank you for your order.",
    "html": "<p>Thank you for your order.</p>"
  }'
```

**`Python`**

```python title="Python"
import os

import requests

response = requests.post(
    "https://ibee-email-send-api-prod.bifrosts.workers.dev/v1/emails",
    headers={
        "Authorization": f"Bearer {os.environ['IBEE_EMAIL_API_KEY']}",
        "Idempotency-Key": "order-1042-confirmation",
    },
    json={
        "from": "orders@acme.com",
        "fromName": "Acme Orders",
        "to": "buyer@example.com",
        "subject": "Your order is confirmed",
        "text": "Thank you for your order.",
    },
    timeout=30,
)
response.raise_for_status()
print(response.json()["id"])
```

**`Node.js`**

```javascript title="Node.js"
const response = await fetch("https://ibee-email-send-api-prod.bifrosts.workers.dev/v1/emails", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.IBEE_EMAIL_API_KEY}`,
    "Content-Type": "application/json",
    "Idempotency-Key": "order-1042-confirmation",
  },
  body: JSON.stringify({
    from: "orders@acme.com",
    fromName: "Acme Orders",
    to: "buyer@example.com",
    subject: "Your order is confirmed",
    text: "Thank you for your order.",
  }),
});

const result = await response.json();
if (!response.ok) {
  throw new Error(`${result.error.code}: ${result.error.message}`);
}
console.log(result.id);
```

### Verify it worked

A successful request returns `202 Accepted`: the message is queued, not yet delivered.

```json
{
  "id": "msg_Xk3v9Qp2LmN7tRzA",
  "status": "accepted",
  "duplicate": false
}
```

Open **Emails** and find the message by its `id`. Its status moves from **Accepted** to **Delivered** (or **Bounced**). With a **Sending + read** or **Read only** key, `GET /v1/emails/{id}` returns the same status.

### Retries and the Idempotency-Key

If a request times out or the network fails, send it again with the **same** `Idempotency-Key`. When the key was already used in the workspace, the API returns the first message's `id` with `"duplicate": true` and doesn't send a second copy. Without the header, IBEE makes a new key for every request, so a retry can send the message twice.

Build the key from your own records, such as `order-1042-confirmation`, and use a new one for every distinct email.

### Send several emails at once

`POST /v1/emails/batch` takes a JSON **array** of 1–100 message objects, each shaped like the body above, and returns `202` with `{"data": [{"id", "status", "duplicate"}, …]}`. Give each item its own `idempotency_key`. If one item is invalid, the request stops there and returns that item's error; items before it are already accepted.

## Send over SMTP

Use these settings in software that sends mail over SMTP (also shown under **Settings → SMTP**):

| Setting    | Value                                            |
| ---------- | ------------------------------------------------ |
| Host       | `smtp.ibee.email`                                |
| Port       | `465`                                            |
| Encryption | SSL/TLS (implicit TLS, not STARTTLS)             |
| Username   | `ibee`                                           |
| Password   | An Email Service API key with **Sending access** |

The From address must be a registered sender on an **Active** domain. SMTP messages count toward the same limits and appear in **Emails** like API messages.

## Track delivery

**Emails** lists every message from the workspace with **To**, **Status**, **Subject**, **From** and **Sent**. It shows the last 15 days by default; filter by text, **Status**, **Domain** and time. Click a message for its delivery timeline and content.

| Status        | Meaning                                                                        |
| ------------- | ------------------------------------------------------------------------------ |
| **Accepted**  | The API accepted the message                                                   |
| **Queued**    | Waiting to be sent                                                             |
| **Submitted** | Handed to the recipient's mail server                                          |
| **Deferred**  | Temporarily refused; IBEE is retrying                                          |
| **Delivered** | The recipient's mail server accepted it                                        |
| **Bounced**   | Permanently rejected. The address is added to the suppression list.            |
| **Rejected**  | Rejected; it won't be delivered                                                |
| **Failed**    | Couldn't be sent                                                               |
| **Complaint** | The recipient marked it as spam. The address is added to the suppression list. |

**Logs** lists API requests made with the workspace's keys (**Endpoint**, **Status**, **API key**, **Duration**, **User agent**, **Created**); request bodies aren't stored. **Metrics** shows sent, delivered, bounce and complaint figures for the last 24 hours, 7, 30 or 90 days.

To check your setup without code, click **Send test email** in **Overview** or **Emails**. Test emails are real messages and count toward your limit.

## Suppressions

The suppression list holds addresses the workspace won't send to. Open **Emails** and switch to **Suppressions**. Bounced and complaining addresses are added automatically; **Add address** adds one by hand. **Remove from list** takes an address off, but sending again to an address that bounced or complained can hurt your sender reputation. If it bounces or complains again, it is added back.

## Webhooks

A webhook sends each delivery event to an HTTPS address in your application, so you don't have to poll.

### Add an endpoint

In **Webhooks**, click **Add endpoint**. Enter a public `https://` **Endpoint URL**, such as `https://api.acme.com/webhooks/email`, and choose the **Events**. Click **Add endpoint**.

### Save the signing secret

The **Save your signing secret** dialog shows it once. Store it on your server, tick **I've saved the secret**, and click **Done**.

| Event              | Sent when                                   |
| ------------------ | ------------------------------------------- |
| `email.delivered`  | The recipient's server accepted the message |
| `email.deferred`   | Delivery was delayed and is being retried   |
| `email.bounced`    | The message bounced permanently             |
| `email.rejected`   | The message was rejected                    |
| `email.failed`     | The message couldn't be sent                |
| `email.complained` | The recipient reported it as spam           |

Each delivery is a `POST` with a JSON body such as:

```json
{
  "id": "evt_4fT8wQm1ZkP0sVnB",
  "type": "email.bounced",
  "createdAt": "2026-10-01T09:30:12.000Z",
  "data": {
    "messageId": "msg_Xk3v9Qp2LmN7tRzA",
    "from": "orders@acme.com",
    "to": "buyer@example.com",
    "subject": "Your order is confirmed",
    "status": "bounced",
    "smtpStatusCode": "550",
    "smtpResponse": "5.1.1 User unknown"
  }
}
```

**Delivery rules:** answer with any `2xx` status within 15 seconds. Redirects aren't followed. Timeouts, network errors and `408`, `425`, `429` or `5xx` answers are retried, up to 7 attempts, with the wait doubling from 5 seconds. The same event can arrive twice: skip events whose `x-ibee-event-id` you have already handled. Events that happen while an endpoint is disabled are never sent.

**Check the signature** before trusting a delivery. Each request has `x-ibee-signature` (`v1=` plus a hex HMAC-SHA256 signature, a fingerprint made with your signing secret), `x-ibee-timestamp` (Unix seconds) and `x-ibee-event-id`. Compute HMAC-SHA256 of `timestamp + "." + rawBody` with your secret, compare it with the value after `v1=` in constant time, and reject timestamps more than 5 minutes old.

**`Python (Flask)`**

```python title="Python (Flask)"
import hashlib
import hmac
import os
import time

from flask import Flask, abort, request

app = Flask(__name__)
SECRET = os.environ["IBEE_WEBHOOK_SECRET"].encode()


@app.post("/webhooks/email")
def ibee_email_webhook():
    raw_body = request.get_data()
    timestamp = request.headers.get("x-ibee-timestamp", "")
    signature = request.headers.get("x-ibee-signature", "")

    if not timestamp.isdigit() or abs(time.time() - int(timestamp)) > 300:
        abort(400)
    expected = hmac.new(SECRET, timestamp.encode() + b"." + raw_body, hashlib.sha256).hexdigest()
    if not signature.startswith("v1=") or not hmac.compare_digest(signature[3:], expected):
        abort(400)

    event = request.get_json()
    print(event["type"], event["data"].get("messageId"))
    return "", 204
```

**`Node.js (Express)`**

```javascript title="Node.js (Express)"
import crypto from "node:crypto";
import express from "express";

const app = express();
const SECRET = process.env.IBEE_WEBHOOK_SECRET;

app.post("/webhooks/email", express.raw({ type: "application/json" }), (req, res) => {
  const timestamp = req.get("x-ibee-timestamp") ?? "";
  const signature = req.get("x-ibee-signature") ?? "";

  const fresh = Math.abs(Date.now() / 1000 - Number(timestamp)) <= 300;
  const expected = crypto.createHmac("sha256", SECRET).update(`${timestamp}.`).update(req.body).digest("hex");
  const received = signature.startsWith("v1=") ? signature.slice(3) : "";
  const valid =
    received.length === expected.length &&
    crypto.timingSafeEqual(Buffer.from(received), Buffer.from(expected));
  if (!fresh || !valid) return res.sendStatus(400);

  const event = JSON.parse(req.body.toString("utf8"));
  console.log(event.type, event.data.messageId);
  res.sendStatus(204);
});

app.listen(3000);
```

Open an endpoint to **Edit** it, **Send test event**, **Disable** or **Enable** it, or **Rotate secret** (the old secret stops working at once). **Deliveries** shows each attempt and its last error.

## Limits

|                               | Value                                                                                                                                                                |
| ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Daily limit                   | Set by your plan. It counts **recipients** (every `to`, `cc` and `bcc` address), and resets at 00:00 UTC. **Overview → Emails today** shows today's count and limit. |
| Monthly allowance and domains | Set by your plan; see **Settings**                                                                                                                                   |
| Recipients per message        | 50 (`to` + `cc` + `bcc`)                                                                                                                                             |
| Messages per batch request    | 1–100                                                                                                                                                                |
| Subject                       | 1–200 characters                                                                                                                                                     |
| `text` / `html` body          | 100,000 / 250,000 characters                                                                                                                                         |
| Attachments                   | 20 per message, 40 MB in total (base64)                                                                                                                              |
| Request body                  | 42 MB                                                                                                                                                                |
| `Idempotency-Key`             | 8–256 characters                                                                                                                                                     |
| Custom headers, tags          | 50 each                                                                                                                                                              |
| Scheduling                    | Up to 30 days ahead                                                                                                                                                  |
| Domains per API key           | 1–50 (an Email Token: 1)                                                                                                                                             |
| API key name                  | 80 characters                                                                                                                                                        |
| Webhook answer time           | 15 seconds; up to 7 attempts                                                                                                                                         |
| Reputation targets            | Bounce rate below 2%, complaint rate below 0.05% (shown on **Overview**)                                                                                             |

A message repeated with an already-used `Idempotency-Key` doesn't count toward the daily limit.

## Troubleshooting

Errors return JSON such as `{"error": {"code": "recipient_suppressed", "message": "…"}}`. Every response has an `x-request-id` header; include it when you contact support.

| You see                                                           | What it means                                                                                     | What to do                                                                                                                                              |
| ----------------------------------------------------------------- | ------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Email Service shows only a plan page                              | The workspace has no active plan                                                                  | Choose a plan and click **Activate plan**                                                                                                               |
| Domain stuck on **Verification pending**                          | The records aren't visible yet, or don't match                                                    | Compare each record with the portal, check the name isn't doubled (`send.acme.com.acme.com`), turn off the Cloudflare proxy, then **Verify connection** |
| `401` `api_key_required`                                          | No `Authorization: Bearer` header                                                                 | Add the header                                                                                                                                          |
| `401` `api_key_invalid`                                           | The key is wrong, revoked or expired                                                              | Create a new key                                                                                                                                        |
| `403` `sender_not_allowed`                                        | The From address isn't a registered sender on an **Active** domain                                | Register the sender                                                                                                                                     |
| `403` `sender_not_allowed_by_key`                                 | The key doesn't include the sender's domain                                                       | Create a key for that domain                                                                                                                            |
| `403` `scope_missing`                                             | The key is **Read only**                                                                          | Use a key with **Sending access**                                                                                                                       |
| `403` `plan_payment_due`, `plan_suspended` or `plan_cancelled`    | The workspace's email plan is unpaid, suspended or ended                                          | Settle the payment, or choose a plan, in the portal                                                                                                     |
| `403` `tenant_inactive`                                           | Email Service isn't active for this workspace                                                     | [Contact support](/docs/support/contact-support)                                                                                                        |
| `400` `recipient_invalid`, `sender_invalid` or `reply_to_invalid` | An address is malformed, or `to` is empty or has more than 50                                     | Fix the address list                                                                                                                                    |
| `400` `recipient_limit_exceeded` or `recipient_duplicate`         | More than 50 recipients in total, or an address appears twice                                     | Split the message, or remove duplicates                                                                                                                 |
| `400` `subject_invalid` or `body_empty`                           | The subject is empty or too long, or there is no `text` or `html`                                 | Fix the subject or add a body                                                                                                                           |
| `400` `idempotency_key_invalid`                                   | The key isn't 8–256 allowed characters                                                            | Use letters, digits, `.`, `_`, `:` and `-`                                                                                                              |
| `400` `attachments_invalid` or `413` `attachments_too_large`      | An attachment has no `filename` or base64 `content`, there are more than 20, or they exceed 40 MB | Fix or shrink the attachments                                                                                                                           |
| `409` `recipient_suppressed`                                      | The address is on the suppression list                                                            | Remove it from **Suppressions** only if you're sure it's valid                                                                                          |
| `409` `domain_limit_reached` (when adding a domain)               | Your plan's domain limit is used                                                                  | **Upgrade plan**                                                                                                                                        |
| `413` `body_too_large` or `request_too_large`                     | The body or the whole request is too large                                                        | Shorten the content                                                                                                                                     |
| `415` `content_type_invalid`                                      | `Content-Type` isn't `application/json`                                                           | Set the header                                                                                                                                          |
| `429` `daily_limit_reached`                                       | Today's limit is used (`details` has `limit`, `used` and `requested`)                             | Wait until 00:00 UTC, or upgrade your plan                                                                                                              |
| `429` `quota_or_acceptance_conflict` or `500` `internal_error`    | A temporary problem                                                                               | Retry with the same `Idempotency-Key`                                                                                                                   |

## Related pages

* [API Tokens](/docs/tools/api-tokens): the Email Tokens tab and other credentials
* [Verify your identity](/docs/getting-started/account-setup/verify-your-identity): needed before any change
* [Billing and usage](/docs/platform-fundamentals/billing-and-usage): how plans are billed
* [Contact support](/docs/support/contact-support): request access or help with a domain