Stop tracking a receiving domain
Irreversible, and classified destructive — a test-environment credential is refused.
Mail is arriving at this domain right now. The MX record is yours;
SendOps never wrote it and cannot remove it. Deleting the row
re-publishes the routing without the domain, so within about a minute
your intake function stops recognising it and parks every message as
unknown_domain. Nothing is lost — the raw mail keeps landing in your
own bucket — but delivery stops, and no call undoes it: re-adding the
domain is a new row, a new webhook and a new secret to deploy.
The SES identity is deliberately left in place. It is per-region and shared by every use of the domain in that region, so deleting it to tidy up our row could stop your own sending, or a sibling org's.
Path parameters
domain string required The receiving domain, by NAME (in.acme.com). A UUID is also accepted. Matched case-insensitively, and scoped to the calling org — a domain belonging to another org is a 404, never a 403.
Responses
Errors follow the RFC 7807 problem format — see the error reference.
code: invalid_scope), or it is bound to the test environment and this operation is irreversible (code: test_environment_forbidden). Branch on code: the first is fixed by granting the scope, the second only by using a live credential. See the "Live and test credentials" section of the API description. application/problem+json code is internal_error. The
request_id field can be quoted to SendOps support to investigate.
application/problem+json