Skip to main content
Pre-release — contact your Fortary account team for access.
Illustrative reference. These examples show the shape of the API and are provided for early evaluation while it is still being finalized. Field names and response details may change before the API is released. A complete reference, generated directly from the live API, will replace these examples once it is available.
GET /v1/vaults/{vaultId}/balances Lists the asset balances held by a vault, across the networks it operates on. Requires the vault:read scope.

​
Request

curl https://customer-api.fortary.io/v1/vaults/vault_3f8a2c1d9b/balances \
  -H "Authorization: Bearer fkc_..."

​
Response

{
  "data": [
    {
      "asset": "Ethereum/native",
      "network": "Ethereum",
      "symbol": "ETH",
      "amount": "12.48"
    },
    {
      "asset": "Ethereum/erc20:0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48",
      "network": "Ethereum",
      "symbol": "USDC",
      "amount": "250000.00"
    },
    {
      "asset": "Bitcoin/native",
      "network": "Bitcoin",
      "symbol": "BTC",
      "amount": "3.50000000"
    }
  ],
  "pagination": {
    "limit": 100,
    "nextCursor": null
  }
}
Each item in data is a balance:
  • asset — the structured asset identifier ({network}/{tokenType}[:{address}]).
  • network — the network the balance is held on, as a friendly name.
  • symbol — the asset’s ticker symbol.
  • amount — the balance, as a string. Parse it with a decimal library, never a float — see Identifiers & data formats.
To page through a longer list, pass nextCursor back — see Pagination. Errors follow the standard error envelope.