Error Codes
* **-1009:** Withdrawal settlement cannot proceed until the required arrears are deposited.
Details for selected error codes
- -1011: A temporary internal network problem can prevent orders from being placed or cancelled; retry after a few seconds.
- -1012: An internal module may reject an order, for example while the account is being liquidated or because of another internal error; retry after a few seconds. The same code can also report that another liquidation is already in progress.
- -1101: If risk exposure is too high, check current exposure through the client information endpoint. This code also covers operations that would leave insufficient margin.
- -1103: The price may be below
quote_min, abovequote_max, or not aligned with the market tick size. - -1104: Quantity may be below
base_min, abovebase_max, or not aligned with the step size; visible quantity can also fail the step-size check. - -1105: The price may be
X%above orX%below the mid price. - -1201: When total notional is below
10000, the minimum request ratio is1; another message indicates the request ratio must match the specified value. - -1202: Liquidation may not be needed because margin is sufficient, or the supplied liquidation ID may not exist.
The following table lists API error codes, their HTTP statuses, and their meanings.
| Error code | HTTP status | Description |
|---|---|---|
| -1000 | 500 | An unexpected error occurred while processing the request. |
| -1000 | 500 | The requested data does not exist. |
| -1001 | 401 | The API key or secret has an invalid format. |
| -1002 | 401 | The API key or secret is invalid, lacks the required permission, has expired, or was revoked. |
| -1003 | 429 | The rate limit has been exceeded. |
| -1004 | 400 | The request contains an unrecognized parameter. |
| -1005 | 400 | One or more parameters have an invalid format. |
| -1005 | 400 | ratio_qty_request must be from 0 to 1. |
| -1005 | 400 | extra_liquidation_ratio must be from 0 to 1. |
| -1005 | 400 | If extra_liquidation_ratio is greater than 0, ratio_qty_request must equal 1. |
| -1006 | 400 | The requested data cannot be found on the server. For example, cancelling an order that is already cancelled returns this error. |
| -1007 | 409 | The data already exists or the request is duplicated. |
| -1008 | 400 | The settlement quantity is greater than the permitted amount. |
| -1009 | 400 | Withdrawal settlement is unavailable; settle outstanding arrears first. |
| -1011 | 400 | An internal network issue currently prevents order placement or cancellation. |
| -1012 | 400 | The order was rejected by an internal module, such as when the account is in liquidation. |
| -1012 | 400 | A liquidation is already being processed. |
| -1101 | 400 | Risk exposure is too high, which can result from a large order or low leverage. |
| -1101 | 400 | The operation would leave insufficient margin. |
| -1102 | 400 | The order value, calculated as price multiplied by size, is too small. |
| -1103 | 400 | The order price is below quote_min, above quote_max, or does not align with the tick size. |
| -1104 | 400 | The order quantity is below base_min, above base_max, or does not align with the step size. |
| -1104 | 400 | The visible quantity does not align with the step size. |
| -1105 | 400 | The price is too far above or below the mid price. |
| -1201 | 400 | The liquidation request ratio does not meet the required value. |
| -1202 | 400 | No liquidation is required because the account margin is sufficient, or the specified liquidation ID cannot be found. |