Skip to main content
POST
Add Sending Domain
Add a sending domain to the authenticated company. Publish every record returned in website.dnsRecords before running verification. Newly added domains always return the unified Sequenzy record set (Sequenzy MX/SPF plus required DMARC). 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 and inbound-reply shape. For a legacy custom reply domain, run Verify Sending Domain after publishing its inbound MX. If that reply hostname needs separate ownership verification, the result includes dnsRecords.inboundVerificationRecord. Publish its TXT and verify again. Sending readiness and reply-routing readiness are separate; use dnsRecords.inboundRoutingStatus for replies. Existing reply addresses remain unchanged.
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.

Responses