> For the complete documentation index, see [llms.txt](https://docs.flash.trade/flash-trade/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flash.trade/flash-trade/flash-trade-protocol/perpetuals-specifications/stop-loss-take-profit-orders.md).
# Stop Loss/Take Profit Orders
You can attach SL/TP (stop-loss/take-profit) orders to any open position from the **Positions** tab.
* A **Stop-Loss** order caps your losses by closing your position when price reaches your designated level.
* A **Take-Profit** order secures your profits by closing your position when price reaches your designated level.
***
#### How it works
* Set TP/SL when opening a trade (the **Take Profit / Stop Loss** section of the order panel) or add them to any open position from the **Positions** tab.
* Active SL/TP orders appear under the **Orders** tab (**SL/TP** sub-tab), where you can edit trigger prices or cancel.
* On execution you receive the position's backing asset (for example, BTC for a BTC long; USDC for any short).
* Partial exits are supported: up to **5 take-profit and 5 stop-loss orders per market** can ladder out of one position.
* When a position closes — by you or by a trigger — its remaining SL/TP orders cancel automatically.
{% hint style="warning" %}
**Execution is trigger-based, not price-guaranteed.**
* In times of high volatility or congestion, liquidations process first and SL/TP orders may execute at a different price than your trigger.
* On markets with a maximum profit cap, take-profit orders cannot be placed past the price where max profit occurs — see Max Profit.
{% endhint %}
Building a bot instead? The same trigger orders are available programmatically — see Build On Flash.
---
# 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://docs.flash.trade/flash-trade/flash-trade-protocol/perpetuals-specifications/stop-loss-take-profit-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.
