# TRADE Interface

### Request for explanation

* This document is for partners who have applied for the channel number channelId and private key at us.
* Partner requirements: Provide channel name, register account.
* Request type: POST  application/json.
* Error code description:

  | Error code | Explanation                                              |
  | ---------- | -------------------------------------------------------- |
  | 800        | SUCCESS                                                  |
  | 900        | The system is busy, please try again later               |
  | 1100       | The trading pair is invalid                              |
  | 1101       | The trading pair does not exist                          |
  | 1102       | The depth does not exist                                 |
  | 1103       | The trading type is invalid                              |
  | 1104       | The trading price is invalid                             |
  | 1105       | The trading price accuracy is too long                   |
  | 1106       | The trading amount is invalid                            |
  | 1107       | The trading amount accuracy is too long                  |
  | 1108       | The minimum trading amount cannot be lower than 0.01 ETH |
  | 1109       | The minimum trading sum cannot be lower than 0.01 ETH    |
  | 1110       | Cancellation successful                                  |
  | 1111       | Cancellation fail                                        |


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs-swft.en.swft.pro/trade-api/swft-trade-interface.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.