> For the complete documentation index, see [llms.txt](https://docs.apex.win/apex-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apex.win/apex-docs/order-types/limit-orders.md). # Limit Orders Your entire order gets executed at your limit price, or better. Should a better price be available than you originally indicated, the size of your order will stay as originally input, but you will be deleveraged if needed. ### Examples Alice sets a limit buy for 1 ETH at 1500, while it trades at 1600. For this she is willing to provide a 750 USD margin. A large sell order pushes the vAMM price below 1500, so the bot executes her order. Alice will end up with a position of 1 ETH at 2x leverage or less. Bob sets a reduce-only limit sell for 100 Sushi at 18 USD. He already has a 100 Sushi long position and he only wants to take profit, hence the reduce only parameter. The bots will only execute the order at the given price or better. --- # 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.apex.win/apex-docs/order-types/limit-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.