Domain setup
Verify ownership and configure the domain your application sends from.
An organization admin opens the console, chooses the organization, and selects Domains. Its URL is /org/{your-organization-slug}/domains. If you cannot open that page, ask an admin to complete the setup and give you the verified domain name.
Verify ownership
Add the domain to your organization. Publish the verification TXT record exactly as the console displays it, then run the ownership check. A domain on a different organization cannot be used by your key.
Ownership verification and mail hosting are separate. A verified domain that is not hosted on the Prawnwire mail server still cannot send through this API: it returns ErrorCode 401 with HTTP 422. An unverified domain returns ErrorCode 400.
Host the domain
Complete the console’s hosting setup. The domain must exist on the Prawnwire mail server so outgoing mail can be signed with that domain’s DKIM key. The API allows any From address on that verified, hosted domain; a separate mailbox is not required for each sender address.
Publish mail records
Use the exact names, priorities and values shown for your domain. Do not copy another domain’s DKIM key.
| Record | Purpose | What to check |
|---|---|---|
| MX | Routes incoming mail to the mail server | Moving MX changes where the domain receives mail. Coordinate this with the domain’s admin. |
| SPF (TXT) | Authorizes the sending servers | Maintain one SPF record, merging authorized senders rather than publishing a second record. |
| DKIM (TXT) | Lets receiving servers verify the message signature | Publish the selector and public key shown by the console. |
| DMARC (TXT) | Sets policy for SPF/DKIM alignment and reporting | Start with monitoring if you are still checking all legitimate senders, then tighten policy when ready. |
Check the result
Run the console’s DNS checks after records propagate. Ownership verification does not prove that every SPF or DMARC check is healthy. The API’s From check establishes verification and hosting; successful delivery still depends on DNS, content, recipient health, and receiving-server policy.
Send a live message to an address you control, inspect its authentication results, and read delivery events. A test key does not test SMTP submission or delivery.