Find out why an address did or didn't get your email
Starts from the recipient, because that's what a support ticket gives you. Reads your suppression list and your 5 most recent messages to the address, and returns one plain answer with what to do next. The address goes in the body so it never appears in a request path or an API log. Mail to other addresses, and other accounts, is never read.
bearerAuthAuthorizationBearer <token>API key sent as Authorization: Bearer <key>. Looked up by SHA-256
hash (email_core::sha256_hex) against api_keys.hash; revoked
keys and keys belonging to a suspended tenant are rejected. See the
top-level Authentication section for permission levels.
application/json- body
email*stringThe recipient to look up.
emailThe diagnosis. diagnosis is the answer for the latest message.
application/json- response
email*stringsuppressed?|Set when this address is on your suppression list.
diagnosis*Did this email arrive, and if not, why?
messages*array<>Your latest messages to this address, newest first (at most 5).
curl -X POST 'https://api.emitd.com/v1/diagnose' \ -H 'Content-Type: application/json' \ -d '{ "email": "jane@example.com"}'{ "email": "jane@example.com", "suppressed": { "reason": "hard_bounce", "created_at": 1761955200000 }, "diagnosis": { "state": "bounced", "summary": "The recipient's mail server rejected it permanently, so we've stopped sending to this address.", "next_step": "Check the address for a typo, and ask for a correct one. Sending to a dead address again hurts your domain's reputation." }, "messages": [ { "id": "msg_1", "subject": "Your receipt", "status": "sent", "created_at": 1761955100000, "diagnosis": { "state": "bounced", "summary": "The recipient's mail server rejected it permanently, so we've stopped sending to this address.", "next_step": "Check the address for a typo, and ask for a correct one. Sending to a dead address again hurts your domain's reputation." } } ]}