Conversation data
Know what your integration can read and retain.
Message records, mailbox content, and voice conversation text serve different purposes. Choose how your agent uses each one.
Request AccessMessage history starts with records
The messages API lists records for an identity, including direction, status, and timing. It supports filters and pagination. Reading a full message is a separate request that retrieves available content from the identity’s mailbox.
Your application can use these records to follow a conversation and investigate a failed send. Treat them as communication history, rather than automatic memory for your model.
Choose content retention per identity
The retain_content setting defaults to false and can be changed through the identity API. It controls whether email subjects are retained in message metadata and whether voice conversation text is retained for later call-detail retrieval. Subject search requires this setting.
Turning this setting off is not a promise that mailbox bodies, delivery processing, or operational records disappear. Full email content is retrieved separately from the mailbox. Changing the setting also does not erase copies your own application or a recipient already holds.
Keep the context your workflow needs
Your application supplies the context used by the agent, including the connection between an email exchange and a phone conversation. Decide what belongs in your customer system and who can access it.
Use narrowly scoped API keys for message and call access. Before relying on Mailrun as an archive, agree the retention, export, and deletion requirements for your workflow with the team. Your integration should handle content that is no longer available.
LET’S BUILD SOMETHING USEFUL
Bring us your workflow.
Access is coming soon.