Archive Data Types

Reference for every archive data_type Lirium generates and what each file contains.

Lirium generates daily reconciliation archives as CSV files. Each archive is identified by a date and a data_type, and you retrieve them with the Search Archives and Archive Details endpoints. This guide explains the data_type values available and what each file is for.

📘

Choosing a data_type

data_type is a query parameter on Search Archives and a path segment on Archive Details. When omitted on Search Archives it defaults to orders. A single date + data_type can be split across multiple files — always iterate the files array. See the Download Archive Files recipe for a complete download-and-verify loop.

Available data types

data_typeGranularityWhat it answers
ordersOne row per transactionEvery transaction that affected a settlement or Customer balance during the reporting window.
customer_balancesOne row per Customer + currencyThe balance each of your Customers held in each currency at the reporting cutoff.
settlement_balancesOne row per currencyThe balance of your pre-funding settlement account in each currency at the reporting cutoff.
cold_storageOne row per currencyHow much of each asset should be held in cold storage versus hot liquidity.

orders

The default and most detailed archive. It contains one row per transaction that affected the Banking Partner's settlement account and/or a Customer's asset account within the day's reporting window (buy, sell, send, receive, swap, settlement top-ups, withdrawals, commissions, and fees).

Use it to reconcile movements transaction by transaction. The full column list, possible values, and the transaction types that populate each field are documented in the Archives reference.

customer_balances

A snapshot of every Customer's holdings per currency as of the reporting cutoff. One row is emitted for each Customer + currency combination that has a non-zero balance.

FieldTypeRequiredDescription
customer_idstringYesId of the Customer.
reference_idstringNoThe reference id you provided for the Customer.
currencystringYesCurrency of the balance (uppercase, e.g. BTC, USDC).
balancestringYesThe Customer's balance in that currency at the cutoff.
last_movementISO 8601 stringYesTimestamp of the last transaction that affected this balance.

Use it to reconcile the per-Customer liabilities you hold against Lirium.

settlement_balances

A snapshot of your pre-funding settlement account balances per currency as of the reporting cutoff. One row per currency.

FieldTypeRequiredDescription
currencystringYesCurrency of the settlement account (uppercase).
balancestringYesSettlement account balance in that currency at the cutoff.
last_movementISO 8601 stringYesTimestamp of the last transaction that affected this balance.

Use it to reconcile the funds available in your settlement account across currencies.

cold_storage

A daily cold storage report that helps you decide how much of each asset to keep in cold storage versus available as hot liquidity. For each currency it compares your current cold storage balance against a target balance derived from your Customers' average holdings, a minimum-liquidity threshold, and a configured cold-storage percentage.

One row is emitted per currency. Amounts are expressed both in the asset's own units and in USD.

FieldTypeRequiredDescription
currencystringYesCurrency the row refers to (uppercase).
rolling_average_balancestringYesAverage total Customer balance over the rolling window.
rolling_average_customersstringYesAverage number of Customers holding the currency over the rolling window.
last_day_balancestringYesTotal Customer balance on the last day of the window.
last_day_customersstringYesNumber of Customers holding the currency on the last day.
current_balancestringYesAmount currently held in cold storage.
current_balance_in_usdstringYescurrent_balance valued in USD.
calculation_usd_pricestringYesUSD price used for the calculation.
calculation_min_liquiditystringYesMinimum USD liquidity to keep hot before allocating to cold storage.
calculation_percentage_coldstringYesConfigured percentage of the eligible balance to keep in cold storage.
calculation_min_cold_balancestringYesMinimum USD amount below which nothing is allocated to cold storage.
calculation_base_typestringYesWhich balance drove the calculation: last day or rolling.
calculation_base_balancestringYesThe balance used as the calculation base (the lower of last-day and rolling).
calculation_base_balance_in_usdstringYescalculation_base_balance valued in USD.
calculation_target_balance_in_usdstringYesComputed target cold storage amount in USD before applying the minimum.
target_balance_in_usdstringYesFinal target cold storage amount in USD.
target_balancestringYesFinal target cold storage amount in the asset's own units.
🚧

Cold storage availability

The cold_storage archive requires per-currency configuration (minimum liquidity, cold-storage percentage, and minimum cold balance) to be set up for your domain. Contact [email protected] to enable it.

Reporting window and configuration

Archives are generated per date according to your reporting_cutoff_time, reporting_window, and timezone settings. See the Archives reference for how the window is computed and how to configure it.