Domains
Add a sending hostname in the console or via API. evre shows a connection badge immediately:
| Badge | Meaning |
|---|---|
| DNS configuration required | Publish or fix the records below |
| Waiting on email provider | Public DNS looks good — SES is catching up |
| Connected | Verified and all required DNS found |
| Checking DNS… | Only while a verify request is in flight |
API flow
POST /domains— creates the domain, runs an initial DNS check, returns records + badge state- Publish DNS at your host (CNAME for DKIM, TXT for SPF, MX for return-path)
- Background checks run every few minutes;
POST /domains/{id}/verifyforces a refresh
From-addresses must use a connected domain for the active project.
SPF already on this domain?
If you send mail elsewhere (Google Workspace, MXRoute, etc.), you already have a v=spf1 TXT record. Edit it — add include:spf.evre.email — instead of creating a second SPF TXT. The console detects this and suggests a merged value.
Inbound receive
After connected, POST /domains/{id}/inbound appends inbound MX records. See Inbound email.