Errors Messages on Cryptowat.ch (trade.kraken.com)

The Cryptowatch trading interface (trade.kraken.com) throws a variety of errors when things go wrong. This document breaks down each error and what it means.

Internal Errors

Internal errors usually mean it’s our fault. 

800: No response from API

Cryptowatch is failing to get a response from Kraken's API. This usually gets resolved with time.

What you can do: Wait and try again. Check status.kraken.com.

801: Network problem

Similar to 800, Cryptowatch's network request to Kraken's API failed.

What you can do: Wait and try again. Check status.kraken.com.

802: Unauthenticated request

Kraken's API returned an authentication error, perhaps because your API keys are invalid.

What you can do: Import a fresh API.

803: Request was rate limited

Kraken's API has rate limited Cryptowatch's request. This should rarely happen and we closely monitor its occurrence.

What you can do: Wait and try again. 

805: API key invalid

Your API key is being rejected by the Kraken's API.

What you can do: Generate a fresh API key with permissions to view & place orders (withdrawal permissions not needed).

806: Invalid nonce

Kraken's API rejected Cryptowatch's 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, generate a fresh API key for use only by Cryptowatch (this is good practice in general). 

808: Timeout

The interface timed out resolving the request (no response for 60 seconds).

What you can do: Timeouts are usually caused by high load on Kraken so it’s likely your request did eventually succeed. Verify if it did. If it did not, wait and try again. Check status.kraken.com.

809: Exchange API is unavailable

Kraken's API is down. This rarely happens.

What you can do: Wait and try again. Check status.kraken.com.

810: Invalid anonymous session

Your anonymous session has expired.

What you can do: Re-authenticate via kraken.com.

820: Internal error

Cryptowatch's service failed for an unpredictable reason, for example the response from Kraken's API was garbled.

What you can do: Wait and try again. If it happens repeatedly, contact Cryptowatch support.

821: Unknown error

This is a catch-all error for when Kraken's API returns an error but Cryptowatch's system doesn’t understand what it means.

What you can do: Wait and try again. If it happens repeatedly, contact Cryptowatch support.

905: Insufficient margin

Kraken does not have sufficient funds to lend out for margin trading.

What you can do: Reduce the order amount, or wait and try again later.

 

User Errors

In this case, it might be your fault.

804: API key lacking necessary privileges

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). 

--OR--

You have 2FA enabled for Trading on Kraken.com.

What client can do: Simply remove 2FA for Trading from Kraken.com (you do not need to remove 2FA for other actions such as Account Login or Funding).

900: Not enough balance

Your order was rejected because you don’t have enough balance to cover it.

What you can do: Reduce the order amount.

901: Order id is invalid

Your request was rejected because the order doesn’t exist anymore.

What you can do: If you were trying to cancel an order, it’s possible it has already been filled or canceled. If you can’t figure out why you got this error, contact Cryptowatch support.

902: Order amount is too small

Your order was rejected because its amount is too small.

What you can do: Increase the order amount.

903: Cannot open position

Kraken's API has rejected your margin order.

What you can do: Reduce the order amount. If you can’t figure out why you got this error, contact Cryptowatch support.

904: Margin allowance exceeded

Your margin order was rejected because you have reached your Margin Borrow Limits.

What you can do:

  • Reduce the order amount.
  • Use a different margin currency pair (e.g. if trying to go long on XBT/USD, try going long on XBT/EUR instead).
  • Increase your verification level.

906: Too many open orders

Your order was rejected because you have too many open orders.

What you can do: Cancel some orders, or wait for them to fill.

907: Too many open positions

Your order was rejected because you have too many open positions.

What you can do: Close some positions.

908: Invalid position

Your request was rejected because the position doesn’t exist anymore.

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, contact Cryptowatch support.

909: Invalid arguments

Your request was rejected 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, contact Cryptowatch support.

910: Invalid price parameter

Your request was rejected 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, contact Cryptowatch support.

911: Invalid amount parameter

Your request was rejected 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, contact Cryptowatch support.

912: Price parameter is too precise

Your order was rejected because the price parameter was too precise.

What you can do: Try using fewer decimal places.

913: Order price is too low/high

Your order was rejected because the price parameter was too low or too high.

What you can do: Try adjusting your price amount.

914: Order size is too low/high

Your order was rejected because the amount parameter was too low or too high.

What you can do: Try adjusting your order amount.