Links

Trading Interface Errors

The Cryptowatch trading interface throws a variety of errors when things go wrong. Sometimes things go wrong — usually it's our fault, but sometimes it's the exchange's fault (or even your fault).
You can check Cryptowatch's status page at any time to see if there are any performance issues.

Internal Errors

Internal errors usually mean it's our fault, or perhaps the exchange's fault. It's definitely not your fault.

800: No Response

What it means: We're failing to get a response from the exchange's API. This usually gets resolved with time.
What you can do: Monitor the API response and uptime on Cryptowatch's status page. If this issue persists, wait and try again.

801: Network Problem

What it means: Similar to 800, our network request to the exchange's API failed.
What you can do: Monitor the API response and uptime on Cryptowatch's status page. If this issue persists, wait and try again.

802: Unauthenticated Request

What it means: The exchange's API returned an authentication error, perhaps because your API keys are invalid.
What you can do: Import a fresh API.

803: Rate Limited

What it means: The exchange's API has rate limited our request. This error occasionally occurs when you open/close order(s) too quickly.
What you can do: Wait and try again — read What to do when you are being rate limited for more information.

804: Unprivileged Key

What it means: Your API key does not have the privileges needed to trade with it.
What you can do: Generate a fresh API key with permissions to view & place orders (withdrawal permissions not needed). Every exchange has a different interface for choosing privileges when generating an API key. Read the Connecting Exchange Accounts article for help connecting API keys.

805: Invalid Key

What it means: Your API key is being rejected by the exchange's API.
What you can do: Generate a fresh API key with permissions to view & place orders (withdrawal permissions not needed).

806: Invalid Nonce

What it means: The exchange's API rejected our request because the nonce was too small.
What you can do: Try again. If it happens repeatedly, make sure you're not using the same API key somewhere else. If you are, please generate a fresh API key for use only by Cryptowatch (this is good practice in general).

807: Invalid Timestamp

What it means: The exchange's API rejected our request because the timestamp was invalid.
What you can do: Try again. If it happens repeatedly, please contact support.

808: Invalid Passphrase

What it means: The exchange's API rejected our request because the passphrase associated with your API key is wrong. This error is specific to Coinbase Pro.
What you can do: Generate a fresh API key with permissions to view & place orders (withdrawal permissions not needed) and make sure to input the key passphrase correctly.

809: Invalid Signature

What it means: The exchange's API rejected our request because the cryptographic signature that we provided was invalid.
What you can do: Please ensure you're using a valid API Key and you have provided the correct API Key Secret. If the issue persists, generate a new API Key with permissions to view & place orders and try again. If the issue still persists, please contact support.

810: Timeout

What it means: The interface timed out resolving the request (no response for 60 seconds).
What you can do: Timeouts are usually caused by high load on the exchange so it's likely your request did eventually succeed. Please verify if it did. If it did not, wait and try again. If it happens repeatedly, please contact support.

811: Unavailable

What it means: The Exchange's API is unavailable/down. This rarely happens.
What you can do: Monitor the API response and uptime on the exchange's status page, if available. Wait and try again.

812: Invalid Session

What it means: The anonymous session has expired. This error is specific to Kraken Pro.
What you can do: Re-authenticate via kraken.com.

813: Too Many Requests

What it means: The exchange has too many requests to process at this moment and we have to wait for some to be resolved.
What you can do: Try again after a short period of time.

814: IP Banned

What it means: IP addressed is banned — too many request have been made to the exchange by Cryptowatch.
What you can do: Try again after a short period of time. If this issue persists please contact support.

815: Bad Argument

What it means: A bad argument was passed to the API. The format of the request provided to the exchange was invalid.
What you can do: Please contact support.

816: Forbidden

What it means: The exchange has rejected the action for lacking permissions. Your API keys may lack the proper permissions for this action, or the exchange requires you to update your terms agreement.
What you can do: Log in to your exchange account and agree to any updated terms. Alternatively, you may need to generate a new API key with updated permissions. If the issue persists, please contact support.

820: Internal

What it means: Our service failed for an unpredictable reason, for example the response from the exchange's API was garbled.
What you can do: Wait and try again. If it happens repeatedly, please contact support.

821: Unknown

What it means: This is a catch-all error for when the exchange's API returns an error but our system doesn't understand what it means.
What you can do: Wait and try again. If it happens repeatedly, please contact support.

822: Unimplemented

What it means: Our service failed to properly implement the API client for the exchange.
What you can do: Please contact support.

2503: Error placing order

What it means: When contacting the exchange, the exchange's site returned an HTTP 503 error. This error means the service is temporarily unavailable. In other words, the exchange is experiencing downtime.
What you can do: Monitor the Website response and uptime on the exchange's status page. If this issue persists, wait and try again or contact support.

User Errors

‌These errors usually mean the issue occurred on your end.

900: Not Enough Balance

What it means: The exchange's API rejected your order because you don't have enough balance to cover it.
What you can do: Reduce the order amount, cancel any open orders that may be locking up funds, or check to see if order was partially filled.

901: Order ID Invalid

What it means: The exchange's API rejected your request because it was dealing with an order that, according to them, doesn't exist.
What you can do: If you were trying to cancel an order, it's possible it has already been filled or canceled. Check your exchange account to see if the order still exists. If you can't figure out why you got this error, please contact support.

902: Order Amount Too Low

What it means: The exchange's API rejected your order because its amount is too low.
What you can do: Increase the order amount. Check to see if your exchange has minimum order size parameters.

903: Order Price Too Low

What it means: The exchange's API rejected your order because its price is too low.
What you can do: Increase the order price.

904: Order Amount Too High

What it means: The exchange's API rejected your order because its amount is too high.
What you can do: Decrease the order amount.

905: Order Price Too High

What it means: The exchange's API rejected your order because its price is too high.
What you can do: Decrease the order price.

906: Cannot Open Position

What it means: The exchange's API rejected your margin order.
What you can do: Reduce the order amount. If you can't figure out why you got this error, please contact support.

907: Margin Allowance Exceeded

What it means: The exchange's API rejected your margin order.
What you can do: Reduce the order amount based on your exchange's margin allowance limits, or check to see if the order is partially filled. If you can't figure out why you got this error, please contact support.

908: Insufficient Margin

What it means: The exchange does not have sufficient funds to allow margin trading.
What you can do: Reduce the order amount, or wait and try again later.

909: Too Many Orders

What it means: The exchange's API rejected your order because you have too many open orders.
What you can do: Cancel some orders, or wait for them to fill.

910: Too Many Positions

What it means: The exchange's API rejected your margin order because you have too many open positions.
What you can do: Close some positions.

911: Position Invalid

What it means: The exchange's API rejected your request because it was dealing with a position that, according to them, doesn't exist.
What you can do: Re-sync the interface to see if the position has already been closed. If you can't figure out why you got this error, please contact support.

912: Invalid Arguments

What it means: The exchange's API rejected your request because the request parameters were invalid.
What you can do: It's possible this was caused by a bug in our trading backend. If you can't figure out why you got this error, please contact support.

913: Price Invalid

What it means: The exchange's API rejected your request because the price parameter was invalid.
What you can do: It's possible this was caused by a bug in our trading backend. If you can't figure out why you got this error, please contact support.

914: Amount Invalid

What it means: The exchange's API rejected your request because the amount parameter was invalid.
What you can do: It's possible this was caused by a bug in our trading backend. If you can't figure out why you got this error, please contact support.

915: Price Too Precise

What it means: The exchange's API rejected your request because the price parameter was too precise.
What you can do: Try using fewer decimal places. Alternatively, disable the "Validate inputs client-side" setting under the Trading Preferences menu.

916: Invalid Order Price

What it means: The exchange's API rejected your request because the price parameter was either too low or too high.
What you can do: Try adjusting your price amount.

917: Invalid Order Size

What it means: The exchange's API rejected your request because the amount parameter was either too low or too high.
What you can do: Try adjusting your order amount. Make sure it exceeds your exchange's minimum order size, if applicable.

918: Invalid Leverage

What it means: The exchange's API rejected your request because the leverage parameter was either too low or too high.
What you can do: Try adjusting your leverage parameter.

919: Invalid Close Price

What it means: The exchange's API rejected your request because the close parameter was either too low or too high.
What you can do: Try adjusting your close price parameter.

920: Invalid Lot Size

What it means: The exchange's API rejected your request because the size (quantity) of your order was either too high, too low, or using the incorrect amount of decimal precision for that market (too many or two few decimal places).
What you can do: Try adjusting your order amount based on the supported decimal precision for that market.

922: Error placing order

What it means: The exchange has entered post-only, cancel-only, or limit-only mode — only orders of these types will be accepted during the corresponding mode, all other order types will be rejected.
What you can do: Attempt a different order type, disable order options relevant to the exchange's restrictions, or contact your exchange's support team to determine which restriction the exchange has applied.

923: Trading Restricted in Region

What it means: The market you are attempting to trade in is not available in your region, per the policy of the exchange. Exchanges may restrict markets in certain regions to abide by local laws.
What you can do: Continue to advocate for cryptocurrency adoption.

2xxx: HTTP Errors

HTTP errors return an error code with a “2” leading the HTTP error code.
Example: A 504 error (504 Gateway Timeout) appears as 2504.
What it means: an HTTP error code has occurred while using Cryptowatch / Kraken Terminal. The cause of an HTTP error code varies — see this wikipedia article for a list of HTTP errors for further information.
What you can do: Depending on the error code returned, you may only need to refresh the page. Monitor the API response and uptime on Cryptowatch’s Status page. You may want to check your exchange’s status page as well. If the problem persists, please contact support.