List receiving domains
Every receiving domain in the org, with its verification state, the DNS records that verify it, and its webhook configuration. Unpaginated: a receiving domain is a subdomain whose MX a person publishes by hand, so an org has a handful.
status is DNS verification and webhook.status is publication — has
what SendOps holds reached the config object your intake function reads.
They move independently and neither implies the other.
webhook never carries the HMAC secret. That is returned exactly once,
by the call that mints it.
Responses
Errors follow the RFC 7807 problem format — see the error reference.
data array<object> required Each entry in data:
domain string required id string<uuid> required status string enum required error means a CHECK could not be performed — a resolver failure, an SES call that failed — and is NOT "the record is missing", which is pending_dns. Polling continues either way, so error is never terminal.
One of: pending_dns, verified, error
last_error string optional The first thing missing or wrong, in plain words. Absent on a verified domain.
region string required The RECEIVING region — the region of the stack carrying the inbound module, and the region whose SES endpoint your MX must name.
cross_region boolean required True when the receiving region differs from the account's sending region. A fact to state, never an error: only 22 AWS regions receive mail at all.
mx_verified_at string<date-time> optional identity_verified_at string<date-time> optional records array<object> required The copy-paste DNS instruction set. SendOps will never publish these for you — it holds no DNS credentials — so this list is the whole of what turns pending_dns into verified.
Each entry in records:
type string enum required One of: MX, CNAME
name string required value string required verified boolean required webhook object | null required Null when no webhook is configured.
Fields of webhook:
url string<uri> required allow_patterns array<string> required Local-part globs — support, ticket-*. EMPTY MEANS EVERY RECIPIENT AT THE DOMAIN IS DELIVERED, which is the opposite of how an empty list usually reads and is the most consequential field on this shape. A recipient that matches nothing in a non-empty list is recorded as no_route.
spam_posture string enum required tag delivers a message SES marked as spam, with the verdict stated in the payload; drop records the outcome and delivers nothing.
One of: tag, drop
virus_posture string enum required One of: tag, drop
status string enum required pending means the routing has not been re-published yet, which normally closes within seconds. invalid means the URL failed re-validation at publish time — most often a host that stopped resolving, or one that now resolves to a private address — so the domain was left out of the routing entirely; error says which.
One of: unset, pending, published, invalid
error string optional published_at string<date-time> optional created_at string<date-time> required pagination object required Fields of pagination:
has_more boolean required next_cursor string | null optional code is internal_error. The
request_id field can be quoted to SendOps support to investigate.
application/problem+json