Skip to main content
Browse this schema interactively in the Data Catalog. Nullable describes whether the field’s value can be JSON null in the current v4 API:
  • Yes — the source permits or produces null.
  • No — the value is always filled in: either the source defines it as non-null, or it is populated on every current record.
  • Not specified — this legacy field is not defined in the current response schema; do not assume it is returned or non-null.
This column is not a presence guarantee: field selection can omit properties, and a non-null object can contain nullable members. For nested tables, the column applies when the parent object exists. For arrays, it describes the array itself, not its elements. See Field Nullability and Presence.

Reference Data

Basic Information

Catalog Timestamps

Both fields are returned by /v4/tokens and on the tokens nested in /v4/assets responses. Values are UTC with an offset, such as 2025-12-06T08:58:13.124+00:00. Filter them with the date operators before, onOrBefore, after and onOrAfter, or with is_null and is_not_null, the same operators as the asset _created_at filter. Pass a full timestamp with an offset, such as 2026-11-01T00:00:00Z. A date-only value compares as midnight at the start of that day, so onOrBefore 2026-11-01 leaves out the rest of November 1. _updated_at is not an “as of” time for metrics. It describes the token’s catalog record: reference data such as its name, address, network, platform and classification. It says nothing about when measures such as market value, supply or holders were last calculated. For dated metric values, use the timeseries endpoints, whose points carry their dates. Current behavior: every token’s _updated_at is the time of the most recent daily catalog publish. All tokens share one value, and it moves every day whether or not the token changed, so filtering or sorting by it does not find recently changed tokens. Planned change: _updated_at will become the time the token was added or its catalog data last changed, so it will differ between tokens and can be months old. The changelog will announce when this ships. The Broadridge DLR token is entered by hand rather than loaded from the catalog, so both of its timestamps are fixed at 2025-01-01.

Token Standards & Transferability

Platform Information

protocol_id, protocol_name and protocol are deprecated. Use platform_id, platform_name and platform instead; they return the same platform, and platform also carries the platform’s tokenization_type and issuance_type. The protocol_* names remain in filters and on assets, such as the protocol_slug filter and protocol_ids, until platform_* equivalents are available.

Network Information

Parent Asset

Return fields under asset are in percentage points (2.5 means 2.5%). To sort or filter tokens by them, use the field name without the asset. prefix and fractional values (0.025 means 2.5%).

Metrics

Yield & Pricing Metrics

Supply & Circulation Metrics

Asset Value Metrics

Minting & Burning

Holder & Address Metrics

Transaction Metrics

Transfer Metrics

Deprecated Fields

These 60 fields are deprecated and will be removed in API v5. /v4/tokens and the tokens nested in /v4/assets still return them, but they are null on every token. Don’t select them or read them from token rows.
  • Status: status, asset_status and investment_status
  • Value, price and yield: net_asset_value_dollar, net_asset_value_token, price_dollar, apy_7_day, apy_30_day, daily_yield_rate, daily_yield_distributed_dollar, daily_yield_distributed_token and weighted_average_maturity
  • Performance: trailing_7_day_return_percent, trailing_1_month_return_percent, trailing_3_month_return_percent, trailing_1_year_return_percent, year_to_date_return_percent, since_inception_return_percent, daily_asset_performance_rate and hypothetical_10_000_performance
  • Market data: m2_money_stock and secured_overnight_financing_rate
  • Holders and addresses: adjusted_holding_addresses_count, trailing_90_day_active_addresses_count and trailing_365_day_active_addresses_count
  • Token flows: total_token_inflow and total_token_outflow
  • Loan, credit and capacity: funded_assets_dollar, funded_assets_token, drawndown_assets_dollar, drawndown_assets_token, principal_paid_dollar, principal_paid_token, interest_paid_dollar, interest_paid_token, written_off_principal_dollar, written_off_principal_token, recovered_assets_dollar, recovered_assets_token, defaulted_loans_amount_dollar, defaulted_loans_amount_percent, number_of_defaulted_loans, outstanding_capital_dollar, maximum_capacity_dollar and cash_drag_percent
  • Bridge volumes: daily_bridge_volume, daily_bridge_inflow_volume, daily_bridge_outflow_volume, weekly_bridge_volume, weekly_bridge_inflow_volume, weekly_bridge_outflow_volume, monthly_bridge_volume, monthly_bridge_inflow_volume, monthly_bridge_outflow_volume, trailing_7_day_bridge_volume, trailing_7_day_bridge_inflow_volume, trailing_7_day_bridge_outflow_volume, trailing_30_day_bridge_volume, trailing_30_day_bridge_inflow_volume and trailing_30_day_bridge_outflow_volume
The parent asset’s APYs and returns are in the token’s asset object (asset.apy_7_day, asset.trailing_1_year_return_percent and so on). The apy_7_day, apy_30_day and *_return_percent token filters and sorts read those parent asset values and keep working. Also deprecated and removed in v5: available_capacity_dollar, available_capacity_token, idle_capital_dollar, idle_capital_token, outstanding_principal_dollar, outstanding_principal_token, number_of_loans_funded, number_of_active_loans, cumulative_repaid_principal_dollar, cumulative_repaid_principal_token, cumulative_interest_earned_dollar and cumulative_interest_earned_token. They have values only on two legacy pool tokens.