IDEX error codes and descriptions

errors.txt

TradeError --

  '1': 'Order not found',
This happens when the client tries to fill an order that has been sniped during his attempt to match and sign and dispatch

  '2': 'Trade signature invalid. Please try again.',
Self explanatory, invalid signature from the client (probably due to ledger issues)

  '3': 'You have insufficient funds to place this order.',
Taker has insufficient funds to execute trade

  '4': 'You have insufficient funds to place this order.',
Maker has insufficient funds to execute trade (possibly due to the client falling out of sync with the server due to connection problems, or some kind of server-side glitch)


  '5': 'Order signature invalid',
self explanatory

  '6': 'Withdrawal signature invalid. Please try again.',
self explanatory, but this one actually isnt used. see 12

  '7': 'Insufficient balance for withdrawal',
self explanatory, but this one actually isnt used. see 13

  '8': 'Cancel signature invalid. Please try again.',
self explanatory

  '9': 'Order cannot be filled by this many units',
order is still on the books, but has been partially filled during trade execution before the client could update. Can be caused by sync issues

  '10': 'Nonce too low',
self explanatory, this hopefully should never happen unless the client is spamming actions

  '11': 'Account submitting cancel does not match order account.',
Trying to cancel an order is not yours

  '12': 'Withdrawal signature invalid. Please try again.',
Self explanatory

  '13': 'You cannot withdraw more than your balance.',
Self explanatory

  '14': 'You have insufficient funds to place this order.',
Happens when someone tries to make an order and doesnt have enough funds

  '15': 'You must cancel some of your orders before you can withdraw this balance.',
Not implemented

  '16': 'Please enter a valid amount.',
Not used

  '17': 'Please enter a valid amount.',
Happens when amountSell or amountBuy is equal to 0 when making an order

  '18': 'Value of order must be at least %s USD, please try making a larger order.',
Self explanatory

  '19': 'Minimum trade amount not met. Please try a larger total amount (met %s of minimum).',
Self explanatory

  '20': 'All trades filled must be for the same currency pair',
Not used, see 23

  '21': 'User %s must cancel open orders before being able to place trade',
Not implemented

  '22': 'Each trade in list must be for a separate order',
Prevents people doing many partial fills for the same order in a multitrade

  '23': 'All trades in list must be for the same token pair',
Prevents people making multitrades across different markets, which is not yet tested

  '24': 'All trades must be from the same user',
Prevents people making multitrades across different users

  '25': 'Cannot place a trade for 0 units',
Self explanatory

  '26': 'Invalid token pair'
Happens when someone tries to execute a trade for a pair that we dont allow


APIError --
  '1': '%s',
arbitrary message, used to report unexpected errors from the runtime over the websocket

  '2': 'Method "%s" not found',
used in the WS RPC when a consumer tries to execute a method that isnt allowed or not a valid method in the RPC

  '3': 'Chat log-in signature invalid',
self explanatory

  '4': 'User not logged in',
Happens when someone tries to abuse the RPC by posting a message without logging in

  '5': 'Username already taken, please choose another.',
self explanatory

  '6': 'Username must be 15 or fewer characters.',
self explanatory

  '7': 'Message must contain characters',
message refers to chat message

  '8': 'Reward proportions signature invalid',
used to validate the signature of the rewards slider

  '9': 'Fee string not a number',
an invalid payload in the reward sliders, due to abuse

  '10': 'Fee string out of range',
an invalid payload in the reward slider where the number is not 0-100, due to abuse

  '11': 'Username cannot contain spaces',
self explanatory

  '12': 'Max message length exceeded',
message limit is 800 chars

  '13': 'Minimum withdrawal of %s USD required (met %s of minimum). Please enter a higher amount.',
self explanatory

  '14': 'Cannot withdraw 0 or under',
Only used during 0 withdrawals, preliminary validation weeds out negative numbers for withdrawals, see 17

  '15': 'Cannot change username once set',
self explanatory

  '16': 'No orders to cancel',
cancel all response when no orders exist

  '17': 'Invalid payload',
A catch-all error message which is given to people trying to abuse the RPC with bogus values that are not the correct type, prevents negative numbers, invalid ethereum addresses, etc

  '18': 'Maximum payload size exceeded',
Prevents the RPC from parsing messages that are over 50000 chars, due to abuse

  '19': 'To perform this action, you must have no outstanding orders which were made before orders which have been cancelled',
Prevents the server from invalidating orders that are outstanding during a mine cancel event. The client never sees this message unless he is using the RPC directly, since we prompt the user to first cancel his outstanding orders on the client

  '20': 'No cancelled orders to invalidate',
Self explanatory (mine cancels event)

  '21': 'Order invalidation signature invalid',
Self explanatory (mine cancels event)

  '22': 'Target nonce must be one higher than your last cancelled order nonce',
Prevents the server from invalidating anything except the bare minimum nonce, the client should never see this message

  '23': 'Invalid chat name'
Occurs when the chat name is reserved by us, (reserved words: IDEX Mod Support Help Aurora Team)