Native Email

Domain Not Verified 422

The sending domain exists but has not completed DNS verification.

type https://errors.swepay.com.br/native-mail/domain-not-verified

What this means

The sending domain referenced by the request exists but has not completed DNS verification, so it cannot be used to send email. The request is well-formed and the domain is known to the tenant — it is simply not in a sendable state yet.

This is a state precondition, not an input-shape problem: the body is valid, but the domain must be verified before Native Email will accept a send from it.

Common causes

The required DNS records (SPF/DKIM CNAME/TXT) have not been published yet.
The records were published but DNS has not propagated and verification has not run.
The domain was added but the verification step was never triggered.

How to resolve

Check the domain status via GET /v1/domains/{domain}.
Retrieve the required DNS records via GET /v1/domains/{domain}/dns-records and publish them at your DNS provider (SPF/DKIM CNAME/TXT).
Trigger verification via POST /v1/domains/{domain}/verify and wait until the status becomes Verified.
Retry the send once the domain is verified.

Example response

HTTP 422 · application/problem+json

{
  "type": "https://errors.swepay.com.br/native-mail/domain-not-verified",
  "title": "Domain Not Verified",
  "status": 422,
  "detail": "Domain 'mail.empresa.com.br' is not verified for tenant 'acme'.",
  "instance": "/v1/messages",
  "code": "DOMAIN_NOT_VERIFIED",
  "recovery": "Verify the domain's DNS records (CNAME/TXT) before sending email from it.",
  "requestId": "1-67a8c3f1-2b9e4d6a8c1f0e3b"
}

References

Machine-readable: /native-mail/domain-not-verified.json