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 Lists the vaults the credential can access. Requires the vault:read scope.

​
Request

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

​
Response

{
  "data": [
    {
      "id": "vault_3f8a2c1d9b",
      "label": "Treasury — Operating",
      "networks": ["Ethereum", "Bitcoin"],
      "createdAt": "2026-01-14T09:32:07Z"
    },
    {
      "id": "vault_7b1e4a0c2f",
      "label": "Cold Storage — Reserve",
      "networks": ["Bitcoin"],
      "createdAt": "2025-11-02T16:05:41Z"
    }
  ],
  "pagination": {
    "limit": 100,
    "nextCursor": null
  }
}
Each item in data is a vault:
  • id — the vault’s opaque identifier (vault_…). Treat it as opaque; pass back the exact string you received.
  • label — the human-readable name given to the vault.
  • networks — the networks the vault operates on, as friendly names.
  • createdAt — when the vault was created (UTC, ISO 8601).
To page through a longer list, pass nextCursor back — see Pagination. Errors follow the standard error envelope.