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}/transactions Lists a vault’s transaction history, most recent first. Requires the vault:read scope.

​
Request

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

​
Response

{
  "data": [
    {
      "hash": "0x9f2c4b7a1e8d3c0f5a6b2d9e4c1f8a7b3e0d6c9a2f5b8e1d4c7a0f3b6e9d2c5a",
      "network": "Ethereum",
      "status": "confirmed",
      "direction": "outbound",
      "asset": "Ethereum/erc20:0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48",
      "amount": "50000.00",
      "from": "0x3a1f9c2b8d7e6f5a4b3c2d1e0f9a8b7c6d5e4f3a",
      "to": "0x77b2e4a0c1f3d6b9e2c5a8f1d4b7e0c3a6f9d2b5",
      "timestamp": "2026-02-03T14:22:51Z"
    }
  ],
  "pagination": {
    "limit": 100,
    "nextCursor": "eyJ0cyI6MTczODU4MDU3MTAwMH0"
  }
}
Each item in data is a transaction:
  • hash — the on-chain transaction hash.
  • network — the network the transaction settled on, as a friendly name.
  • status — the transaction’s settlement status (for example, confirmed or pending).
  • direction — whether the transaction moved value into or out of the vault (inbound or outbound).
  • asset — the structured asset identifier of the value transferred ({network}/{tokenType}[:{address}]).
  • amount — the amount transferred, as a string. Parse it with a decimal library, never a float — see Identifiers & data formats.
  • from / to — the source and destination addresses.
  • timestamp — when the transaction settled (UTC, ISO 8601).
To page through a longer list, pass nextCursor back — see Pagination. Errors follow the standard error envelope.