> 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/exchange/trading/order-types/conditional-orders.md). # Conditional Orders A Conditional Order is an instruction to buy or sell an asset once certain market conditions are met, such as reaching a specific trigger price. When the trigger condition is activated, the order is placed automatically as a market or limit order. ### **When to Use？** * When you want to **automate entries or exits** based on price movement. * To **protect against losses** (e.g., stop-loss) or **lock in profits** (e.g., take-profit). * When you cannot monitor the market continuously but want orders to be placed automatically at key levels. *** ### **Key Points** * Provides flexibility by combining trigger conditions with order execution. * Can be set as a **stop-market** or **stop-limit** order after the condition is met. * Execution is not guaranteed if the market does not reach the trigger price, or if there is insufficient liquidity at the chosen limit price. * Commonly used for **risk management** and **strategic trading automation**. --- # 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/exchange/trading/order-types/conditional-orders.md?ask=&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.