Export the account
Ask for a file holding everything in the chosen vaults, or in every vault of the account.
The file holds every contact, value, relationship, life event, reminder and file of those vaults, sensitive fields included, and it is not encrypted. Only a key holding the sensitive fields scope can ask for one: any other key answers 403. A key minted for everything does not count, the scope has to be asked for by name.
The file is prepared in the background. Ask for the export until its status is ready, then download it with GET /exports/{accountExport}/download.
An account prepares one export at a time. Asking for another while one is being prepared answers 422.
Body parameters
Sent as JSON. Anything not listed here is ignored.
The vaults to put in the file, each named by its slug or its id. Leave it out to export every vault of the account. An empty list answers 422, and a vault of another account answers 404.
Returns
The export object, being prepared.
The export.
Always account_export. It names the kind of record, so a caller holding several kinds can tell them apart without looking at where they came from.
The id of this record, as a string even when it reads as a number. It is what every endpoint naming this record takes.
Everything the record holds.
Where the export stands: preparing, ready, failed or expired. The file is prepared in the background, and an email says when it is ready.
The vaults the file holds.
The id of one of those vaults. A vault deleted since the export was asked for is left out.
The size of the file in bytes, or null until it is ready.
When the file was complete, as a count of seconds since 1970, or null until it is ready.
When the file is deleted, seven days after it was ready unless a newer export of the account is ready first, as a count of seconds since 1970, or null until it is ready. From that moment it can no longer be downloaded.
When the export was asked for, as a count of seconds since 1970.
Where to find this record.
The absolute address this record is read from.
Rate limit
Sixty requests per minute, per user, shared by every key and device. Every answer carries the budget left in X-RateLimit-Remaining.
Keys act as you, with exactly the access you have. Make one per integration so you can revoke it alone.