> For the complete documentation index, see [llms.txt](https://docs.cn.omnibridge.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cn.omnibridge.pro/integration/response-code.md).

# 状态码说明

| 状态码  | 说明                                        |
| ---- | ----------------------------------------- |
| 201  | 设备来源不存在                                   |
| 202  | 存币金额小数位数太长                                |
| 203  | 获取存币地址失败                                  |
| 204  | 手续费方式不存在                                  |
| 205  | 手续费方式不能重复设置                               |
| 207  | 地址类型不存在                                   |
| 209  | 目标接收地址不能重复设置                              |
| 210  | 退原币地址不能重复设置                               |
| 212  | 地址类型设置不正确                                 |
| 213  | 非法请求                                      |
| 214  | 币种不存在                                     |
| 215  | 地址不合法                                     |
| 216  | 金额数量不合法                                   |
| 217  | 账户余额不足                                    |
| 218  | 该币种不支持兑换，请重新选择                            |
| 266  | 金额小数点后不能超过两位数字                            |
| 270  | 金额小数点后不能超过4位                              |
| 271  | 金额只能为整数                                   |
| 279  | 小数点后不能超过三位数字                              |
| 311  | 当天交易额度达到上限                                |
| 800  | 成功                                        |
| 900  | 服务器错误                                     |
| 901  | 请求参数不全                                    |
| 902  | 系统启动中                                     |
| 903  | 认证失败                                      |
| 904  | 报文解密失败                                    |
| 905  | 报文处理错误                                    |
| 906  | 系统处理异常                                    |
| 907  | 必填字段为空                                    |
| 908  | 发送报文出错                                    |
| 909  | 报文验密失败                                    |
| 910  | 接收成功                                      |
| 911  | 系统处理错误                                    |
| 912  | 系统无此订单数据                                  |
| 913  | 存入货币币种不存在                                 |
| 914  | 接收货币币种不存在                                 |
| 915  | 存入货币和接收货币不能相同                             |
| 916  | 目标地址不合法                                   |
| 917  | 退款地址不合法                                   |
| 918  | 目标地址和退款地址不能相同                             |
| 919  | 存币金额不合法                                   |
| 920  | 接收币金额不合法                                  |
| 921  | 存币金额不在范围内                                 |
| 972  | <p>操作频繁，请稍后再试<br>eg: 同数量币种连续下单不存币会被拦截</p> |
| 1145 | 目标地址,退款地址或IP存在风险,请换其他地址和IP进行兑换            |
| 1146 | XRP地址未激活该代币                               |
| 1147 | CUBE每日兑换总额度已达上限，暂时无法兑换                    |
| 1154 | 流动性不足                                     |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.cn.omnibridge.pro/integration/response-code.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.