Vaults

A vault is the container Fortary custody is organized around: your organization’s assets are held in vaults, and the v1 API reads everything — balances, transaction history, deposit addresses — through the vault that holds it.

​

Vault identity

Vaults are identified by opaque, prefixed IDs such as vault_3f8a2c1d9b. Treat them as opaque — don’t parse or construct them; store and pass back the exact string you received. See Identifiers & data formats. Start with List vaults to discover the vaults your credential can access and their IDs; every other vault operation takes one of those IDs in its path.

​

What a credential can see

A credential sees a vault only where its vault:read scope, its owner’s live Developer role, and its vault allowlist all agree — see Authorization. A vault outside that intersection returns 404, never 403, so responses never reveal whether a vault you can’t see exists.

​

Operations