List forwards this company rejected
Emails that reached this company’s forwarding address but were not accepted, because the sender is not on the allowlist or the message failed email authentication. Only metadata is kept — the attachments are not stored. This is where a new company’s first forwards land, so it is the place to find out who is trying to send and allow them.
Authentication. An API key (x-dolfin-api-key) or a JWT Bearer token. When your credential grants access to more than one client, select one with the x-dolfin-client-id header.
Authorizations
An API key issued to your client. It carries the client's scope; org-scoped calls also require the x-dolfin-organisation-id header. Keys are created and revoked by a client administrator.
Headers
Target client. Required when your credential grants access to more than one client; omit when it resolves a single client.
Path Parameters
Query Parameters
Maximum rejections to return, newest first. 1-100, default 20.
Response
OK
The sender the dropped forward came from.
Number of attachments on the dropped email.
Short 'name (type)' summary of the attachments — the bytes are not stored.
Why it was dropped: SenderNotAllowed or AuthenticationFailed.
SenderNotAllowed, AuthenticationFailed Overall email-auth (DKIM/DMARC) verdict for the sender: Pass, Fail or Unknown.
Unknown, Pass, Fail Aligned-DKIM check: Pass (valid signature from the sender's domain), Fail, or Unknown. Render as a per-check tick/cross.
Unknown, Pass, Fail Aligned-SPF check: Pass (SPF passed for the sender's domain), Fail, or Unknown. Render as a per-check tick/cross.
Unknown, Pass, Fail When the dropped forward was received.