# 业务状态码

| 状态码   | 说明           | 建议                                                      |
| ----- | ------------ | ------------------------------------------------------- |
| 0     | 成功           |                                                         |
| 100   | 请求参数错误       | 通常出现在`POST`请求上，请检查 json 结构是否正确                          |
| 103   | 无效签名         | 请查看 [生成签名](/chinese/shuo-ming/qian-ming-sheng-cheng.md) |
| 104   | 签名过期         | 请重新签名或检查服务器时间。                                          |
| 11000 | 操作失败，请稍后再试   | 通常是业务发生变化，或不能操作，可放弃或重试，根据 `msg` 的提示进行调整                 |
| 11001 | 操作过于频繁，请稍后再试 | 针对`app_id`限制每秒钟请求 `5` 次。请降低请求频率或新增应用                    |
| 11003 | 缺少必要参数       | 请仔细核对文档和实际请求的参数类型和值是否合理有效                               |
| 12001 | 数据已存在        |                                                         |
| 12002 | 数据不存在        |                                                         |
| 12003 | 数据为空         |                                                         |
| 20000 | 应用不存在        |                                                         |
| 20001 | 应用已被禁用       |                                                         |
| 20002 | 余额不足         | 请到用户中心 充值                                               |
| 20003 | 配额不足         |                                                         |
| 20004 | 请求频率受限       |                                                         |
| 20005 | 无效参数         | 根据 `msg` 的提示进行调整                                        |


---

# 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://apidoc.tokenpay.me/chinese/cuo-wu-ma/ye-wu-zhuang-tai-ma.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.