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}/addresses Lists a vault’s deposit addresses. Requires the vault:read scope.

​
Request

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

​
Response

{
  "data": [
    {
      "address": "0x3a1f9c2b8d7e6f5a4b3c2d1e0f9a8b7c6d5e4f3a",
      "network": "Ethereum",
      "assetType": "native"
    },
    {
      "address": "bc1qar0srrr7xfkvy5l643lydnw9re59gtzzwf5mdq",
      "network": "Bitcoin",
      "assetType": "native"
    }
  ],
  "pagination": {
    "limit": 100,
    "nextCursor": null
  }
}
Each item in data is a deposit address:
  • address — the on-chain deposit address.
  • network — the network the address belongs to, as a friendly name.
  • assetType — the kind of asset the address receives (for example, native).
To page through a longer list, pass nextCursor back — see Pagination. Errors follow the standard error envelope.