> For the complete documentation index, see [llms.txt](https://support.backpack.exchange/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.backpack.exchange/support-docs/cn/jiao-yi-suo/jiao-yi/ding-dan-lei-xing/xian-jia-dan.md).

# 限价单

**限价单 (Limit Order)** 允许你在买入时设定你愿意支付的最高价格，或在卖出时设定你愿意接受的最低价格。

***

### 何时使用？

* 当你想要控制确切的进场或出场价格时。
* 适合耐心等待有利市场条件的交易者。

***

### 关键点&#x20;

成交并不保证 —— 只有当市场价格达到或超过你设定的价格时，订单才会被执行。

***

### 为什么我的限价单最终会以市价单的方式成交？

* 限价单的逻辑是：
  * 买单 (buy order) 会在 **≤ 你设定的价格** 时成交。
  * 卖单 (sell order) 会在 **≥ 你设定的价格** 时成交。
* 如果你 **未启用 Post Only** 选项，系统会在满足价格条件的情况下，立即将你的订单与订单簿中的现有订单匹配。
* 若要确保你的订单始终作为 **挂单 (Maker order)** 被放入订单簿，你需要勾选 **Post Only**。否则，你的订单可能会立即作为 **吃单 (Taker order)** 被执行。

<figure><img src="https://592295428-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fp2WpAGNII69RQ8wSTC1p%2Fuploads%2FGpK5lieGoQe3EAVBusTl%2Fimage.png?alt=media&amp;token=81704a15-2771-4db1-88d9-7a34f9f12f18" alt=""><figcaption></figcaption></figure>

***

**示例 (Example):**

* 你在 30,000 设置了一笔 **BTC/USD 买入限价单 (buy limit order)**。
* 当前最佳卖价是 29,900。
* **结果 (Result):** 系统会立即在 29,900 执行该订单，而不是挂在 30,000 等待。


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.backpack.exchange/support-docs/cn/jiao-yi-suo/jiao-yi/ding-dan-lei-xing/xian-jia-dan.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
