> For the complete documentation index, see [llms.txt](https://docs.symm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.symm.io/trader-documentation/building-a-trading-bot/part-2-trading/take-profit-stop-loss.md).

# Take-profit / stop-loss

TP/SL is a deferred close. You sign a typed-data message now, the conditional-orders handler (COH) holds it, and when the trigger price is hit the COH submits a real close to the solver on your behalf. That's why the bot delegation exists.

### A different domain and message shape

Unlike opens and closes, TP/SL doesn't use the `SymmioInstantLayer` domain. It uses:

```
domain = {
    name: "ConditionalOrder",
    version: "1",
    chainId: <chain id>,
    verifyingContract: <InstantLayer address>      // same address
}
```

The message has a top level with seven scalar fields and three nested "leg" structs:

* `virtualAccount`: the VA holding the position
* `subAccount`: the parent sub-account
* `salt`: random `uint256`
* `quoteId`: `int256` (yes, `int` for some reason; the value is positive)
* `symbolId`, `positionType`, `affiliate`
* `takeProfit`: leg struct (see below)
* `stopLoss`: leg struct (see below)
* `sendQuote`: leg struct with an extra `leverage` field (see below)

**All three legs must be present** even if you're only setting one. The COH rejects messages with missing legs. Zero-fill the unused legs:

```
zero_leg = {
    "quantity": "0", "price": "0", "orderType": 0,
    "conditionalPrice": "0", "conditionalPriceType": "market"
}
zero_send = { ...zero_leg, "leverage": 0 }
```

For an active leg, the fields mean:

* `quantity`: total quantity to close (decimal string, must match symbol's `quantity_precision`)
* `price`: current mark price as a reference (decimal string, must match `price_precision`)
* `orderType`: `1` for MARKET
* `conditionalPrice`: the *trigger* price (decimal string, must match `price_precision`)
* `conditionalPriceType`: typically `"last_close"`

**Decimal precision matters here.** The COH rejects unbounded decimals with `error_code: 407` "provided values do not meet the required precision standards". If `price_precision = 6`, send `"0.013242"`, not `"0.013241567893"`. Same for `quantity` and `conditionalPrice`.

You can sanity-check your typed-data encoder: hit `GET <conditional-orders endpoint>/signing-spec` (with the deployment's `App-Name` header) and you'll get back the live, authoritative type schema plus an `expectedMessageHash` for the included example. Encode that example with your library and confirm you produce the same hash.

### POST it

```
POST <conditional-orders endpoint>
App-Name: <your app name>
Content-Type: application/json

{
  "typedData": { /* the full {types, domain, primaryType, message} */ },
  "signer": "<sessionKey address>",
  "signature": "0x..."
}
```

`200 { "successful": true }` means the order is registered. The COH will fire it on trigger, you'll see `TriggeredTPSL` on the notifications feed, and a normal close fill will follow.

Failure modes worth recognizing on sight:

* `401 "parent subaccount has not delegated required access to COH for selectors=REQUEST_TO_CLOSE_POSITION"` with `recovered_signer = 0x2471...`: the bot delegation is missing. Re-run it.
* `401 "recovered signer is neither owner nor active session key"`: the session-key delegation for `0x00000001` is gone (expired or never granted). Re-run it.
* `401 "virtualAccount X does not match predicted VA Y"`: your sub-account doesn't have `singleVAMode = true`. This can't be fixed on the existing sub-account; create a new one.
* `400 error_code 407`: precision. Quantize before sending.
* `404` on a quote that already has a TP/SL: one-shot per quote. Cancel the existing order or open a new position.


---

# 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.symm.io/trader-documentation/building-a-trading-bot/part-2-trading/take-profit-stop-loss.md?ask=<question>&goal=<endgoal>
```

`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.