Export the Message Store for Compliance
A 3-step recipe with RingCentral. We can help you get access.
Recipe · 3 steps
Export the Message Store for Compliance
with RingCentral
Request, poll, and download a bulk message store export.
- Request the message store report for the date range. RingCentral accepts the request asynchronously and returns a task resource whose id drives the rest of the flow.
- Poll the export task until it completes. The archive is not retrievable while the task is still Accepted or InProgress, so this step repeats until the task reports a terminal status.
- Retrieve the finished export archive so the message history can be handed to a retention or eDiscovery system.
What you'll need to have ready
- accountId: Internal identifier of the RingCentral account. Use "~" for the account associated with the current authorization session.
- dateFrom: Start of the export window (ISO 8601).
- dateTo: End of the export window (ISO 8601).
- messageTypes: Message types to include in the export, for example SMS, Fax, VoiceMail, Pager. Omit to include all types.
For your developer
Arazzo workflow ringcentral:export-message-store, 3 operations: createMessageStoreReport → readMessageStoreReportTask → readMessageStoreReportArchive. Specs on APIs.io.