Skip to main content
Only the record owner can export data; care-circle read access does not include bulk export. Authenticate with your deployment’s account token, as in the HTTP API example.

What you can export

The web client offers the readings export on your own record.

Export with curl

The example uses the local Docker demo and its demo account; a real deployment signs in the way its users do.
1

Get a token

2

Download the readings as CSV

The first line names the columns, the standardized value and unit among them.
3

Stream the record as NDJSON

The last line is the footer: "complete": true with the row count per dataset. A file whose last line is not a footer was cut off, and a footer with "complete": false names the dataset that changed while it streamed; run it again.

Scope of the export

NDJSON exports the visible observations listed in its manifest. It does not include files, medications, care-circle settings or accounts, and cannot be imported as a deployment backup. Use backup and restore to move a complete deployment. Feature limits are tracked in .

The complete copy

shell/backup.sh dumps the database and archives the uploaded files, and checks that the archive’s table of contents can be read. Keep it with the matching .env: encrypted content is unreadable without the keys in it. Backup & Restore explains the volumes, and Verify and Restore a Backup walks through a rehearsal and a recovery.