Skip to main content
API
Asset Manager Roles
Added fields to /v4/assets that show every manager role named in an asset’s fund documents, and the strategy manager under its own name: the firm whose strategy and brand the investor is buying.
  • strategy_manager_id and strategy_manager: the strategy manager. Filter with strategy_manager_id, strategy_manager_name and strategy_manager_slug wherever the matching manager_* filter exists, and group with groupBy=strategy_manager in asset and token aggregates, time series and fund flows.
  • legal_manager_id and legal_manager: the manager named in the fund documents of the asset’s own pool. It can differ from strategy_manager, for example when a licensed platform is the named manager of a feeder fund.
  • strategy_manager_source: which role decided strategy_manager. One of LEGAL_MANAGER, SUB_ADVISOR, MASTER_FUND or UNDERLYING.
  • management_company_id: the management company or AIFM of the asset’s own pool, if any.
  • literal_structure: the asset’s own legal manager, sub-advisor and management company, its master fund and, for third-party wrappers, its underlying asset, each with their own roles.
strategy_manager_id, legal_manager_id and strategy_manager_source can be filtered and appear in /v4/assets/meta. legal_manager_name and legal_manager_slug can also be used to filter and sort. In the reference data catalog, the Manager entry is now Strategy Manager and points at strategy_manager_id.Example: feeder funds credited to their master fund’s strategy manager:
Deprecated: manager, manager_id, groupBy=manager and the manager_id, manager_name and manager_slug filters. They equal the strategy manager and keep working for now; move to the strategy_manager fields, or on /v4/assets to legal_manager when you mean the manager named in the fund documents.See Manager Attribution for how the strategy manager is chosen, and Manager roles and Literal structure object in the Assets Schema.
API
Token Catalog Timestamps
Added _created_at and _updated_at to tokens in /v4/tokens and to the tokens nested in /v4/assets. Both are UTC timestamps with an offset, such as 2025-12-06T08:58:13.124+00:00. Both can be filtered with the date operators and used as sort fields, like the asset _created_at filter.
  • _created_at is when the token was added to the RWA.xyz catalog.
  • _updated_at is currently the time of the latest daily catalog publish, so every token shares one value. It will later become the time the token was added or its catalog data last changed; a future entry will announce that change.
_updated_at describes the catalog record, not metrics: it is not the date of market value, supply, holder or other measure values.Example: tokens added since November 1, newest first:
See Catalog timestamps in the Tokens Schema, and the same section in the Assets Schema for the asset fields.
APIDataMethodology
Corporate Actions & Rebasing Tokens
Added rebase_transfer_unit to tokens in /v4/tokens and /v4/assets. It is shares when a rebasing token’s transfers move raw shares, amounts when they move already-rebased amounts, and null when the token does not rebase.Fund flows now value tokens with a shares transfer unit at ending NAV × ending rebase multiplier, so net flows reconcile with circulating asset value. Total supply is now raw supply × that day’s rebase multiplier, and daily asset performance compounds rebase multiplier changes.See Corporate actions & rebasing for the methodology.
APIData
Asset Performance Measures
Added daily_asset_performance_rate (measure 90), a one-calendar-day return expressed in percentage points, and six derived return fields to /v4/assets:
  • 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
Period returns compound daily rates rather than summing them. hypothetical_10_000_performance is the ending value of an investment anchored at $10,000 at inception—not profit—and is calculated as 10000 × (1 + since_inception_return_percent / 100).See Asset performance metrics for the methodology and the Assets Schema for the field reference.
API
Token Issuance Type
Added issuance_type field to differentiate natively issued tokens from bridged tokens. The classification is inherited from the token’s platform.Allowed values: NATIVE, BRIDGEWhere it appears:
  • On each token object (top-level issuance_type field)
  • Inside the nested platform object on each token
  • On assets: native_token_count, bridge_token_count, has_native_tokens, has_bridge_tokens
Filtering example — get only bridged tokens:
See the Tokens Schema and Assets Schema for the full field reference.
Data
Asset Classification Framework
Introduced a new asset classification framework to provide more granular coverage of credit and fund strategies. Read the full announcement.New asset classes:
  • Venture Capital
  • Asset-Backed Credit
  • Diversified Credit
  • Specialty Finance
Removed asset classes:
  • “Credit” and “Institutional Funds” have been removed. Assets previously under these classes have been re-classified into the new classes above.
Renamed asset classes:
  • “Corporate Bonds” → Corporate Credit
  • “Public Stocks” → Stocks
  • “Actively-Managed Strategies” → Active Strategies
New pages:Removed pages:
  • app.rwa.xyz/private-credit and app.rwa.xyz/institutional-funds have been removed. Their data is now covered under the new pages above.