Technical notes

Registry data structure

A compact reference for the normalized registry fields used by DunaDB. Responses use a top-level data key and include pagination or lookup metadata when relevant.

Endpoints

Reference routes used by the registry interface.

Method	Path	Description	Params
GET	`/api/v1/dunas.json`	Download the static normalized DUNA registry snapshot.	None
GET	`/api/v1/dunas/7`	Fetch one DUNA record by numeric ID.	None
GET	`/api/v1/financials/7`	Fetch static balance sheet and income statement rows.	None
GET	`/api/v1/platforms`	List governance platform lookup values.	None
GET	`/api/v1/administrators`	List administrator lookup values.	None

Example request

curl "/api/v1/dunas.json"

Example response shape

{
  "data": [
    {
      "id": 7,
      "displayName": "DUNI",
      "projectName": "Uniswap",
      "tokenSymbol": "UNI",
      "links": {},
      "registration": {
        "date": "2025-10-06"
      },
      "financialCoverage": {
        "hasFinancials": true,
        "balanceSheetRows": 29,
        "incomeStatementRows": 38
      }
    }
  ],
  "meta": {
    "total": 1,
    "limit": 50,
    "offset": 0
  }
}

Source and freshness

DunaDB currently serves read-only data aggregated into the dunadb Postgres schema at build time. Canonical edits happen outside this frontend, and deployed data changes only after a new static build. Registration dates are normalized from source filing records when available. Financial statement values are returned as strings to preserve decimal precision.