> For the complete documentation index, see [llms.txt](https://docs.bitbrokertrade.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bitbrokertrade.com/snel-aan-de-slag/aankooptransacties.md).

# Aankooptransacties

![](/files/-M4F2F8JSXd02ZU2MATl)

Je ziet het actuele bruto rendement van de posities onder de kop “Rendement”.&#x20;

Je kunt op de pauze button (II) drukken om daarmee verkoop te blokkeren. Als je de positie vast wilt houden ongeacht de koers, dan activeer je de pauze button. De status wijzigt dan in “Hold”. Door nogmaals op de button te drukken maak je de status weer actief en kan de trader weer handelen met deze specifieke positie.&#x20;

Als je de positie wil verkopen en daarmee de trader wil 'overrulen', druk je op de middelste button (groene pijl). De trader vraagt je de opdracht te bevestigingen en gaat direct over tot verkoop tegen de vastgestelde koers.


---

# 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.bitbrokertrade.com/snel-aan-de-slag/aankooptransacties.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.
