---
title: "Add a sending domain"
method: POST
path: "/domains"
tags: ["Domains"]
---

# Add a sending domain

`POST /domains`

## Request

- Base URL: `https://api.supersendtx.com`
- URL: `https://api.supersendtx.com/domains`
- Auth: HTTP bearer

## Request body

- CreateDomainRequest
  - `name` string, required
  - `inbound_enabled` boolean: Request inbound receiving for the domain as soon as verification succeeds.
  - `inboundEnabled` boolean: Alias for inbound_enabled.

## Response `200`

Domain created with DNS records to add

- CreateDomainResponse
  - `domain` Domain, required
    - `id` string, required
    - `name` string, required
    - `status` 'pending' | 'verified' | 'failed', required
    - `created_at` string, date-time, required
    - `verified_at` string, date-time, nullable, required
    - `open_tracking` boolean, required: Open tracking preference for this domain.
    - `click_tracking` boolean, required: Click tracking preference for this domain.
    - `tls_mode` 'opportunistic' | 'enforced', required: Preferred outbound TLS behavior for this domain.
    - `inbound_enabled` boolean, required: True when SuperSend TX should accept inbound mail for this domain.
    - `inbound_status` 'disabled' | 'pending' | 'active' | 'error', required: `pending` before verification, `active` once inbound receiving is configured, or `error` when setup fails.
    - `inbound_error` string, nullable, required: Why inbound setup failed when `inbound_status` is `error`. Verify the domain again to retry.
  - `records` DnsRecord[], required
    - `type` 'TXT' | 'CNAME' | 'MX', required: DNS record type. The return path is always a single `CNAME`, set to DNS only (not proxied). Publish no other records on the return-path host.
    - `host` string, required
    - `value` string, required: Record content. For MX records, the mail server hostname (priority is in `priority`).
    - `priority` integer: MX preference when `type` is `MX` (lower is preferred).
    - `purpose` string, required: Human-readable purpose (`Domain ownership`, `DKIM`, `Return path`, `SPF`, `DMARC`, `Open/click tracking`, `Inbound receiving`)
  - `inbound_records` DnsRecord[], required
    - `type` 'TXT' | 'CNAME' | 'MX', required: DNS record type. The return path is always a single `CNAME`, set to DNS only (not proxied). Publish no other records on the return-path host.
    - `host` string, required
    - `value` string, required: Record content. For MX records, the mail server hostname (priority is in `priority`).
    - `priority` integer: MX preference when `type` is `MX` (lower is preferred).
    - `purpose` string, required: Human-readable purpose (`Domain ownership`, `DKIM`, `Return path`, `SPF`, `DMARC`, `Open/click tracking`, `Inbound receiving`)
  - `inbound_note` string, required
  - `mail_server_dns_synced` boolean: Whether mail-server DKIM/return-path records were synced into the response records
  - `mail_server_dns_error` string: Present when mail-server DNS sync failed; ownership/SPF/DMARC records are still returned

## Other responses

- `400`: Invalid domain name, or `inbound_enabled` is not a boolean
- `401`: Missing or invalid API key / session
- `403`: Plan domain limit reached (when billing is enabled)
- `409`: Domain already added to this workspace, or already owned by another workspace

---

[API](https://skmtc.dev/ranla/apis/supersend-tx-api.md) · [All operations](https://skmtc.dev/ranla/apis/supersend-tx-api/llms.txt) · [OpenAPI document](https://skmtc.dev/ranla/apis/supersend-tx-api/revisions/e3e782652f50?raw)