System value and transaction stats API reference

These endpoints report the value and transaction activity of a whole DALP system, not a single participant. A treasury dashboard reads the current total value of all indexed assets, charts how that value moved over a window, and tracks how many transfers settled in the same period. The value endpoints answer "what is the organization holding right now, and how did it get here." The transaction endpoints answer "how much settlement activity ran through the system."

All four endpoints are read-only and scoped to the active organization and system from the request context. They report indexed state; they do not move assets or change configuration. For authentication and base URL setup, see Getting started. For how the organization and system context is resolved, see Organization and system scope.

Endpoints

Every endpoint returns a JSON:API single-resource envelope with data and links.self.

The value and value-history endpoints cover the entire organization. The transaction-count and transaction-history endpoints scope to the caller's own wallet set, with an organization-wide view for callers that hold the admin permission. The scope of transaction stats section explains the difference.

Current system value

GET /api/v2/system/stats/value returns the current worth of all indexed assets in the system, expressed in the organization's base currency. It takes no query parameters.

curl "https://your-platform.example.com/api/v2/system/stats/value" \
  -H "x-api-key: YOUR_API_KEY"

{
  "data": {
    "totalValue": "1452300.00",
    "conversionReliable": true
  },
  "links": {
    "self": "/v2/system/stats/value"
  }
}

Read conversionReliable before you present a total as authoritative. When it is false, at least one asset was priced with a fallback rate, so the figure can drift from the true converted value.

System value history

The value-history endpoints return total system value as a timestamped series, so a dashboard can chart how the organization's holdings moved over time. Choose the custom-range endpoint when your interface controls the window, or the preset endpoint for a fixed trailing window.

Custom range

GET /api/v2/system/stats/system-value-histories accepts an interval of hour or day, plus from and to timestamps. from must be before or equal to to.

curl --globoff \
  "https://your-platform.example.com/api/v2/system/stats/system-value-histories?interval=day&from=2026-03-01T00:00:00.000Z&to=2026-03-07T00:00:00.000Z" \
  -H "x-api-key: YOUR_API_KEY"

Preset range

GET /api/v2/system/stats/system-value-histories/presets/{preset} returns the same shape for a predefined trailing window, so you do not compute timestamps yourself.

curl "https://your-platform.example.com/api/v2/system/stats/system-value-histories/presets/trailing7Days" \
  -H "x-api-key: YOUR_API_KEY"

{
  "data": {
    "range": {
      "interval": "day",
      "from": "2026-03-01T00:00:00.000Z",
      "to": "2026-03-08T00:00:00.000Z",
      "isPreset": true
    },
    "data": [
      { "timestamp": "2026-03-01T00:00:00.000Z", "totalValueInBaseCurrency": 1420500 },
      { "timestamp": "2026-03-02T00:00:00.000Z", "totalValueInBaseCurrency": 1438200 }
    ],
    "conversionReliable": true
  },
  "links": {
    "self": "/v2/system/stats/system-value-histories/presets/trailing7Days"
  }
}

The resolved range can differ from the window you requested. The platform pulls to back to the present if you ask for a future end, and clamps from so it never runs past to. Chart against range, not your request, so the axis matches the returned points.

Transaction activity

The transaction endpoints count TransferCompleted settlements: completed transfers of assets in the system. The count endpoint returns running and recent totals; the history endpoint adds a daily series for charting.

Transaction count

GET /api/v2/system/stats/transaction-count accepts a timeRange in days for the recent count.

curl "https://your-platform.example.com/api/v2/system/stats/transaction-count?timeRange=30" \
  -H "x-api-key: YOUR_API_KEY"

{
  "data": {
    "totalTransactions": 18432,
    "recentTransactions": 512,
    "timeRangeDays": 30
  },
  "links": {
    "self": "/v2/system/stats/transaction-count"
  }
}

Transaction history

GET /api/v2/system/stats/transaction-history returns the same totals plus a daily series, bucketed by UTC day, for the requested window.

curl "https://your-platform.example.com/api/v2/system/stats/transaction-history?timeRange=7" \
  -H "x-api-key: YOUR_API_KEY"

{
  "data": {
    "totalTransactions": 18432,
    "recentTransactions": 96,
    "transactionHistory": [
      { "timestamp": "2026-03-06T00:00:00.000Z", "transactions": 12 },
      { "timestamp": "2026-03-07T00:00:00.000Z", "transactions": 21 }
    ],
    "timeRangeDays": 7
  },
  "links": {
    "self": "/v2/system/stats/transaction-history"
  }
}

A day with no transfers does not appear in transactionHistory. Fill missing days with a zero on the client when you plot a continuous axis.

Scope of transaction stats

The value and value-history endpoints always report the whole organization. The transaction-count and transaction-history endpoints scope by caller:

• A standard caller sees transfers that involve one of their own wallets. The result counts a transfer when one of the caller's wallet addresses is a party to it.
• A caller with the admin permission sees the organization-wide transfer activity for the system.

A caller with no wallet in the system, such as an API key that has no default wallet, gets a valid empty result rather than an error: zero totals and an empty transactionHistory series. Treat an unexpected zero as a possible scope or wallet-mapping gap, not proof that the system has no settlement activity.

When to use it

Use these endpoints when you need to:

• Show the current total value of a system's indexed assets in the organization base currency.
• Chart how that total moved over a custom window or a trailing preset.
• Track completed transfer activity as a running total, a recent count, and a daily trend.
• Build a treasury or operations dashboard that reports value and settlement activity for a whole system.

To read the authenticated participant's own portfolio value and asset-type breakdown instead of the system total, see Portfolio statistics.