How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Fireblocks Vaults API

Create and manage vault accounts, asset wallets, deposit addresses, attached tags, and balance inquiries. Vaults are the root container for MPC-secured keys, balances, and transactions inside a Fireblocks workspace. Supports paged listing, bulk address creation, customer-ref-id tagging, auto-fuel toggling, and UTXO/unspent-input enumeration.

Fireblocks Vaults API is one of 35 APIs that fireblocks publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include Digital Assets, Vault, Custody, and MPC. The published artifact set on APIs.io includes API documentation, an OpenAPI specification, a JSON-LD context, and 1 JSON Schema.

This API exposes 33 operations across 29 paths, and defines 44 schemas. It is described by OpenAPI 3.0.0, at version 1.8.0.

Requests are made against 2 base URLs: https://api.fireblocks.io/v1, https://sandbox-api.fireblocks.io/v1.

33 operations 29 paths 44 schemas 15 GET16 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
1.8.0
Base URL
https://api.fireblocks.io/v1
Authentication
HTTP Bearer, API Key
Resource Areas
1

Authentication & Security 2

Fireblocks Vaults API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerTokenAuth). An API key is passed in the header as X-API-Key (ApiKeyAuth).

Paths & Operations 33

Across 29 paths, the API surfaces 33 operations — 15 GET, 16 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Vaults 33
GET
/vault/accountsdeprecated
Get vault accounts
getVaultAccounts 4 params → 200default
POST
/vault/accounts
Create a new vault account
createVaultAccount 1 param body → 200default
POST
/vault/accounts/addresses/bulk
Bulk creation of new deposit addresses
createMultipleDepositAddresses 1 param body → 200default
GET
/vault/accounts/addresses/bulk/{jobId}
Get the job status of the bulk deposit address creation
getCreateMultipleDepositAddressesJobStatus 1 param → 200default
POST
/vault/accounts/bulk/
Bulk creation of new vault accounts
createMultipleAccounts 1 param body → 200default
GET
/vault/accounts/bulk/{jobId}
Get job status of bulk creation of new vault accounts
getCreateMultipleVaultAccountsJobStatus 1 param → 200default
POST
/vault/accounts/attached_tags
Attach or detach tags from vault accounts
attachOrDetachTagsFromVaultAccounts 1 param body → 200400404
GET
/vault/accounts_paged
Get vault accounts (Paginated)
getPagedVaultAccounts 9 params → 200
GET
/vault/accounts/{vaultAccountId}
Get a vault account by ID
getVaultAccount 1 param → 200default
PUT
/vault/accounts/{vaultAccountId}
Rename a vault account
updateVaultAccount 2 params body → 201default
GET
/vault/asset_wallets
Get vault wallets (Paginated)
getAssetWallets 6 params → 200
POST
/vault/accounts/{vaultAccountId}/hide
Hide a vault account in the console
hideVaultAccount 2 params → 201default
POST
/vault/accounts/{vaultAccountId}/unhide
Unhide a vault account in the console
unhideVaultAccount 2 params → 201default
POST
/vault/accounts/{vaultAccountId}/{assetId}/activate
Activate a wallet in a vault account
activateAssetForVaultAccount 3 params → 200default
POST
/vault/accounts/{vaultAccountId}/set_customer_ref_id
Set an AML/KYT ID for a vault account
setVaultAccountCustomerRefId 2 params body → 201default
POST
/vault/accounts/{vaultAccountId}/set_auto_fuel
Set auto fueling to on or off
setVaultAccountAutoFuel 2 params body → 201default
GET
/vault/accounts/{vaultAccountId}/{assetId}
Get the asset balance for a vault account
getVaultAccountAsset 2 params → 200default
POST
/vault/accounts/{vaultAccountId}/{assetId}
Create a new vault wallet
createVaultAccountAsset 3 params body → 200default
POST
/vault/accounts/{vaultAccountId}/{assetId}/balance
Refresh asset balance data
updateVaultAccountAssetBalance 3 params → 200default
GET
/vault/accounts/{vaultAccountId}/{assetId}/addressesdeprecated
Get asset addresses
getVaultAccountAssetAddresses 2 params → 200default
POST
/vault/accounts/{vaultAccountId}/{assetId}/addresses
Create new asset deposit address
createVaultAccountAssetAddress 3 params body → 200default
GET
/vault/accounts/{vaultAccountId}/{assetId}/addresses_paginated
Get addresses (Paginated)
getVaultAccountAssetAddressesPaginated 5 params → 200default
GET
/vault/accounts/{vaultAccountId}/{assetId}/max_spendable_amount
Get max spendable amount in a transaction
getMaxSpendableAmount 3 params → 200default
PUT
/vault/accounts/{vaultAccountId}/{assetId}/addresses/{addressId}
Update address description
updateVaultAccountAssetAddress 4 params body → 201default
POST
/vault/accounts/{vaultAccountId}/{assetId}/addresses/{addressId}/set_customer_ref_id
Assign AML customer reference ID
setCustomerRefIdForAddress 4 params body → 201default
POST
/vault/accounts/{vaultAccountId}/{assetId}/addresses/{addressId}/create_legacy
Convert a segwit address to legacy format
createLegacyAddress 4 params → 200default
GET
/vault/accounts/{vaultAccountId}/{assetId}/unspent_inputs
Get UTXO unspent inputs information
getUnspentInputs 2 params → 200default
GET
/vault/public_key_info
Get the public key for a derivation path
getPublicKeyInfo 3 params → 200default
GET
/vault/accounts/{vaultAccountId}/{assetId}/{change}/{addressIndex}/public_key_info
Get an asset's public key
getPublicKeyInfoForAddress 5 params → 200default
POST
/vault/accounts/attached/tags/attachdeprecated
Attach tags to a vault accounts
attachTagsToVaultAccounts 1 param body → 204
POST
/vault/accounts/attached/tags/detacheddeprecated
Detach tags from a vault accounts
detachTagsFromVaultAccounts 1 param body → 204
GET
/vault/assets
Get asset balance for chosen assets
getVaultAssets 2 params → 200default
GET
/vault/assets/{assetId}
Get vault balance by an asset
getVaultBalanceByAsset 1 param → 200default

Schemas 44

The contract defines 44 schemas that model the data the API accepts and returns. The most detailed are VaultAsset (17 properties), AssetWallet (11 properties), VaultWalletAddress (11 properties), CreateVaultAssetResponse (8 properties). Each schema is shown below with its type and property counts.

Tag
object
7 properties 4 required
GetVaultAccountsResponse
array
TagAttachmentOperationAction
string
UnspentInput
object
A representation of an Unspent Transaction Output (UTXO).
2 properties
UpdateVaultAccountAssetAddressRequest
object
1 property
GetMaxSpendableAmountResponse
object
1 property
VaultActionStatus
object
1 property
CreateMultipleDepositAddressesJobStatus
object
3 properties 1 required
UpdateVaultAccountRequest
object
1 property
PublicKeyInformation
object
3 properties
VaultAccount
object
7 properties 4 required
VaultAsset
object
17 properties 6 required
VaultAccountsTagAttachmentsRequest
object
2 properties 2 required
CreateMultipleDepositAddressesRequest
object
6 properties 3 required
GetVaultAssetsResponse
array
CreateAssetsRequest
object
1 property
PaginatedAddressResponse
object
2 properties
CreateAddressResponse
object
5 properties
SetAutoFuelRequest
object
1 property
GetUnspentInputsResponse
array
SetCustomerRefIdForAddressRequest
object
1 property
ErrorSchema
object
2 properties
CreateMultipleAccountsRequest
object
5 properties 2 required
VaultAccountTagAttachmentRejectedOperation
object
4 properties 4 required
CreateAddressRequest
object
2 properties
JobCreated
object
1 property
ApprovalRequest
object
Approval request details
3 properties 3 required
VaultAccountsTagAttachmentOperationsResponse
object
3 properties
CreateMultipleVaultAccountsJobStatus
object
3 properties 1 required
PaginatedAssetWalletResponse
object
2 properties
VaultWalletAddress
object
11 properties
VaultAccountsTagAttachmentOperationsRequest
object
3 properties 1 required
VaultAccountTagAttachmentOperation
object
3 properties 3 required
RewardsInfo
object
1 property
AssetWallet
object
11 properties
UnspentInputsResponse
object
5 properties
VaultAccountTagAttachmentPendingOperation
object
4 properties 4 required
SetCustomerRefIdRequest
object
1 property
CreateVaultAssetResponse
object
8 properties 2 required
VaultAccountsPagedResponse
object
4 properties
RenameVaultAccountResponse
object
2 properties
CreateVaultAccountRequest
object
6 properties
GetVaultAccountAssetAddressesResponse
array
NewAddress
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

fireblocks-vaults-api-openapi.yml Raw ↑

Other APIs fireblocks publishes across the network.

Fireblocks Transactions API
Fireblocks Tokenization API
Fireblocks Staking API
Fireblocks NFTs API
Fireblocks Compliance and Policy API
Fireblocks Gas Station API
Fireblocks Webhooks API
fireblocks Approval Requests API
fireblocks Blockchains & Assets API
fireblocks Connected Accounts (Beta) API
fireblocks Contract Interactions API
fireblocks Contract Templates API
Where this information came from

This is an independent, third-party profile of Fireblocks Vaults API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.