List bill forwards awaiting sender approval
Returns recent bills forwarded to this organisation’s inbound address that were dropped because the sender is not yet allowed (or failed email authentication) — the ‘senders waiting’ feed. Each entry identifies the sender so a user can allow them. Attachments are not stored; allowing a sender imports their future forwards, not these dropped ones.
Authentication. An API key (x-dolfin-api-key) together with the x-dolfin-organisation-id header identifying the organisation, or a JWT Bearer token that carries the organisation in its claims.
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 organisation. Required when authenticating with an API key; omit for Bearer callers (resolved from the token).
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.