| -1 | 401 | All | Invalid signature If you receive this error message, ensure the private key you used is correct. |
| -2 | 401 | All | Missing API Key in the JWT Verify that you specify the API key |
| -3 | 401 | All | The entire JWT is missing - Uncommon_ - Potential code change, or bad parameters passed to Fireblocks SDK constructor |
| -4 | 401 | All | Wrong URL in the JWT - Uncommon_ - Potential code change to the Fireblocks SDK source code on your device |
| -5 | 401 | All | Unauthorized: Invalid token format This error code typically indicates the certificate associated with the API user making the call has expired. |
| -6 | 401 | All | Wrong User in the JWT The user being used as part of the request is incorrect. Verify that the correct user is being used |
| -7 | 401 | All | Unauthorized: Token was not accepted This error code typically indicates that the JSON Web Token (JWT) supplied with the API user’s request was not accepted. API requests to Fireblocks are authenticated using the provided JWT. If the JWT is invalid, you will receive the error code. The cause of the error is likely either the wrong API key being used or the wrong baseURL being used. For SDK users, this typically means an incorrect API key was used to create the client. For users with native API client implementations, this typically indicates an error with your JWT creation logic. |
| -8 | 401 | All | Insufficient permissions This error code typically indicates that the API user initiating this request does not have access to the requested operation based on their user role |
| -10 | 401 | All | The request has expired This error typically indicates the JSON Web Token (JWT) supplied with the API user’s request has timed out. Please note: - For Fireblocks SDK users, the JWT expiration time is defined based on the system time. - For users with their own API client implementations, the JWT data is defined by the user’s implementation. |
| -12 | 401 | All | The request is with a future issuance timestamp (iat) This error code typically indicates the JSON Web Token (JWT) supplied with the API user’s request is not yet valid for processing. - For SDK users, the JWT “initiated–at” time is defined based on the system time. - For users with their own API client implementations, the JWT data is defined by the user’s implementation. |
| 900 | 400 | All, Trading | Validation Error The request contains invalid data or parameters. |
| 1000 | 400 | Vault | GetVaultAccounts request has invalid values Check that you pass a valid minAmountThreshold (if you pass it) and only one of namePrefix, nameSuffix if you pass it |
| 1002 | 400 | Vault | Create Vault Account failed Verify that the values provided to the create vault account request are valid and conform to the types specified in the API Docs |
| 1004 | 404 | Vault | Vault account ID was not found Verify that the vault account you’re trying to query is valid and exists |
| 1006 | 404 | Asset, Balance | Asset doesn’t exist The asset requested for the given vault account does not exist. Verify that the vault account contains the asset you’re requesting. |
| 1008 | 400 | Wallet, Asset (EOS Specific) | EOS Wallet Creation failed The eosAccountName parameter is invalid |
| 1010 | 400 | Wallet | Renaming a deposit address failed You’re trying to add an address to a blockchain that does not support more than 1 address (such as ETH) |
| 1013 | 400 | Vault | Vault account renaming failed Verify that the parameters passed to the vault account renaming operation are valid |
| 1015 | 400 | Wallet | Rename a deposit address failed Verify that the parameters that were passed are valid and that the asset you’re trying to rename exists |
| 1016 | 400 | Wallet | Rename a deposit address failed The rename operation failed due to a backend issue - open a ticket to support |
| 1017 | 400 | Vault | Hide vault account failed The vault account you requested to hide does not exist. Please verify you’re using the correct vault account ID |
| 1019 | 400 | Vault | Hide on a hidden vault account request You’re requesting to hide a vault account that is already hidden. Please verify you’re using the correct vault account ID |
| 1020 | 400 | Vault | Unhide vault account failed The vault account you requested to unhide does not exist. Please verify you’re using the correct vault account ID |
| 1022 | 400 | Vault | Unhide on a visible vault account request You’re requesting to unhide a vault account that is not hidden. Please verify you’re using the correct vault account ID |
| 1023 | 400, 404 | Wallet | Get legacy address failed There is no legacy address used for this specific asset |
| 1024 | 400, 404 | Wallet | Get legacy address for an asset without one The asset you’re trying to get the legacy address for does not have one (for example, ETH) |
| 1025 | 400 | Asset, Vault, Wallet | Usage of an unsupported asset The asset you specified in your request is invalid. Please check it against the supported asset list |
| 1026 | 400 | Asset, Vault, Wallet | Creation of a wallet that already exists You’ve requested to create a wallet for an asset that already has a wallet in the vault account. Please check whether you’re using the correct vault account and the correct asset |
| 1027 | 400 | Asset, Balance | Requested max spendable amount for asset that doesn’t support that request You’ve requested to know the max spendable amount for an asset, which does not support this request. Verify you’re using one of the assets according to the API docs |
| 1028 | 400 | Asset, Balance | Max Spendable Amount invalid value The parameters you provided for the request are invalid. Please verify you provided the correct type of values, as well as a valid asset and vault account ID |
| 1031 | 400 | Asset, Balance | Get balance by assets The request to balance of assets in all vault accounts is invalid, only one of accountNamePrefix and accountNameSuffix can be provided |
| 1032 | 400, 404 | Asset, Balance | Get balances by assets or get balance for asset failed The asset requested does not exist in the vault account |
| 1034 | 400 | Wallet | Create testnet asset failed You’re requested to create a testnet asset on a workspace that does not have testnet support |
| 1035 | 400 | Asset | Activate wallet failed The request to activate the wallet failed. Please open a ticket to support |
| 1037 | 400 | Vault | Get vault accounts endpoint is disabled Workspaces created after May 2022 do not support the get vault accounts endpoint; use the paged request |
| 1038 | 400 | Wallet, Asset | Adding a token without base asset Before adding a token to the vault account, please create a base asset wallet |
| 1039 | 400 | Wallet, Asset | Insufficient base asset for token wallet Before creating a token asset, make sure you have sufficient base asset to cover token transactions |
| 1040 | 401 | Vault | Unauthorized user to create vault account The user who is trying to add a vault account does not have the proper permissions needed to create a vault account. Make sure you use the correct user |
| 1048 | 400 | Vault | The vault account type is not supported by the workspace You attempted to create/use a vault account with a type that isn’t enabled or recognized for your tenant (plan/feature flag/environment). Use a supported type (or omit it to use the default), or contact Fireblocks to enable the feature. |
| 1103 | 400 | Exchange, Fiat | No such exchange/fiat account ID The exchange or fiat account ID does not exist. Make sure you’re using the correct one |
| 1105 | 400 | Exchange | Exchange account for asset by ID does not exist The exchange account’s asset does not exist for the specified exchange account ID. Make sure you’re using the correct exchange account ID and asset |
| 1106 | 400 | Exchange Transfers | No such exchange account ID The exchange account ID specified does not exist |
| 1108 | 408 | Exchange | Exchange timeout when adding an account We faced an internal timeout when trying to add the exchange account |
| 1111 | 400 | Exchange Transfers | Exchange convert failed Failed to perform a convert operation. Please check the message reply to understand the issue |
| | | |
| 1202 | 400 | Internal Wallets | Create internal wallet failed Internal wallet name must be specified, not empty, and to not already exist in a different wallet |
| 1204 | 400 | Internal Wallets | Get internal wallet by id failed The internal wallet specified does not exist. Make sure you’re querying the correct internal wallet ID |
| 1206 | 400 | Internal Wallets | Delete internal wallet failed Failed to delete the internal wallet. Please make sure you’ve specified the correct internal wallet parameters |
| 1208 | 400 | Internal Wallets | Create an internal wallet failed Failed to create an internal wallet. Please verify you’ve provided the correct parameters for the creation as per the API docs |
| 1209 | 400 | Internal Wallets | Getting the wallet’s asset failed The internal wallet based on the ID and asset specified does not exist. Please make sure you’re using the correct asset and wallet ID |
| 1212 | 400 | Internal Wallets | Deleting specific asset from wallet failed Please verify that you specified the correct wallet ID and asset ID for deletion |
| 1213 | 400 | Internal Wallets | Create an unsupported asset address in a wallet The asset you’re trying to add to the wallet is not supported. Verify the asset you’re trying to use |
| 1214 | 400 | Internal Wallets | Create an asset from a different network in the wallet The asset you’re trying to add to the wallet is in a different network (mainnet or testnet), and your workspace does not support this network. Please verify the network of the asset and that your workspace correlates |
| 1215 | 400 | Internal Wallets | Add an asset in a wallet that already has it You’re trying to add an asset to the internal wallet, but it already has this asset. Please make sure you’re adding a new asset and not one that already exists |
| 1216 | 400 | Internal Wallets | Add an asset with an invalid address to the wallet You’re trying to add an asset to the internal wallet, but the address does not match the asset’s conventions. Please check the address you’re trying to add |
| | | |
| 1302 | 400 | External Wallets | Create external wallet failed External wallet name must be specified, not empty, and to not already exist in a different wallet |
| 1304 | 400 | External Wallets | Get external wallet by Id failed The external wallet requested does not exist. Please make sure you’re using the correct wallet ID |
| 1306 | 400 | External Wallets | Delete external wallet failed Failed to delete the external wallet. Please make sure you’ve specified the correct external wallet parameters |
| 1308 | 400 | External Wallets | Create an external wallet failed Failed to create an external wallet. Please verify you’ve provided the correct parameters for the creation as per the API docs |
| 1309 | 400 | External Wallets | Getting the wallet’s asset failed The external wallet based on the ID and asset specified does not exist. Please make sure you’re using the correct asset and wallet ID |
| 1312 | 400 | External Wallets | Deleting specific asset from wallet failed Please verify that you specified the correct wallet ID and asset ID for deletion |
| 1313 | 400 | External Wallets | Create an unsupported asset address in a wallet The asset you’re trying to add to the wallet is not supported. Verify the asset you’re trying to use |
| 1314 | 400 | External Wallets | Create an asset from a different network in the wallet The asset you’re trying to add to the wallet is in a different network (mainnet or testnet), and your workspace does not support this network. Please verify the network of the asset and that your workspace correlates |
| 1315 | 400 | External Wallets | Add an asset in a wallet that already has it You’re trying to add an asset to the external wallet, but it already has this asset. Please make sure you’re adding a new asset and not one that already exists |
| 1316 | 400 | External Wallets | Add an asset with an invalid address to the wallet You’re trying to add an asset to the external wallet, but the address does not match the asset’s conventions. Please check the address you’re trying to add |
| | | |
| 1351 | 400 | Contract Wallets | Create contract wallet failed Contract wallet name must be specified, not empty, and to not already exist in a different wallet |
| 1354 | 400 | Contract Wallets | Get contract wallet by Id failed The contract wallet requested does not exist. Please make sure you’re using the correct wallet ID |
| 1356 | 400 | Contract Wallets | Delete contract wallet failed Failed to delete the contract wallet. Please make sure you’ve specified the correct contract wallet parameters |
| 1358 | 400 | Contract Wallets | Create a contract wallet failed Failed to create a contract wallet. Please verify you’ve provided the correct parameters for the creation as per the API docs |
| 1359 | 400 | Contract Wallets | Getting the wallet’s asset failed The contract wallet based on the ID and asset specified does not exist. Please make sure you’re using the correct asset and wallet ID |
| 1362 | 400 | Contract Wallets | Deleting specific asset from wallet failed Please verify that you specified the correct wallet ID and asset ID for deletion |
| 1363 | 400 | Contract Wallets | Create an unsupported asset address in a wallet The asset you’re trying to add to the wallet is not supported. Verify the asset you’re trying to use |
| 1364 | 400 | Contract Wallets | Create an asset from a different network in the wallet The asset you’re trying to add to the wallet is in a different network (mainnet or testnet), and your workspace does not support this network. Please verify the network of the asset and that your workspace correlates |
| 1365 | 400 | Contract Wallets | Add an asset in a wallet that already has it You’re trying to add an asset to the contract wallet, but it already has this asset. Please make sure you’re adding a new asset and not one that already exists |
| 1366 | 400 | Contract Wallets | Add an asset with an invalid address to the wallet You’re trying to add an asset to the contract wallet, but the address does not match the asset’s conventions. Please check the address you’re trying to add |
| | | |
| 1401 | 400 | Transaction | The operation requested is not supported The operation argument that you provided in the create transaction is not supported. Please verify it’s correct |
| 1402 | 400 | Transaction | Source balance insufficient The balance of the source account is not sufficient to cover the transaction |
| 1403 | 400 | Transaction | Destination balance is insufficient Some blockchains (such as NEAR) require a minimal amount of assets to be activated. You tried to pass less than the minimal amount to a vault account that does not have such a wallet, thus the wallet can’t be created. Please verify you’re transferring a sufficient amount, or have the destination create a wallet and deposit a sufficient amount of base asset |
| 1404 | 400 | Transaction | Invalid Peer type When creating the transaction, verify that the type of the source and destination are valid and one of the defined enums in the API docs |
| 1405 | 404 | Transaction | No such transaction The transaction ID you used to try and get the transaction object is invalid and was not found in the system. Make sure you’re using the correct transaction ID |
| 1406 | 400 | Transaction | Failed to cancel transaction Cancelling the transaction failed for some reason. Please open a support ticket |
| 1407 | 400 | Transaction | User can’t create a transaction The user trying to create the transaction does not have sufficient permissions to do so. Please verify the user’s permission level and that you’re using the correct user |
| 1408 | 400 | Transaction | Paged get tried to change direction When getting transactions in a paged fashion, you can only go in one direction (forward or backward) and can’t change direction mid execution. Make sure you’re only querying the information in one direction |
| 1409 | 400 | Transaction | Transaction creation parameters are invalid Here is a list of items to check: 1. The asset type is valid and is supported 2. You can only specify destination or destinations, not both 3. For OTA, you must specify the address 4. Typed messages only supported BTC, LTC, DASH, and ETH 5. AML Customer reference ID can only use -_: and alpha-numeric 6. You can not have more than 650 destinations in the destinations parameters 7. Invalid nodeControls parameters |
| 1410 | 400 | Transaction | Transaction destination wallet does not exist The destination is sending the transaction to an external/internal/contract wallet by an ID, but the ID specified does not exist. Check that the ID you’re using is correct |
| 1411 | 400 | Transaction | Transaction destination wallet asset does not exist The destination is sending the transaction to an external/internal/contract wallet by an ID, but the asset used in the transaction does not exist. Check that the asset has an address in the wallet ID |
| 1412 | 400 | Transaction | Transaction destination wallet address is suspended The destination is an external/internal/contract wallet that has not been approved yet. Approve it and try again |
| 1421 | 400 | Transaction | Confirmation number change failed Changing the number of confirmations for the transaction failed. Please verify that the transaction exists; otherwise, open a support ticket |
| 1422 | 400 | Transaction | Confirmation number change failed Changing the number of confirmations for the transaction by transaction hash failed. Please make sure you’re using the correct transaction hash; otherwise, open a support ticket |
| 1423 | 400, 404 | Transaction | Get transaction by transaction hash failed Couldn’t find a transaction with the specified transaction hash. Please verify the transaction hash and try again |
| 1424 | 400 | Transaction, Network Connection | Destination address invalid Here is a list of parameters to check: 1. The address used is invalid for the asset you’re using 2. The target (in case of a network transfer) does not contain a wallet for the specified asset 3. You’re using the internal/external/contract wallet for a different workspace than the one you’re performing the transaction on 4. You are trying to send a transaction to a network connection that you do not have 5. You’re using destinations and one of the destinations is a network connection - this is not supported |
| 1425 | 400 | Transaction | Missing a tag You’re trying to send a transaction to an address that requires a tag. Please verify you’re providing a tag |
| 1426 | 400 | Transaction | Unfreeze failed You tried to unfreeze a transaction, but it was neither rejected nor failed by AML; therefore, it can’t be unfrozen |
| 1427 | 400 | Transaction | Source type of transaction is invalid You tried to send a transaction with the source being invalid. Verify that the source is one of: VAULT_ACCOUNT, EXCHANGE_ACCOUNT, GAS_STATION or FIAT_ACCOUNT |
| 1428 | 400 | Transaction | Destination of transaction is invalid The destination type of one of the destinations is not one of the defined enums in the API docs. Verify that it is correct and try again |
| 1429 | 400 | Asset, Transaction | Validate address failed The asset you tried to use for the validate_address endpoint is not supported |
| 1431 | 400 | Asset, Transaction | Validate address didn’t find an address The address provided to the validate_address endpoint is invalid. |
| 1432 | 400 | Transaction | Invalid amount specified The amount must be a number or a numeric string; verify it is so |
| 1433 | 400 | Transaction | Invalid tag specified The tag/memo specified does not comply with the rules of the blockchain. Verify the tag/memo is valid |
| 1434 | 400 | Transaction | Freeze failed or Cannot freeze Depending on the context of the error code, you will see one of the above responses. Typically, freezing fails because of one of the following reasons: - The transaction is not in either the Confirming or the Completed status. - An input is not available. - There is an insufficient balance for freezing. - The transaction direction or asset type is not supported for freezing. |
| 1435 | 400 | Transaction | List unspent for unknown asset You tried to get the unspent inputs (UTXO) for an asset that does not have such values, or no UTXOs exist |
| 1437 | 400 | Exchange, Transaction | Unsupported transfer Direct transfers (Exchange to OTA) is not supported for the Kraken exchange |
| 1438 | 400 | Transaction | External Tx ID Duplicate The externalTxId specified in the transaction was already used in the past. Please use a different one |
| 1439 | 404 | Transaction | No such External Tx ID The external Tx ID used does not exist. Please verify the external Tx ID you’re using |
| 1440 | 400 | Transaction | Drop for unsupported blockchain You’re trying to run a drop transaction request for a blockchain that is not ETC or ETH |
| 1441 | 400 | Transaction | Replace by fee too low You’re attempting to perform an RBF transaction, but the gas price you specified is too low. Please check it and submit a higher gas price |
| 1443 | 400 | Transaction | Too late for RBF You’re trying to replace by fee, but the transaction was already mined |
| 1445 | 403 | Transaction | User can’t freeze The user who is trying to perform a freeze does not have the permissions to perform this. Check the user’s permissions and that you’re using the correct user |
| 1446 | 403 | Transaction | User can’t unfreeze The user who is trying to perform an unfreeze does not have the permissions to perform this. Check the user’s permissions and that you’re using the correct user |
| 1448 | 400 | Transaction | Fee payer is not allowed for asset You’re trying to define a fee payer for an asset that does not support it. Please check whether the asset you’re using allows for a fee payer configuration |
| 1449 | 400 | Transaction | Fee payer can’t pay The defined fee payer does not have a wallet with the base asset to pay the fee. Verify that you specified the correct fee payer and check that it contains a base asset wallet with a sufficient amount to pay for the transaction |
| 1450 | 400 | Transaction | Transactions are blocked for this blockchain We have temporarily disabled transactions for the specified blockchain. Check the status page for more details |
| 1451 | 400 | Transaction | Transaction confirmations don’t match Fireblocks restrictions Fireblocks requires a specific number or a minimum number of confirmations for some blockchains. Manually setting confirmations for a transaction must meet these requirements. For more, see Deposit Control & Confirmation Policy. |
| 1454 | 400 | Transaction | Missing license for creating a MEV protected transaction This feature is not enabled in your workspace, and you should contact your Customer Success Manager or the Fireblocks Support team |
| 1455 | 400 | Transaction, Gasless (meta-tx) | Missing Gasless configuration Gasless transactions aren’t set up for this workspace/asset. Configure Gasless (relayer/fee payer) or send a standard transaction. |
| 1502 | 400 | Asset, Transaction | Trying to use a deprecated asset The asset specified in the transaction is deprecated and can’t be used. Please check the asset and use a different one |
| 1503 | 400 | Asset, Balance, Transaction | Unsupported asset The asset specified is not supported. Please check the asset you’ve specified |
| | | |
| 1601 | 404 | Network Connection | Network Connection Id does not exist The network connection you’re trying to query by ID does not exist. Please check the ID you’re using |
| 1603 | 400 | Network Connection | Delete Network Connection but id is not specified The delete network connection request does not have a connectionId parameter specified, please make sure one is provided and exists |
| 1604 | 400 | Network Connection | Create a network connection failed The network connection creation failed. Check the error message for more information and open a support ticket if insufficient |
| 1605 | 404 | Network Connection | Get Network Connection for unknown id The network connection ID provided could not be found. Please verify you’re using the correct ID |
| 1606 | 404 | Network Connection | Delete network connection for unknown id The network connection ID provided could not be found. Please verify you’re using the correct ID |
| 1607 | 400 | Network Connection | Setting the routing policy for a network connection failed Verify that you used the proper parameters for the call |
| 1608 | 404 | Network Connection | Set routing policy for an unknown network connection id The ID you provided for the call was not found. Verify you’re using the correct ID and it exists |
| 1609 | 400 | Network Connection | Validating routing policy failed The attempt to validate whether the network connection’s routing will lead to a third party or not for a given asset failed. Please verify you passed the correct parameters and open a support ticket if needed |
| 1610 | 404 | Network Connection | Validating routing policy for an unknown network connection id The ID you provided for the call was not found. Verify you’re using the correct ID and it exists |
| 1611 | 403 | Network Connection | No multiple network profiles The workspace does not support multiple network profiles. Contact us to request support |
| 1612 | 422 | Network Connection | The counterparty rejected the connection request The Counterparty has to send a connection request. |
| 1613 | 422 | Network Connection | The counterparty is already an active connection The network connection already exists |
| 1614 | 422 | Network Connection | The connection is pending approval You can request approval from the workspace admins |
| 1615 | 422 | Network Connection | The connection is pending approval You can request approval from your counterparty |
| 1616 | 403 | Network Connection | Network connection cannot be deleted There is an active Smart Transfers ticket with the connection, which must be closed before deleting the Network connection |
| 9007 | 404 | Network Connection | The Fireblocks Network is not activated in the workspace Reach out to Fireblocks Support to resolve this |
| 9011 | 403 | Network Connection | Cannot delete network ID The default ID cannot be deleted before making another ID the default |
| 9012 | 403 | Network Connection | Network profile cannot be deleted It is the last remaining ID. There must be at least one Network profile per tenant |
| 9013 | 403 | Network Connection | Network profile cannot be deleted There is an active Smart Transfers ticket with the Network profile, which must be closed before deleting the Network profile |
| 9014 | 422 | Network Connection | Invalid network name The name can’t contain the < and > characters |
| 9015 | 403 | Network Connection | Could not add an additional network ID Contact Fireblocks Support to activate the feature |
| 9016 | 422 | Network Connection | The selected asset is not supported on the Fireblocks Network Reach out to Fireblocks Support to resolve this |
| 9017 | 422 | Network Connection | Invalid routing policy > non-custom scheme A routing destination type or ID is required |
| 9018 | 422 | Network Connection | Invalid routing policy > destination ID incompatible with selected asset. Make sure you are sending a supported asset |
| 9019 | 422 | Network Connection | Invalid routing policy > selected routing policy is not allowed Select a valid routing policy |
| 9020 | 422 | Network Connection | Invalid routing policy > selected routing destination is not supported Select one of the supported destinations |
| 9021 | 422 | Network Connection | Invalid routing policy > selected crypto destination is not supported Select a vault or a connected exchange account. |
| 9022 | 422 | Network Connection | Invalid routing policy > third-party account provided is invalid Make sure you are adding a supported third-party destination |
| 1706 | 400 | FIAT Accounts | FIAT Account id provided is unknown The exchange account ID you provided was not found. Please verify you’re using the correct account ID |
| 1708 | 400 | FIAT Accounts | FIAT Account id provided is unknown The exchange account ID you provided was not found. Please verify you’re using the correct account ID |
| | | |
| 1901 | 400 | Asset, Transaction | Estimate fee for unknown asset The asset you specified for the estimate fee call is unknown. Please make sure you’re using a supported and known asset |
| 1902 | 400 | Asset, Transaction | Estimate fee for an invalid asset The asset you specified does not support the estimate fee call. Please make sure you’re using a supported and allowed asset |
| 1904 | 400 | Asset, Transaction | Estimate fee with invalid parameters Make sure when calling the estimate fee endpoint that you do not have destination and destinations parameters both used, and that the source parameter is a vault account |
| 1905 | 400 | Asset, Transaction | Estimate fee failed due to insufficient funds The funds you have in the source vault are not sufficient, and thus the estimate fee call failed. Make sure you have sufficient base asset in the source vault and try again |
| 1907 | 400 | Asset, Transaction | Estimate fee failed due to smart contract error. The transaction reverted during its simulation as part of estimating the gas limit. There are three ways to properly handle this error: 1. Initiate the transaction again while using different parameters. 2. Try using a different vault to perform the transaction. 3. Read the contract’s source code to better understand the error. |
| 1908 | 400 | Asset, Transaction | Estimate fee failed since the amount you are sending is too small The transaction failed since the amount you tried to send was not enough to pass our balance validation and internal tx checks. Confirm the transfer amount is above the required minimum for this blockchain or more than the transaction fees necessary before resubmitting the transaction. Minimum transfer amounts vary per blockchain. Known minimums: Bitcoin (BTC) - 546 satoshi Cardano (ADA) - 1 ADA + applicable transaction fees |
| 1909 | 400 | Asset, Transaction | Estimate failed due to insufficient gas fees The transaction failed since you didn’t have enough gas fees. Make sure you have sufficient gas money and try again. |
| 2002 | 400 | Public Key | Public key could not be found Make sure that the information you provided to the public key query is valid, and a wallet for this asset exists in the specified vault account |
| | | |
| 2101 | 400 | Gas Station | Invalid gas station parameters When editing the gas station configuration, make sure you provide both gasCap and gasThreshold |
| 2110 | 400 | Gas Station | Invalid asset for gas station When editing the gas station configuration, the asset you specified is not supported for this operation. Make sure you’re using a supported and valid asset |
| | | |
| 2201 | 400 | Balance, Private Ledger | Lock/Release allocation for unsupported asset The asset you specified in the lock or release allocation call is not supported. Make sure it is a valid and supported asset |
| 2202 | 400 | Balance, Private Ledger | Lock/Release Allocation for unknown account The virtual account you specified does not exist. Please make sure you’re using a valid virtual account that exists |
| 2204 | 400 | Private Ledger, Off-Exchange | Allocation not allowed The vault account you specified does not have off-exchange set up; therefore, locking allocation is not allowed. Make sure you have off-exchange set up and then try again |
| 2205 | 400 | Private Ledger, Balance | Insufficient amount for fee in allocation The call you’re trying to perform requires that a sufficient amount for the fee bank be allocated. The allocation amount you’ve specified does not meet this demand. Please increase the allocation amount |
| | | |
| 2501 | 400 | Webhooks | Resend webhook for specific tx id failed Make sure one of the parameters resendCreated and resendUpdated is marked as true, and try again |
| | | |
| 2602 | 404 | Off-Exchange | Unknown virtual account id The virtual account ID specified does not exist. Make sure you’re using a virtual account ID that exists |
| 2604 | 404 | Off-Exchange | Unknown virtual account id The virtual account ID specified does not exist. Make sure you’re using a virtual account ID that exists |
| | | |
| 2702 | 403 | Users | Insufficient permissions for operation The user who is trying to perform this call does not have sufficient permissions for it. Make sure you’re using the correct user and that they have the proper permissions to view the user list |
| | | |
| 2814 | 400 | Fee Payer | Fee Payer not configured No fee payer was configured for this workspace. Configure one and try again |
| 2816 | 400 | Fee Payer | Asset wallet does not exist You’ve attempted to set a fee payer by specifying a vault account and asset; however, the specified asset does not have a wallet in the specified vault account. Please create a wallet in the specified vault account and fund it, then try again |
| 2817 | 400 | Fee Payer | Non-base asset You’ve specified a fee payer asset that is not the base asset. This is not allowed. Please specify the base asset and try again |
| 2818 | 400 | Fee Payer | Unsupported asset You’ve tried to set a fee payer for an asset that is not supported. Please verify you’re using a supported asset and try again |
| | | |
| 2902 | 403 | Audits | Getting audits is not allowed The user trying to get the audits is not allowed to due so due to a permissions matter. Make sure that the user has the proper permissions and that you’re using the correct user |
| | | |
| 3001 | 404 | Smart Transfers | Ticket not found Fireblocks could not find the Smart Transfer ticket. |
| 3002 | 403 | Smart Transfers | Ticket should be open The attempted action can only be performed on an open Smart Transfer ticket. |
| 3003 | 403 | Smart Transfers | Ticket should be draft The attempted action can only be performed on a Smart Transfer ticket draft. |
| 3004 | 403 | Smart Transfers | Ticket should be draft or open The attempted action can only be performed on an open Smart Transfer ticket or a Smart Transfer ticket draft. |
| 3005 | 403 | Smart Transfers | Ticket action allowed for owner Only the Smart Transfer ticket creator can perform the attempted action. |
| 3006 | 403 | Smart Transfers | Ticket cancel can be done by payer You cannot close the Smart Transfer ticket because the connection has already funded it. |
| 3007 | 403 | Smart Transfers | Ticket terms are missing You must define all required terms before you can open the Smart Transfer ticket. |
| 3008 | 403 | Smart Transfers | Ticket expiration date passed The Smart Transfer ticket has expired. |
| 3009 | 400 | Smart Transfers | Term not found No Smart Transfer ticket term matches your search criteria. |
| 3010 | 403 | Smart Transfers | Term should be created status The submitted or updated Smart Transfer ticket term is incorrect. |
| 3011 | 403 | Smart Transfers | Term should be funded status Only a funded Smart Transfer ticket can be closed. |
| 3012 | 403 | Smart Transfers | Term should be funding failed status The attempt to fund the Smart Transfer ticket failed. |
| 3013 | 403 | Smart Transfers | Term amount required You must enter a term amount before you can open a Smart Transfer ticket. |
| 3014 | 403 | Smart Transfers | Term asset required You must select an asset before you can open a Smart Transfer ticket. |
| 3015 | 403 | Smart Transfers | Term asset not supported Fireblocks does not support the selected asset for Smart Transfer tickets. |
| 3016 | 403 | Smart Transfers | Term from to should be different The Smart Transfer ticket must include two different connections. |
| 3017 | 403 | Smart Transfers | Term amount is different than fund amount The entered fund amount does not match the term amount on the Smart Transfer ticket. |
| 3018 | 403 | Smart Transfers | Term asset is different than fund asset The asset selected for funding does not match the term’s asset on the Smart Transfer ticket. |
| 3019 | 403 | Smart Transfers | Counterparty not found Fireblocks could not find the counterparty connection. |
| 3020 | 403 | Smart Transfers | Network does not belong to tenant You can only open a Smart Transfer ticket using a Fireblocks Network profile belonging to you. |
| 3021 | 403 | Smart Transfers | Networks not connected The selected counterparty is not a Fireblocks Network connection. |
| 3022 | 403 | Smart Transfers | Term should be created or funding failed status The Smart Transfer ticket has already been funded or is currently being funded. |
| 3023 | 403 | Smart Transfers | Term transaction can be made by counterparty of term who should pay Your Fireblocks Network profile cannot fund the Smart Transfer ticket. |
| 3024 | 403 | Smart Transfers | Network connection does not belong to peers The Fireblocks Network connection funding the Smart Transfer ticket does not match the connection listed on the term. |
| 3025 | 403 | Smart Transfers | Transaction fee and fee level defined You cannot set a fee level (low, medium, or high) and specify a custom fee at the same time. |
| 3027 | 403 | Smart Transfers | Tickets can have at most two terms Smart Transfer tickets can only have two transfer terms. |
| 3029 | 403 | Smart Transfers | Network doesn’t have FF enabled The Fireblocks Network connection does not use the Smart Transfer feature. |
| 3030 | 400 | Smart Transfers | Ticket missing expire in You must set an expiration date before you can open a Smart Transfer ticket. |
| 3031 | 403 | Smart Transfers | Ticket creator must receive asset You can only open a Smart Transfer ticket for receiving assets. |
| 3101 | 404 | Trading | Provider Not Found Provider not found. |
| 3102 | 400 | Trading | Terms Approval Not Supported This provider does not support terms of service approval. |
| 3103 | 400 | Trading | Same Chain Required Input and output assets must be on the same chain. |
| 3104 | 400 | Trading | Cross Chain Required Input and output assets must be on different chains. |
| 3105 | 400 | Trading | Unsupported Input Chain The input blockchain is not supported by this provider. |
| 3106 | 400 | Trading | Unsupported Output Chain The output blockchain is not supported by this provider. |
| 3107 | 400 | Trading | Unsupported Assets Pair This trading pair is not supported by the provider. |
| 3108 | 400 | Trading | Settlement Required This trade requires settlement information to be provided. |
| 3109 | 400 | Trading | Unsupported DVP Settlement Source/Destination Only vault accounts can be used for DVP settlement type. |
| 3110 | 400 | Trading | Unsupported Settlement Pair Source and destination must be the same vault account. |
| 3111 | 400 | Trading | Unsupported Side in DeFi Quote DeFi trades only support selling (not buying) at this time. |
| 3112 | 400 | Trading | Unsupported Execution Type This type of trade execution is not supported. |
| 3113 | 400 | Trading | Unsupported Asset Provider This asset is not supported by this provider. |
| 3114 | 400 | Trading | Quote Not Available No pricing quote is available for this trade at the moment. |
| 3115 | 404 | Trading | Quote Not Found The price quote has expired or is no longer valid. |
| 3116 | 404 | Trading | Order Not Found The trading order you requested does not exist. |
| 3117 | 404 | Trading | Source Account Not Found Source account to extract funds not found for the given asset. |
| 3118 | 404 | Trading | Provider Account Not Found The specified provider account was not found. |
| 3119 | 400 | Trading | Provider Account Not Active The specified provider account is not active. |
| 3120 | 403 | Trading | Terms of Service Approval Required You must approve the terms of service before trading with this provider. |
| 3121 | 400 | Trading | Quotes Unsupported The provider does not support quote operation. |
| 3122 | 403 | Trading | Unmanaged Wallet Not Approved Please approve the unmanaged wallet request before sending an order. |
| 3123 | 400 | Trading | Rates Unsupported The provider does not support rate operation. |
| 3124 | 400 | Trading | Insufficient Funds Insufficient balance. |
| 3125 | 404 | Trading | Destination Asset Wallet Not Found Destination account to deposit funds not found for the given asset. |
| 3126 | 400 | Trading | Account Not Activated Exchange/Connected account not activated. |
| 3127 | 400 | Trading | Blockchain Rail Unsupported for Fiat A blockchain rail cannot be used with a fiat asset. |
| 3300 | 500 | Staking | Internal Error An unexpected internal error occurred. Retry the request; if the issue persists, contact support. |
| 3310 | 404 | Staking | Position Not Found The staking position you requested does not exist. Verify the position ID is correct. |
| 3311 | 404 | Staking | Validator Address Not Found No validator address was found for the specified provider and chain. Verify the provider ID and chain descriptor. |
| 3312 | 404 | Staking | Provider Not Found The staking provider you specified does not exist or is invalid. Verify the provider ID. |
| 3313 | 404 | Staking | Wallet Not Found The specified wallet was not found. Verify the wallet address or vault account. |
| 3320 | 409 | Staking | Position State Invalid The staking position is not in a valid state for the requested action (e.g. source or destination position is not active). Wait for any pending operations to complete before retrying. |
| 3321 | 403 | Staking | Terms of Service Approval Required The provider’s terms of service have not been approved. Approve the provider’s terms of service before performing staking operations. |
| 3322 | 409 | Staking | Position Already Exists A staking position already exists for this vault and provider combination (e.g. MATIC can only be staked once per provider per vault). Use the existing position or choose a different vault/provider. |
| 3330 | 400 | Staking | Chain Not Supported The specified blockchain is not supported for staking. Use a supported chain descriptor. |
| 3332 | 400 | Staking | Action Unavailable The requested action (e.g. unstake, withdraw, addToStake, consolidate) is not available for this position in its current state. Verify the position status before retrying. |
| 3333 | 403 | Staking | Not Available for Workspace The requested staking feature or chain is disabled for your workspace (controlled via feature flags). Contact your account manager to enable it. |
| 3341 | 400 | Staking | Invalid Amount The stake amount is invalid — it must be positive, non-zero, and meet chain-specific requirements (e.g. ETH must be at least 32 and divisible by 32; MATIC must be at least 1; Lido must be greater than 100 wei). Adjust the amount accordingly. |
| 3381 | 409 | Staking | Operation Already In Progress Another staking operation is currently in progress on one of the involved positions. Wait for the existing operation to complete before initiating a new one. |
| 9001 | 400 | Wallet | Invalid customer reference id The customer reference ID specified is invalid. Make sure it only consists of \-\_:a-zA-Z0-9 |
| 9003 | 400 | Transaction | Invalid idempotency key length The idempotency key must be no longer than 40 characters. Please verify that if you’ve specified one, it has a proper length Idempotency key used on internal error request, returning bad request This operation doesn’t support the usage of the same idempotency key after an internal error |
| 9004 | 400 | Vault | An existing vault account by the same name already exists Please try to create a different vault account using a different name. |
| 9005 | 400 | Transaction | A transaction with the same idempotency key is in progress Please wait until the previous transaction for this idempotency key is done before issuing a new one |
| 9006 | 400 | Network Connection | Missing required parameter in request body The request you’ve sent is missing the isDiscoverable parameter in the body, make sure it exists and is a boolean, then try again |
| 9007 | 404 | Network Connection | Unknown network id The network ID specified could not be found. Please verify it exists and try again |
| 9009 | 400 | Network Connection | Parameters passed are invalid The parameters passed to the set_routing_policy call are invalid, please make sure they are correct and conform to the API docs, then try again |
| 11001 | 400 | All | The specified vault account is invalid Please make sure that the vault account you’ve specified is correct, valid, and exists |
| 12000 | 400 | All | Cloud provider issue There is an issue with one of our cloud providers. Please check the status page for more details |
