On error, all MetaKeep HTTP APIs return non-200 HTTP code. The response also contains a JSON object with a status
field which looks like this:
{
status: "INVALID_REQUEST"
}
You can find list of error status returned by all MetaKeep APIs below.
Common Errors
The table below lists all the common errors returned by MetaKeep APIs.
Status | HTTP Code | Description |
---|---|---|
UNAUTHORIZED | 401 | The request is not authorized. This can happen if the API key , Account key , or App id is invalid or if the request is not signed correctly. |
INVALID_ACCOUNT_KEY | 401 | The provided key is not a valid account key. Account keys start with account_key_ . |
FORBIDDEN | 403 | The request is forbidden. This can happen if the API key , Account key , or App id does not have access to the requested resource. |
INVALID_REQUEST | 400 | The request data is invalid. This can happen if the request is missing the required fields or if the request data is malformed. |
UNSUPPORTED_OPERATION | 400 | The API is not supported on the chain. Please contact us if you need support for this API on the chain. |
SOMETHING_WENT_WRONG | 500 | An unknown error occurred. Please get in touch with us if you continue seeing this error. |
/v3/getWallet
Status | HTTP Code | Description |
---|---|---|
INVALID_EMAIL | 400 | The user email is not a valid email. |
/v3/getWallet/multiple
Status | HTTP Code | Description |
---|---|---|
INVALID_EMAIL | 400 | One of the user emails is not a valid email. |
TOO_MANY_USERS_REQUESTED | 400 | You are trying to query wallets for a lot of users. Please check the API limitations. |
/v3/wallet/getUser
Status | HTTP Code | Description |
---|---|---|
INVALID_WALLET_ADDRESS | 400 | The provided wallet address is not valid. |
USER_NOT_FOUND | 404 | No user was found for the provided wallet address. |
/v3/getDeveloperWallet
Status | HTTP Code | Description |
---|---|---|
MISSING_APP_ID | 400 | The appId field is missing in the request. This is required when making requests using the account keys. |
FORBIDDEN | 403 | The API key is not valid. |
/v2/app/nft/createCollection
Status | HTTP Code | Description |
---|---|---|
FORBIDDEN | 403 | Api key is not valid. |
INVALID_REQUEST | 400 | Request is not valid e.g. if request json has unsupported fields. |
INVALID_NAME | 400 | Collection name is either empty or too long. Collection name currently has a character limit of 20. Our current recommendation is to use metadata/name for a verbose name which has the added bonus of ability to dynamically change the collection name without fees. |
INVALID_SYMBOL | 400 | Collection symbol is either empty or too long. Collection symbol currently has a character limit of 10. |
INVALID_METADATA | 400 | Collection metadata is invalid e.g. invalid uri, invalid fee recipient. |
IDEMPOTENCY_KEY_MISSING | 400 | Idempotency key is missing. |
IDEMPOTENCY_PARAMS_MISMATCH | 409 | Another request with the same Idempotency key has different request body. |
SOMETHING_WENT_WRONG | 500 | Unknown error occurred. Please get in touch with us if you continue seeing this error. |
/v2/app/nft/listCollections
Status | HTTP Code | Description |
---|---|---|
FORBIDDEN | 403 | Api key is not valid. |
SOMETHING_WENT_WRONG | 500 | Unknown error occurred. Please get in touch with us if you continue seeing this error. |
/v2/app/nft/listTokens
Status | HTTP Code | Description |
---|---|---|
FORBIDDEN | 403 | Api key is not valid. |
FORBIDDEN_CONTRACT_NOT_OWNED | 403 | Api key is not allowed to perform operations on the collection. |
INVALID_REQUEST | 400 | Request is not valid e.g. if request json has unsupported fields. |
INVALID_COLLECTION | 400 | Collection address is not valid or doesn't exist. |
TOO_MANY_COLLECTIONS | 400 | You have provide more than 20 collections in the request. Note that you can get all NFTs owned by the user by not sending any collection in the request. |
INVALID_USER | 400 | of user is not valid.Currently we only support email and eth address. |
SOMETHING_WENT_WRONG | 500 | Unknown error occurred. Please get in touch with us if you continue seeing this error. |
/v2/app/nft/lock
Status | HTTP Code | Description |
---|---|---|
FORBIDDEN | 403 | Api key is not valid. |
FORBIDDEN_CONTRACT_NOT_OWNED | 403 | Api key is not allowed to perform operations on the collection. |
INVALID_REQUEST | 400 | Request is not valid e.g. if request json has unsupported fields. |
INVALID_COLLECTION | 400 | Collection address is not valid or doesn't exist. |
INVALID_TOKEN | 400 | Token is empty or invalid. |
IDEMPOTENCY_KEY_MISSING | 400 | Idempotency key is missing. |
IDEMPOTENCY_PARAMS_MISMATCH | 409 | Another request with the same Idempotency key has different request body. |
SOMETHING_WENT_WRONG | 500 | Unknown error occurred. Please get in touch with us if you continue seeing this error. |
/v2/app/nft/unlock
Status | HTTP Code | Description |
---|---|---|
FORBIDDEN | 403 | Api key is not valid. |
FORBIDDEN_CONTRACT_NOT_OWNED | 403 | Api key is not allowed to perform operations on the collection. |
INVALID_REQUEST | 400 | Request is not valid e.g. if request json has unsupported fields. |
INVALID_COLLECTION | 400 | Collection address is not valid or doesn't exist. |
INVALID_TOKEN | 400 | Token is empty or invalid. |
IDEMPOTENCY_KEY_MISSING | 400 | Idempotency key is missing. |
IDEMPOTENCY_PARAMS_MISMATCH | 409 | Another request with the same Idempotency key has different request body. |
SOMETHING_WENT_WRONG | 500 | Unknown error occurred. Please get in touch with us if you continue seeing this error. |
/v2/app/nft/mint
Status | HTTP Code | Description |
---|---|---|
FORBIDDEN | 403 | Api key is not valid. |
FORBIDDEN_CONTRACT_NOT_OWNED | 403 | Api key is not allowed to perform operations on the collection. |
INVALID_REQUEST | 400 | Request is not valid e.g. if request json has unsupported fields. |
INVALID_COLLECTION | 400 | Collection address is not valid or doesn't exist. |
INVALID_METADATA | 400 | Token metadata is invalid e.g. invalid uri. |
INVALID_TARGET | 400 | Mint to user is not valid.Currently we only support email and eth address. |
IDEMPOTENCY_KEY_MISSING | 400 | Idempotency key is missing. |
IDEMPOTENCY_PARAMS_MISMATCH | 409 | Another request with the same Idempotency key has different request body. |
SOMETHING_WENT_WRONG | 500 | Unknown error occurred. Please get in touch with us if you continue seeing this error. |
/v2/app/nft/transfer
Status | HTTP Code | Description |
---|---|---|
FORBIDDEN | 403 | The API key is not valid or the current user is not allowed to perform the nft transfer. |
FORBIDDEN_CONTRACT_NOT_OWNED | 403 | The API key is not allowed to perform operations on the collection. |
INVALID_REQUEST | 400 | Request is not valid e.g. if request json has unsupported fields. |
INVALID_COLLECTION | 400 | The collection address is not valid or doesn't exist. |
INVALID_TOKEN | 400 | The token is empty or invalid. |
FORBIDDEN_TOKEN_NOT_OWNED | 403 | The token is not owned by the from user. |
TOKEN_NOT_FOUND | 404 | The token doesn't exist on the chain. |
INVALID_FROM_USER | 400 | Transfer from user is not valid.Currently, only email address is supported. |
INVALID_TARGET | 400 | Transfer to user is not valid.Currently, only email and external wallet addresses are supported. |
IDEMPOTENCY_KEY_MISSING | 400 | Idempotency key is missing. |
IDEMPOTENCY_PARAMS_MISMATCH | 409 | Another request with the same Idempotency key has a different request body. |
SOMETHING_WENT_WRONG | 500 | An unknown error occurred. Please get in touch with us if you continue seeing this error. |
/v2/nft/metadata
This endpoint doesn't return status in the response body
HTTP Code | Description |
---|---|
400 | Request is not valid e.g. if query params has unsupported fields. |
404 | No metadata found for the nft token. |
500 | Unknown error occurred. Please get in touch with us if you continue seeing this error. |
/v2/app/nft/metadata/updateToken
Status | HTTP Code | Description |
---|---|---|
FORBIDDEN | 403 | Api key is not valid. |
FORBIDDEN_CONTRACT_NOT_OWNED | 403 | Api key is not allowed to perform operations on the collection. |
INVALID_REQUEST | 400 | Request is not valid e.g. if request json has unsupported fields. |
INVALID_COLLECTION | 400 | Collection address is not valid. |
INVALID_METADATA | 400 | Token metadata is invalid e.g. invalid uri. |
INVALID_TOKEN | 400 | Token is empty or invalid. |
SOMETHING_WENT_WRONG | 500 | Unknown error occurred. Please get in touch with us if you continue seeing this error. |
/v2/app/nft/metadata/updateCollection
Status | HTTP Code | Description |
---|---|---|
FORBIDDEN | 403 | Api key is not valid. |
FORBIDDEN_CONTRACT_NOT_OWNED | 403 | Api key is not allowed to perform operations on the collection. |
INVALID_REQUEST | 400 | Request is not valid e.g. if request json has unsupported fields. |
INVALID_COLLECTION | 400 | Collection address is not valid. |
INVALID_METADATA | 400 | Collection metadata is invalid e.g. invalid uri. |
IDEMPOTENCY_KEY_MISSING | 400 | Idempotency key is missing. |
IDEMPOTENCY_PARAMS_MISMATCH | 409 | Another request with the same Idempotency key has different request body. |
SOMETHING_WENT_WRONG | 500 | Unknown error occurred. Please get in touch with us if you continue seeing this error. |
/v2/app/coin/createCurrency
Status | HTTP Code | Description |
---|---|---|
FORBIDDEN | 403 | Api key is not valid. |
INVALID_REQUEST | 400 | Request is not valid e.g. if request json has unsupported fields. |
INVALID_NAME | 400 | Collection name is either empty or too long. Collection name currently has a character limit of 20. |
INVALID_SYMBOL | 400 | Collection symbol is either empty or too long. Collection symbol currently has a character limit of 10. |
IDEMPOTENCY_KEY_MISSING | 400 | Idempotency key is missing. |
IDEMPOTENCY_PARAMS_MISMATCH | 409 | Another request with the same Idempotency key has different request body. |
SOMETHING_WENT_WRONG | 500 | Unknown error occurred. Please get in touch with us if you continue seeing this error. |
/v2/app/coin/listCurrencies
Status | HTTP Code | Description |
---|---|---|
FORBIDDEN | 403 | Api key is not valid. |
SOMETHING_WENT_WRONG | 500 | Unknown error occurred. Please get in touch with us if you continue seeing this error. |
/v2/app/coin/mint
Status | HTTP Code | Description |
---|---|---|
FORBIDDEN | 403 | Api key is not valid. |
FORBIDDEN_CONTRACT_NOT_OWNED | 403 | Api key is not allowed to perform operations on the collection. |
INVALID_REQUEST | 400 | Request is not valid e.g. if request json has unsupported fields. |
INVALID_CURRENCY | 400 | Currency address is not valid or doesn't exist. |
INVALID_AMOUNT | 400 | Mint amount is not valid. |
INVALID_TARGET | 400 | Mint to user is not valid.Currently we only support email and eth address. |
IDEMPOTENCY_KEY_MISSING | 400 | Idempotency key is missing. |
IDEMPOTENCY_PARAMS_MISMATCH | 409 | Another request with the same Idempotency key has different request body. |
SOMETHING_WENT_WRONG | 500 | Unknown error occurred. Please get in touch with us if you continue seeing this error. |
/v2/app/coin/lock
Status | HTTP Code | Description |
---|---|---|
FORBIDDEN | 403 | Api key is not valid. |
FORBIDDEN_CONTRACT_NOT_OWNED | 403 | Api key is not allowed to perform operations on the collection. |
INVALID_REQUEST | 400 | Request is not valid e.g. if request json has unsupported fields. |
INVALID_CURRENCY | 400 | Currency address is not valid or doesn't exist. |
INVALID_AMOUNT | 400 | Lock amount is not valid. |
INVALID_USER | 400 | User whose coins to lock is not valid. Currently we only support email and eth address. |
IDEMPOTENCY_KEY_MISSING | 400 | Idempotency key is missing. |
IDEMPOTENCY_PARAMS_MISMATCH | 409 | Another request with the same Idempotency key has different request body. |
SOMETHING_WENT_WRONG | 500 | Unknown error occurred. Please get in touch with us if you continue seeing this error. |
/v2/app/coin/unlock
Status | HTTP Code | Description |
---|---|---|
FORBIDDEN | 403 | Api key is not valid. |
FORBIDDEN_CONTRACT_NOT_OWNED | 403 | Api key is not allowed to perform operations on the collection. |
INVALID_REQUEST | 400 | Request is not valid e.g. if request json has unsupported fields. |
INVALID_CURRENCY | 400 | Currency address is not valid or doesn't exist. |
INVALID_AMOUNT | 400 | Unlock amount is not valid. |
INVALID_USER | 400 | User whose coins to lock is not valid. Currently we only support email and eth address. |
IDEMPOTENCY_KEY_MISSING | 400 | Idempotency key is missing. |
IDEMPOTENCY_PARAMS_MISMATCH | 409 | Another request with the same Idempotency key has different request body. |
SOMETHING_WENT_WRONG | 500 | Unknown error occurred. Please get in touch with us if you continue seeing this error. |
/v2/app/coin/burn
Status | HTTP Code | Description |
---|---|---|
FORBIDDEN | 403 | Api key is not valid. |
FORBIDDEN_CONTRACT_NOT_OWNED | 403 | Api key is not allowed to perform operations on the collection. |
INVALID_REQUEST | 400 | Request is not valid e.g. if request json has unsupported fields. |
INVALID_CURRENCY | 400 | Currency address is not valid or doesn't exist. |
INVALID_AMOUNT | 400 | Burn amount is invalid. |
INVALID_USER | 400 | Burn from user is not valid.Currently we only support email and eth address. |
IDEMPOTENCY_KEY_MISSING | 400 | Idempotency key is missing. |
IDEMPOTENCY_PARAMS_MISMATCH | 409 | Another request with the same Idempotency key has different request body. |
SOMETHING_WENT_WRONG | 500 | Unknown error occurred. Please get in touch with us if you continue seeing this error. |
/v2/app/coin/balance
Status | HTTP Code | Description |
---|---|---|
FORBIDDEN | 403 | The API key is not valid. |
INVALID_REQUEST | 400 | The request is not valid e.g. if the request json has unsupported fields. |
INVALID_CURRENCY | 400 | The currency address is not valid or doesn't exist. |
MISSING_CURRENCY_LIST | 400 | The request is missing the list of currencies. |
TOO_MANY_CURRENCIES | 400 | You have provided more than 20 currencies in the request. Note that you can get all currencies owned by the user by not sending any currency in the request. |
SOMETHING_WENT_WRONG | 500 | An unknown error occurred. Please get in touch with us if you continue seeing this error. |
/v2/app/coin/transfer
Status | HTTP Code | Description |
---|---|---|
FORBIDDEN | 403 | Api key is not valid or current user is not allowed to perform the coin transfer. |
FORBIDDEN_CONTRACT_NOT_OWNED | 403 | Api key is not allowed to perform operations on the collection. |
INVALID_REQUEST | 400 | Request is not valid e.g. if request json has unsupported fields. |
INVALID_CURRENCY | 400 | Currency address is not valid or doesn't exist. |
INVALID_SYMBOL | 400 | Currency symbol is not valid or doesn't exist. |
INVALID_AMOUNT | 400 | Transfer amount is invalid. |
INVALID_FROM_USER | 400 | Transfer from user is not valid.Currently we only support email address and developer's own account. |
INVALID_TARGET | 400 | Transfer to user is not valid.Currently we only support email and eth address. |
IDEMPOTENCY_KEY_MISSING | 400 | Idempotency key is missing. |
IDEMPOTENCY_PARAMS_MISMATCH | 409 | Another request with the same Idempotency key has different request body. |
SOMETHING_WENT_WRONG | 500 | Unknown error occurred. Please get in touch with us if you continue seeing this error. |
/v2/app/sign/transaction
Status | HTTP Code | Description |
---|---|---|
INVALID_REASON | 400 | The reason for signing the transaction is not valid. |
MISSING_NONCE | 400 | The nonce is missing. Please specify nonce for the transaction. |
MISSING_GAS | 400 | Gas is missing. Please specify gas for the transaction. |
INVALID_GAS_FEE_PARAMS | 400 | The transaction contains gasPrice maxFeePerGas and maxPriorityFeePerGas . Please specify either gasPrice or maxFeePerGas and maxPriorityFeePerGas |
MISSING_GAS_PRICE | 400 | Gas price is missing for type 1 transactions. Please specify gasPrice . |
MISSING_MAX_FEE_PER_GAS | 400 | The max fee per gas is missing for type 2 transactions. Please specify both maxFeePerGas and maxPriorityFeePerGas . |
MISSING_MAX_PRIORITY_FEE_PER_GAS | 400 | The max priority fee per gas is missing for type 2 transactions. Please specify both maxFeePerGas and maxPriorityFeePerGas . |
FROM_ADDRESS_DOES_NOT_MATCH_SIGNER | 400 | The from address in the transaction message does not match the signer's address. |
/v2/app/sign/transaction/multiple
Status | HTTP Code | Description |
---|---|---|
INVALID_REASON | 400 | The reason for signing the transaction is not valid. |
MISSING_NONCE | 400 | The nonce is missing. Please specify nonce for the transaction. |
MISSING_GAS | 400 | Gas is missing. Please specify gas for the transaction. |
INVALID_GAS_FEE_PARAMS | 400 | The transaction contains gasPrice maxFeePerGas and maxPriorityFeePerGas . Please specify either gasPrice or maxFeePerGas and maxPriorityFeePerGas |
MISSING_GAS_PRICE | 400 | Gas price is missing for type 1 transactions. Please specify gasPrice . |
MISSING_MAX_FEE_PER_GAS | 400 | The max fee per gas is missing for type 2 transactions. Please specify both maxFeePerGas and maxPriorityFeePerGas . |
MISSING_MAX_PRIORITY_FEE_PER_GAS | 400 | The max priority fee per gas is missing for type 2 transactions. Please specify both maxFeePerGas and maxPriorityFeePerGas . |
FROM_ADDRESS_DOES_NOT_MATCH_SIGNER | 400 | The from address in the transaction message does not match the signer's address. |
TOO_MANY_TRANSACTIONS | 400 | There are too many transactions in the batch. Currently, only up to 5 transactions are supported in a single batch. |
/v2/app/sign/message
Status | HTTP Code | Description |
---|---|---|
FORBIDDEN | 403 | Api key is not valid. |
INVALID_REQUEST | 400 | Invalid data passed to sign operation. Please get in touch with us if you are unable to fix this. |
SOMETHING_WENT_WRONG | 500 | Unknown error occurred. Please get in touch with us if you continue seeing this error. |
/v2/app/sign/typedData
Status | HTTP Code | Description |
---|---|---|
FORBIDDEN | 403 | Api key is not valid. |
INVALID_REQUEST | 400 | Invalid data passed to sign operation. Please get in touch with us if you are unable to fix this. |
SOMETHING_WENT_WRONG | 500 | Unknown error occurred. Please get in touch with us if you continue seeing this error. |
/v2/app/transaction/status
Status | HTTP Code | Description |
---|---|---|
FORBIDDEN | 403 | Api key is not valid. |
INVALID_REQUEST | 400 | Request is not valid e.g. if request json has unsupported fields. |
NOT_FOUND | 404 | Transaction not found. |
SOMETHING_WENT_WRONG | 500 | Unknown error occurred. Please get in touch with us if you continue seeing this error. |
/v2/app/lambda/create
Status | HTTP Code | Description |
---|---|---|
FORBIDDEN | 403 | The API key is not valid. |
BYTECODE_EXCEEDS_MAX_SIZE | 400 | Max supported bytecode size is 23 KB. Note that the EVM contract size limit is 24.576 KB. Our limit is slightly lower to prevent users from experiencing random errors for large contracts. Let us know if you are unable to resolve this. We will be happy to help with contract resizing. |
INVALID_REQUEST | 400 | The request is not valid e.g. if the request json has unsupported fields. |
NAME_ARG_MISSING | 400 | The constructor is missing the lambdaName argument. lambdaName is a required constructor argument. |
INVALID_NAME | 400 | Lambda's name is either empty or too long. Lambda's name currently has a character limit of 20. |
OWNER_ARG_MISSING | 400 | The constructor is missing the lambdaOwner argument. lambdaOwner is a required constructor argument. |
INVALID_OWNER | 400 | The Lambda owner is not the same as the developer's wallet address. Make sure you are initializing the lambda by passing in your developer account eth address as the lambda owner. |
NAMES_DO_NOT_MATCH | 400 | The name provided in the name field and constructor lambdaName arg do not match. |
IDEMPOTENCY_KEY_MISSING | 400 | Idempotency key is missing. |
IDEMPOTENCY_PARAMS_MISMATCH | 409 | Another request with the same Idempotency key has a different request body. |
SOMETHING_WENT_WRONG | 500 | An unknown error occurred. Please get in touch with us if you continue seeing this error. |
/v2/app/lambda/import
Status | HTTP Code | Description |
---|---|---|
FORBIDDEN | 403 | The API key is not valid. |
INVALID_REQUEST | 400 | The request is not valid e.g. if the request json has unsupported fields. |
INVALID_ABI | 400 | The abi is not valid. |
INVALID_NAME | 400 | Lambda's name is either empty or too long. Lambda's name currently has a character limit of 20. |
INVALID_LAMBDA | 400 | The lambda address in the request is not valid |
LAMBDA_ALREADY_EXISTS | 400 | Lambda with the same address already exists. Use /v2/app/lambda/update API to update the lambda. |
CONTRACT_NOT_FOUND | 400 | A deployed contract with the given address was not found on the chain. Please make sure that the contract is deployed and the address is correct. |
SOMETHING_WENT_WRONG | 500 | An unknown error occurred. Please get in touch with us if you continue seeing this error. |
/v2/app/lambda/listLambdas
Status | HTTP Code | Description |
---|---|---|
FORBIDDEN | 403 | The API key is not valid. |
SOMETHING_WENT_WRONG | 403 | An unknown error occurred. Please get in touch with us if you continue seeing this error. |
/v2/app/lambda/invoke
Status | HTTP Code | Description |
---|---|---|
FORBIDDEN | 403 | The API key is not valid. |
FORBIDDEN_CONTRACT_NOT_OWNED | 403 | The API key is not allowed to perform operations on the lambda. |
INVALID_REQUEST | 400 | The request is not valid e.g. if the request json has unsupported fields. |
INVALID_REASON | 400 | The invocation reason is not provided. |
INVALID_DESCRIPTION_TEXT | 400 | The invocation description text is not provided |
INVALID_DESCRIPTION_IMAGE | 400 | The invocation description image URL is not valid. |
INVALID_USER_TYPE | 400 | Invoke as user is not valid.Currently, we only support email addresses. |
INVALID_FUNCTION | 400 | The provided function is not valid |
INVALID_FUNCTION_READ_ONLY | 400 | You are trying to invoke a read-only (pure or view) function. Use /v2/app/lambda/read api to read data from lambda. |
INVALID_FUNCTION_NOT_PAYABLE | 400 | You are trying to send payment(value) to a function that is not payable . |
INVALID_ARGS | 400 | Function args list is not valid |
INVALID_PAYMENT_AMOUNT | 400 | The payment amount provided is not a valid decimal string. |
INVALID_MESSAGE | 400 | The serialized Solana transaction message is not valid. |
MESSAGE_HAS_NO_SIGNERS | 400 | The serialized Solana transaction message does not have any required signers. |
USER_IS_NOT_SIGNER | 400 | The user invoking the lambda is not a signer for the serialized Solana transaction message. |
INVALID_SIGNERS | 400 | The provided signers are invalid. This can happen if the signers are not valid public keys or if the signers are not the signers of the provided serialized transaction message. |
INVALID_EXTERNAL_SIGNATURE | 400 | The provided external signature is not valid for the serialized Solana transaction message. |
INSUFFICIENT_EXTERNAL_SIGNATURES | 400 | The number of external signatures provided is less than the required number of signatures for the serialized Solana transaction message. Please make sure all external signers have signed before sending the request. |
INVALID_SPONSOR | 400 | The transaction fee payer is not valid. Use the /v2/app/lambda/getSponsor API to get the sponsor for the transaction. |
SPONSOR_PAYMENT_NOT_ENABLED | 400 | This happens when the Sponsor account is used as an input to an instruction for rent payments/refunds. To safeguard your developer account from misuse and unexpected bills , the Sponsor only pays for transaction fees by default. Please get in touch with us if you need rent payment enabled for your app. |
PRIORITY_FEE_TOO_HIGH | 400 | The priority fee(compute price on Solana) is too high. Currently, the maximum compute price that can be set on Solana is 1000000(1 million) . |
INVALID_SIGNATURES | 400 | The provided signatures are invalid. This can happen if the signatures are not valid signatures for the provided serialized transaction message. |
CONTRACT_NOT_SUPPORTED_USE_BUSINESS_WALLET | 400 | The lambda contract can only be invoked using theBUSINESS_WALLET |
PAYMENT_NOT_SUPPORTED_USE_BUSINESS_WALLET | 400 | The payment(value transfer) is only supported when using theBUISNESS_WALLET . |
IDEMPOTENCY_KEY_MISSING | 400 | Idempotency key is missing. |
IDEMPOTENCY_PARAMS_MISMATCH | 409 | Another request with the same Idempotency key has a different request body. |
SOMETHING_WENT_WRONG | 500 | An unknown error occurred. Please get in touch with us if you continue seeing this error. |
/v2/app/lambda/invoke/multiple
Status | HTTP Code | Description |
---|---|---|
FORBIDDEN | 403 | The API key is not valid. |
FORBIDDEN_CONTRACT_NOT_OWNED | 403 | The API key is not allowed to perform operations on the lambda. |
INVALID_REQUEST | 400 | The request is not valid e.g. if the request json has unsupported fields. |
INVALID_REASON | 400 | The invocation reason is not provided. |
INVALID_DESCRIPTION_TEXT | 400 | The invocation description text is not provided |
INVALID_DESCRIPTION_IMAGE | 400 | The invocation description image URL is not valid. |
INVALID_USER_TYPE | 400 | Invoke as user is not valid.Currently, we only support email addresses. |
INVALID_FUNCTION | 400 | The provided function is not valid |
INVALID_FUNCTION_READ_ONLY | 400 | You are trying to invoke a read-only (pure or view) function. Use /v2/app/lambda/read api to read data from lambda. |
INVALID_FUNCTION_NOT_PAYABLE | 400 | You are trying to send payment(value) to a function that is not payable . |
INVALID_ARGS | 400 | Function args list is not valid |
INVALID_PAYMENT_AMOUNT | 400 | The payment amount provided is not a valid decimal string. |
INVALID_PAYMENT_RECIPIENT | 400 | The payment recipient is not valid. |
CONTRACT_NOT_SUPPORTED_USE_BUSINESS_WALLET | 400 | The lambda contract can only be invoked using theBUSINESS_WALLET |
PAYMENT_NOT_SUPPORTED_USE_BUSINESS_WALLET | 400 | The payment(value transfer) is only supported when using theBUISNESS_WALLET . |
BATCH_INVOCATION_UNSUPPORTED_USE_BUSINESS_WALLET | 400 | Batch invocation is only supported when using theBUISNESS_WALLET . |
BATCH_INVOCATION_SIZE_EXCEEDED | 400 | The batch size is more than allowed. Please check API docs for the allowed batch size. |
IDEMPOTENCY_KEY_MISSING | 400 | Idempotency key is missing. |
IDEMPOTENCY_PARAMS_MISMATCH | 409 | Another request with the same Idempotency key has a different request body. |
SOMETHING_WENT_WRONG | 500 | An unknown error occurred. Please get in touch with us if you continue seeing this error. |
/v2/app/lambda/read
Status | HTTP Code | Description |
---|---|---|
FORBIDDEN | 403 | The API key is not valid. |
FORBIDDEN_CONTRACT_NOT_OWNED | 403 | The API key is not allowed to perform operations on the lambda. |
INVALID_REQUEST | 400 | The request is not valid e.g. if the request JSON has unsupported fields. |
INVALID_LAMBDA | 400 | The lambda address in the request is not valid |
INVALID_FUNCTION | 400 | The provided function is not valid |
NO_MATCHING_FUNCTION_FOUND | 400 | No function was found matching the name and args in the request. |
NOT_READ_ONLY_FUNCTION | 400 | You are trying to call a function that's not read-only (pure or view). Use /v2/app/lambda/invoke API to invoke write functions and send a transaction. |
READ_SIZE_EXCEEDED | 400 | You are trying to read a lot of data at once. Please go through the Lambda Read Limits doc for more information. |
SOMETHING_WENT_WRONG | 500 | An unknown error occurred. Please get in touch with us if you continue seeing this error. |
/v2/app/lambda/read/events
Status | HTTP Code | Description |
---|---|---|
FORBIDDEN | 403 | The API key is not valid. |
FORBIDDEN_CONTRACT_NOT_OWNED | 403 | The API key is not allowed to perform operations on lambda. |
INVALID_REQUEST | 400 | The request is not valid e.g. if the request JSON has unsupported fields. |
INVALID_LAMBDA | 400 | The lambda address in the request is not valid |
TOO_MANY_LAMBDAS | 400 | The request contains more lambdas than what is allowed. Please check the API documentation for the limits. |
NEWEST_BLOCK_BEFORE_OLDEST_BLOCK | 400 | The newest block number is before the oldest block number. |
INVALID_BLOCK_NUMBER | 400 | The block number is invalid. You can provide an integer string, hex string, or "LATEST". |
TOO_MANY_BLOCKS_TO_READ_FROM | 400 | The block range is too large. Please check the API documentation for the limits. |
SOMETHING_WENT_WRONG | 500 | An unknown error occurred. Please get in touch with us if you continue seeing this error. |
/v2/app/lambda/update
Status | HTTP Code | Description |
---|---|---|
FORBIDDEN | 403 | The API key is not valid. |
FORBIDDEN_CONTRACT_NOT_OWNED | 400 | The API key is not allowed to perform operations on lambda. |
INVALID_REQUEST | 400 | The request is not valid e.g. if the request JSON has unsupported fields. |
UNSUPPORTED_CONTRACT_TYPE | 400 | This happens if you are trying to update NFT or Coin contracts deployed using NFT/Coin APIs. You can only update your custom lambda contracts. |
INVALID_LAMBDA | 400 | The lambda address in the request is not valid. |
INVALID_ABI | 400 | The ABI is not valid. |
SOMETHING_WENT_WRONG | 500 | An unknown error occurred. Please get in touch with us if you continue seeing this error. |
/v2/app/lambda/getBusinessWallet
Status | HTTP Code | Description |
---|---|---|
INVALID_USER | 400 | The user in the request is not valid e.g. if the user email format is invalid. |
INVALID_REQUEST | 400 | The request is not valid e.g. if the request json has unsupported fields. |
SOMETHING_WENT_WRONG | 500 | An unknown error occurred. Please get in touch with us if you continue seeing this error. |
/v2/app/lambda/getBusinessWallet/multiple
Status | HTTP Code | Description |
---|---|---|
INVALID_USER | 400 | One of the users is not valid. |
TOO_MANY_USERS_REQUESTED | 400 | You are trying to query wallets for a lot of users. Please check the API limitations. |
INVALID_REQUEST | 400 | The request is not valid e.g. if the request json has unsupported fields. |
/v2/app/lambda/businessWallet/getUser
Status | HTTP Code | Description |
---|---|---|
INVALID_WALLET_ADDRESS | 400 | The provided wallet address is not valid. |
USER_NOT_FOUND | 404 | No user was found for the provided wallet address. |
/v2/app/lambda/getSponsor
Status | HTTP Code | Description |
---|---|---|
INVALID_REQUEST | 400 | The request is not valid e.g. if the request JSON has unsupported fields. |
SOMETHING_WENT_WRONG | 500 | An unknown error occurred. Please get in touch with us if you continue seeing this error. |
/v2/app/create
Status | HTTP Code | Description |
---|---|---|
INVALID_NAME | 400 | The app name is invalid. It should be between 1 and 64 characters long. |
INVALID_CHAIN_ID | 400 | The chain ID is invalid. Please check the API documentation for the list of supported chain IDs. |
INVALID_REQUEST | 400 | The request is not valid e.g. if the request json has unsupported fields. |
SOMETHING_WENT_WRONG | 500 | An unknown error occurred. Please get in touch with us if you continue seeing this error. |
/v2/app/update
Status | HTTP Code | Description |
---|---|---|
INVALID_NAME | 400 | The app name is invalid. It should be between 1 and 64 characters long. |
INVALID_DISPLAY_NAME | 400 | The display name is invalid. It should be between 1 and 64 characters long. |
INVALID_URL | 400 | The logo URL is not a valid URL string. |
INVALID_COLOR | 400 | The provided color is not in a valid format. It should be a valid RGB color code in hex format (e.g. #FA2323). |
INVALID_ORIGIN | 400 | One of the origins is not in a valid format. |
INVALID_REQUEST | 400 | The request is not valid e.g. if the request json has unsupported fields. |
INVALID_POLICY_MISSING_ADMIN | 400 | The policy quorum is invalid because it's missing the account admin. |
INVALID_QUORUM_MEMBER_SOL_ADDRESS | 400 | The policy quorum member type is SOL_ADDRESS but the public key is not a valid SOL address. |
INVALID_POLICY | 400 | The policy is invalid. |
FORBIDDEN_BY_POLICY | 403 | The action is forbidden by the app policy. |
SOMETHING_WENT_WRONG | 500 | An unknown error occurred. Please get in touch with us if you continue seeing this error. |
/v2/app/list
Status | HTTP Code | Description |
---|---|---|
APP_ID_FILTER_LIST_TOO_LONG | 400 | The number of app IDs in the filter list exceeds the maximum allowed limit of 20. |
SOMETHING_WENT_WRONG | 500 | An unknown error occurred. Please get in touch with us if you continue seeing this error. |
© Copyright 2024, Passbird Research Inc.