> 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 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://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 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.