Summary
Inboxes can now forward a copy of every email they receive to up to 5 verified addresses. Keep a person in the loop on what your agents receive, or copy mail into an archive or another system, without writing a webhook handler.
What’s new?
New endpoints:
POST /v0/forwarding/verificationsemails a confirmation code to an address, andPOST /v0/forwarding/verifications/confirmverifies it with that code. A verified address can be used anywhere in the organization.GET,PUTandDELETEon/v0/forwarding,/v0/pods/{pod_id}/forwardingand/v0/inboxes/{inbox_id}/forwardingread, replace and remove the addresses an organization, a pod or an inbox forwards to.
New features:
- Nearest level wins: an inbox’s list replaces its pod’s, and a pod’s replaces the organization’s. An empty list turns forwarding off at that level.
- Verified addresses only: an address receives nothing until whoever reads it confirms the emailed code.
unverifiedon the read lists the addresses still waiting. - Never forwarded: sent mail, spam, bounces, auto-replies, and mail that was already forwarded, so forwards can’t loop.
- US region only for now: forwarding runs on
api.agentmail.to.
Use cases
- Build support agents whose incoming mail also reaches a team lead’s mailbox.
- Copy every email a pod of agents receives into a compliance archive.
- Hand incoming mail to a system that already reads email, while the agent keeps working in its inbox.
See Auto-forwarding for levels, verification, and what a forwarded email looks like.
