Skip to main content
POST
Add Receiving Domain
Add your workspace’s receiving domain, a domain or subdomain whose mail should reach your Inbox such as support.acme.com, and get the DNS records to publish. Once the records are found, every address on the domain lands in your Inbox, and replies to emails from all your sending domains come back to reply addresses on it, the same way your tracking domain serves every sending domain. Until then, replies keep using inbound.sequenzy.com. The first verification also turns Inbox on. A workspace has one receiving domain. To use a different one, remove the current one first.
Mail for a domain goes wherever its MX records point, for every address at once. If the domain already receives email somewhere else, such as Google Workspace, Microsoft 365 or Cloudflare Email Routing, the request is refused with domain_has_mailbox, because receiving it here would break that mailbox. Use a subdomain such as support.acme.com instead, which leaves your existing mailboxes on acme.com untouched. If the MX lookup gets no answer, the request fails with 503 and dns_check_failed; try again in a minute.
Publish the returned records with your DNS provider. The MX record is always listed. A TXT record at _amazonses.<domain> is listed too when Amazon SES needs proof that you own the name. Sequenzy then checks the domain automatically, or you can check right away with Verify Receiving Domain. When the name is also one of your sending domains, no TXT record is listed: the sending domain’s own Amazon SES verification covers it, so receiving starts once that sending domain is verified. If error says the domain can’t receive because of how it is set up for sending, receive on a subdomain such as support.acme.com instead. A new name is reserved for your workspace for 7 days (claimExpiresAt). If the records are not found by then, another workspace may add the name, which removes it from yours. Adding a name this workspace already has returns it unchanged with created: false and HTTP 200, without checking its MX records again, so retries are safe. Adding your first receiving domain also sets the company’s replyTrackingDomainMode to custom, so reply addresses use your receiving domain once it is verified. Requires the websites:write scope and owner or admin access. CLI: sequenzy receiving-domains add support.acme.com. MCP: add_receiving_domain.

Request

string
required
A domain or subdomain you own, such as acme.com or support.acme.com. Case and a trailing dot are ignored. Sequenzy’s own domains and email providers’ domains such as gmail.com can’t be added.

Response fields

boolean
true when the domain was added (HTTP 201), false when this workspace already had it (HTTP 200).
object
The receiving domain, with the fields described in Get Receiving Domain.

Responses

A name is domain_taken, always with the same message, when another workspace receives on it, receives or sends on a parent domain (for example acme.com for support.acme.com), or still receives on it through a sending domain set up before receiving domains. Another workspace’s claim that never verified stops counting after 7 days.