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/assets Lists the assets Fortary supports. Requires the vault:read scope.

​
Request

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

​
Response

{
  "data": [
    {
      "id": "Ethereum/native",
      "symbol": "ETH",
      "name": "Ether",
      "decimals": 18,
      "network": "Ethereum"
    },
    {
      "id": "Ethereum/erc20:0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48",
      "symbol": "USDC",
      "name": "USD Coin",
      "decimals": 6,
      "network": "Ethereum"
    }
  ],
  "pagination": {
    "limit": 100,
    "nextCursor": null
  }
}
Each item in data is an asset:
  • id — the structured asset identifier ({network}/{tokenType}[:{address}]).
  • symbol — the asset’s ticker symbol.
  • name — the asset’s full name.
  • decimals — the number of decimal places the asset’s smallest unit divides into.
  • network — the network the asset belongs to, as a friendly name.
To page through a longer list, pass nextCursor back — see Pagination. Errors follow the standard error envelope.