Skip to content
AnyReplay
Talk to sales
Sign inStart free
Docs menu · Data export

Features

Exporting Your Organisation's Data

Download everything your organisation holds in AnyReplay as one archive: recordings, sessions, events, notes, translations, audit log, from Settings or the API.

An owner can download a copy of everything the organisation holds in AnyReplay at any time — to keep a record, to move to another tool, or before closing the organisation. Making an export deletes and changes nothing, and recording carries on while it is prepared.

Downloading it

  1. Open Settings

    In the dashboard, open Settings and scroll to Export your data, or go straight to /dashboard/settings#export.

  2. Download

    Press Download export. A small organisation's file is ready in seconds; one with many recordings can take several minutes. Keep the tab open until the file is saved.

  3. Check it

    The file is anyreplay-export-YYYY-MM-DD.tar.gz. Open README.md first. manifest.json is written last; if it is missing, the download was cut short and you should run it again.

Only owners can export, because the archive contains every recording and every member's email address. Other roles see the section and the names of the owners to ask. Each export is written to the audit log.

From the API

The dashboard calls the same route. Send it with a signed-in owner's access token and the organisation's id. There are no API keys for this route yet.

curl -H "Authorization: Bearer $ACCESS_TOKEN" \
     -H "X-Organization-Id: $ORG_ID" \
     -o anyreplay-export.tar.gz \
     https://api.anyreplay.com/v1/organization/export
ResponseMeaning
200The archive, streamed as application/gzip.
403The caller is not an owner of that organisation.
409 export_in_progressAn export of this organisation is already running. Wait for it to finish.
429 rate_limitedToo many exports of this organisation in the last hour (six by default).

What is in the archive

PathWhat it is
README.mdThe format version, a description of every file, and what is left out and why.
organization.jsonThe organisation: plan, retention, the AI switch, closure dates and usage.
members/, projects/Everyone with access, with their role; each project's settings and its public project key.
sessions/, events/, chunks/One row per recording, its tracked events and page changes, and the index of its recording chunks.
recordings/The recordings themselves, exactly as stored: gzip-compressed JSON Lines of rrweb events, one file per chunk.
assets/, images/Images that apps bundle and their recordings refer to.
notes/, translations/, translation-strings/, glossary/Your team's notes, translations of recordings, your translation memory with every correction, and glossary terms.
audit-log/The organisation's audit log, as the dashboard shows it.
argus-…/Argus session summaries, project analyses and tracked issues.
manifest.jsonRow and file counts of everything above. Written last.

Tables are JSON Lines (one JSON object per line), split into numbered parts of a few megabytes. Recordings are included as files rather than as links, so the archive still works after the organisation is closed.

Before closing an organisation

Closing an organisation takes effect after a 30-day grace period, during which an owner can still export and can call the closure off. After that, its data is deleted as described in data retention. If AnyReplay itself ever shuts down, we give at least 90 days' notice and keep the export working throughout; see about.