Domains
Authenticate a whole sending domain with DNS. Mailbox providers trust the domain, not you — the proof is DNS, and it is not optional.
Register a domain
POST /email/domains registers a domain and returns the DNS records to publish — SPF, DKIM and a tracking CNAME. A subdomain such as mail.yourcompany.com is the recommended setup: it isolates your sending reputation from the mail your team reads and writes by hand.
cURL
curl -X POST https://api.qsendyx.com/api/v1/email/domains \
-H "Authorization: Bearer $QSENDYX_TOKEN" \
-H "Content-Type: application/json" \
-d '{ "domain": "mail.yourcompany.com" }'json
{
"id": "019f70a4-3c8e-7d21-b0f4-51ac9e77b3aa",
"domain": "mail.yourcompany.com",
"status": "pending",
"records": [
{ "type": "TXT", "host": "mail.yourcompany.com", "value": "v=spf1 include:..." },
{ "type": "TXT", "host": "s1._domainkey.mail.yourc...", "value": "k=rsa; p=MIGfMA0G..." },
{ "type": "CNAME", "host": "qsy1.mail.yourcompany.com", "value": "track.qsendyx.com" }
]
}Verify and manage
Once the records propagate, POST /email/domains/{id}/verify checks them and flips the domain to verified. GET /email/domains lists them, GET /email/domains/{id} reads one, and DELETE /email/domains/{id} removes it.
cURL
curl -X POST https://api.qsendyx.com/api/v1/email/domains/{domain_id}/verify \
-H "Authorization: Bearer $QSENDYX_TOKEN"A send from an unverified identity is refused. This is not a formality: it is what stops one tenant from sending as another.