API Responses
HTTP Status Codes
200 - OK - Request was processed as expected
400 - Bad request - The request cannot be fulfilled.
403 - Permission Denied - It means that the user has no permissions. For example, when a non-admin user tries to run createMpcUser.
405 - Method Not Allowed - It means that the system is in cold-driven mode or when the session is in approval status and the user sends a non-cancel and revise API request.
428 - Precondition Required - It means that the user tries to make an administrative change before starting an administrative session.
459 - Request Number Is Not Sequential - It means that the request contains a non-sequential number
460 - Invalid Session Number - It means that the session number is invalid.
461 - Object Equals To The Edited Object - It means that the object the user wants to edit is the same as it is now.
462 - Not Enough Online Cosigners - Only the startAdministrativeSession API can respond with StatusCode 462. It means the system does not have enough cosigners online at the time of the request.
463 - Requests Per Session Limit Reached - This means that the current session has reached its request limit and either must be canceled or submitted.
464 - Session Initiated By Other User - It means that the request sender is not the initiator.
500 - Server Error - It means that we have a bug on the server side. More information should be logged.
More specific Errors Status Codes
Error Code | HTTP Status Code | Relevant Features | Issue and Remediation |
|---|---|---|---|
7012 | | All | MPC wallet connection error Verify that the system is up. |
1007 | 400 | All | Wrong account id / Account {account number} has not been initialized Verify that you pass an existing account id. |
1007 | 400 | All | Coin {coin type} is not supported Verify that you pass coin types that are supported by the system. |
1007 | 400 | Accounts | CoinSymbols should be a list Check that you pass a list [“BTC”] and not a simple string “BTC”. |
1009 | 400 | Accounts | Invalid coins provided Verify that you pass utxo coin types. |
1000 | 500 | Wallets | Requested wallet id: {wallet id} is already assigned There is already a wallet with that id, please enter another one. |
1009 | 400 | Wallets | {coin type} is not a valid coin! Verify that you pass coin types that are supported in the system. |
1009 | 400 | Wallets | The following currencies are not supported for an omnibus account due to having a memo: {coin types} Verify that the coin types you pass don’t have a memo. |
1000 | 500 | Wallets | Wallet name can contain alphanumeric characters (can be separated with a space) Verify that the wallet names you pass contain only letters, numbers and spaces. |
1007 | 400 | Wallets | Bad data format, the following fields: {fields} should be a list Verify that you pass a list. |
1000 | 500 | Wallets | Wallet: {wallet id} was not found Verify that there is a wallet with such an id. |
1007 | 400 | Wallets | Address is invalid, This isn't a valid address: {address} Verify that the address is correct. |
1007 | 400 | Wallets | The address {address} is not of account {account number} Verify that the address is of the correct account. |
1000 | 500 | Wallets | The given address {address} is in the wrong size Verify that the address is correct. |
1007 | 400 | Wallets | Maximal number of wallets are 1000 Verify that the number you pass is from 1 to 1000. |
1000 | 400 | Wallets | Wallet was not found Verify that there is a wallet with such an id. |
1007 | 500 | Transactions | At least 1 HBAR is needed for creating a new address
|
1000 | 400 | Transactions | Polkadot node is not synced!
|
1000 | 400 | Transactions | Could not find a relevant policy for the requested transaction / Not allowed by policy - no policy allows you to transfer {coin type} to the requested destination Verify that there is a relevant policy defined before making transactions. |
1000 | 400 | Transactions | Please fill currencies rate in the cold wallet before sending a transaction
|
1009 | 400 | Transactions | Rule RuleTransactionPassLimits failed: Maximum fee per user per frequency has been exceeded definition in user's role / The requested fee exceeds limit
|
1009 | 400 | Transactions | Stellar transactions can not be sent with fee lower than 100 XLM Stroop
|
1003 | 400 | Transactions | Not enough funds for requested transaction Verify that you have enough funds. |
1009 | 400 | Transactions | The requested storage exceeds limit |