Skip to main content
POST
Add Sending Domain
Add a sending domain to the authenticated company. Publish the DKIM record, the bounce records described by website.bounceRecords, DMARC when present, and the optional tracking record before running verification. Newly added domains always return the unified Sequenzy record set with required DMARC, and publish their bounce subdomain as one CNAME (website.bounceRecords.cnameRecord) that stands in for the spfRecord and mxRecord entries, so it also works where your DNS host blocks custom MX records. Verification checks SPF and MX through the CNAME. Re-adding a domain that already exists returns its stored records, which for domains created before the unified rollout can still be the legacy MAIL FROM shape. When website.dnsRecords.platformDnsRecords is present, publish those CNAMEs instead of the DKIM TXT record in byodkimRecord. Each entry has purpose (dkim, dkim_spare or ses_return_path), type, name, value, required and status. Only required entries block verification. The spare DKIM selector lets Sequenzy change the key without a DNS change from you, and the return-path CNAME, once it resolves, aligns SPF with your domain on every email. byodkimRecord stays in the response and still verifies if you publish it as a TXT record, but then a key change needs a DNS change from you. Branch on whether platformDnsRecords is present, not on when the domain was added. A sending domain does not receive mail. To receive replies and other mail on your own domain, add a receiving domain, such as support.example.com. The deprecated dnsRecords.inbound* fields appear only on domains with a reply setup from before receiving domains. Tracked links and opens use your company tracking domain, which every sending domain shares. When your company has none yet, adding a domain creates it under that domain, links.<domain> by default (links.mail.example.com for mail.example.com), and returns its CNAME in dnsRecords.trackingRecord. It is optional: the domain verifies and sends without it, and links use Sequenzy’s shared tracking domain until it verifies. Once your tracking domain works, later domains reuse it with nothing to add. website.tracking reports its status; manage it with Set Tracking Domain.
A sending domain belongs to exactly one company, so confirm the target company before adding it.
MCP clients should call add_sending_domain. The older add_website tool remains available as a compatibility alias.
Do not hard-code the example record count or provider hostnames. Treat the returned dnsRecords object as authoritative so clients work with both unified and legacy domains.

Request

string
required
Domain to add.
string
default:"rp"
Return-path (MAIL FROM) subdomain label. The return-path CNAME is published at <mailFromPrefix>.<domain>, and new domains get a second one, usually <mailFromPrefix>2.<domain> (rp2 by default). Publish the names returned in dnsRecords.platformDnsRecords. Use one DNS label of 1 to 63 letters, numbers or hyphens, without a leading or trailing hyphen; inbound is reserved. It applies only when the domain is created.
string
default:"links"
Label of the company tracking domain created under the domain, <trackingPrefix>.<domain>. When it equals mailFromPrefix, the tracking domain goes on the root instead (<trackingPrefix>.<root>). It is used only when your company has no tracking domain yet and is ignored otherwise. When the hostname is in use, the label followed by 2 to 5 is tried (for example links2); when none is free, the domain is added without a tracking domain. Change the tracking domain later with Set Tracking Domain.
Invalid labels, or a tracking label that lands on the bounce hostname, return 400. Re-adding a domain that already exists returns its stored records and ignores both labels.

Responses