Lifecycle
1
Register
Add the domain in the console or via
POST /v1/domains. Inboundr
creates an email identity and returns the DNS records to publish.2
Publish DNS records
Add the returned MX record (routes inbound mail to Inboundr) and the
DKIM CNAME records (verify you own the domain) at your DNS host.
3
Verify
Inboundr re-checks DNS every few minutes. When DKIM is observed, the domain’s
status becomes verified and mail can flow. Fetching a pending domain via
the API also triggers a fresh check.Verification status
Catch-all
Every verified domain accepts mail on any local part by default — there’s no need to pre-create each address. Set a domain’s catch-all endpoint to deliver all otherwise-unrouted mail to a single webhook endpoint:"catchAllEndpointId": null to clear it. An explicit
address route always takes precedence over catch-all.
Deleting a domain
Deleting a domain removes its email identity and stops mail from being processed immediately. Stored emails are retained, but nothing new will be accepted.Domains API
List, create, inspect, update catch-all, and delete domains.
Catch-all fan-out
A domain’s catch-all works the same as an address route: attach a webhook endpoint and mail to any address without an explicit route goes to it; with nothing attached, unrouted mail is dropped.catchAllEndpointId spelling still works; [] turns the
catch-all off.