Crassula creates a daily backup of your data. You can download it through the API.
Downloading a backup
GET /api/backups/{date}
-
{date}is the day of the backup inYYYY-MM-DDformat, for example2026-11-01. -
Authenticate with a master API key, as described in Using Crassula API. Pass it in the
Authorizationheader.
Responses:
-
302: redirects to the backup file. The link is valid for 2 hours, so download the file right away. -
401: the API key is missing or invalid. -
403: the key is valid but is not a master key. -
404: no backup exists for this date. -
422: the date is invalid.
Example:
curl -L -H "Authorization: <your API key>" \
"https://client.demo.crassu.la/api/backups/2026-11-01" -o 2026-11-01.zip
Backups are kept for 7 days. A request for an older date returns 404.
The backup for a given date is created at 00:04 UTC on the next day and contains the data as of that moment. For example, the backup for 2026-11-01 appears on 2026-11-02 after 00:04 UTC.
File format
The backup is a ZIP archive named YYYY-MM-DD.zip after the backed-up day. Each table below is a separate gzip-compressed CSV file inside the archive, named after the table: <table name>.csv.gz (for example, account_transaction.csv.gz). Each CSV file starts with a header row of column names; values are comma-separated and quoted where needed.
Most fields with a fixed set of values contain the number shown in brackets. For example, state = 8 means COMPLETED. In transaction_state_transition_event, state_from is -1 (UNDEFINED) for the first event of a transaction.
The following fields contain text values instead: client.risk_level (low, moderate, moderately-high, high, prohibited), account.provider_name, account_provider_number.requisites_type (for example swift, sepa) and issued_card.provider.
What is not included
The daily backup contains the main data: clients, accounts, transactions, cards and price lists. It does not include the data listed below.
Not in the backup
-
KYC files and documents. The files themselves (passport scans, company documents) are kept in file storage, not in the database, so they are not exported. The tables describing them are not included either:
identification_request*,document,document_file,client_document. -
Company structure.
company_staff,shareholder_personandshareholder_company(directors and beneficial owners) are not included. Business onboarding applications (business_application,application_*) are not included. -
Consent to legal documents.
legal_document_client_agreementis not included, so the backup does not show who agreed to which version of the terms, and when. -
Notes and comments.
client_note,issue_note,account_transaction_comment. -
Saved beneficiaries and transfer templates.
counterparty,transfer_template. -
Cards. Only
issued_cardis included. Card holds (issued_card_hold_transaction), card limits and card products are not. -
Fee charges.
client_fee_chargeis not included. Price lists are in the backup, actual fee charges are not. -
Other. Travel Rule data (
travel_rule_transaction*), two-factor authentication methods, referral codes, membership and tags. -
Administrators. The backup contains
administrator_id(inissue,activity_logand transaction approvals), but not theadministratortable. These IDs cannot be matched to administrator records. -
Logs. See the Logs section below.
Data stored by providers
Data that is stored by third-party providers rather than by Crassula is not part of the backup: onboarding questionnaires and verification checks at the identity verification provider (SumSub), card data at the card processor, and statements at the banking providers. Obtain this data directly from the provider.
Banking
|
Table name |
Fields |
Description |
|---|---|---|
|
client |
|
Clients |
|
client_metadata_item |
|
Clients' metadata |
|
client_limit |
|
Limits |
|
client_limit_threshold |
|
Limit thresholds |
|
person |
|
Clients / persons |
|
person_phone |
|
Persons' phone numbers |
|
person_email |
|
Persons' email addresses |
|
company |
|
Clients / companies |
|
account |
|
Accounts |
|
account_metadata_item |
|
Accounts' metadata |
|
account_provider_number |
|
External account numbers |
|
account_transaction |
|
Transactions |
|
account_transaction_parameter |
|
Transactions' metadata |
|
account_transaction_bank_details |
|
Beneficiary requisites for outgoing transactions and remitter requisites for incoming transactions |
|
transaction_state_transition_event |
|
Transaction state change history |
|
account_transaction_approval |
|
Administrators' approvals of transactions |
|
subscription_plan |
|
Subscription plans (not used; |
|
client_price_list |
|
Price lists |
|
client_fee |
|
Price list fees |
|
issued_card |
|
Issued cards |
|
issue |
|
Issue management |
E-commerce
Tables
|
Table name |
Sample field list |
Description |
|---|---|---|
|
merchant |
|
Merchants |
|
project |
|
Merchant projects |
|
transaction |
|
Project transactions |
|
fee |
|
Fees |
Exchange
|
Table name |
Sample field list |
Description |
|---|---|---|
|
exchange_order |
|
Exchange orders |
|
exchange_rate_history |
|
Exchange rate history |
Logs
|
account_log |
|
Account logs |
|
account_transaction_log |
|
Transaction logs |
|
issued_card_activity_log |
|
Issued card logs |
|
activity_log |
|
Administrators' audit log |
|
http_request_log |
|
HTTP request logs |
|
entity_change_log |
|
Record change logs |