> For the complete documentation index, see [llms.txt](https://docs.ventuals.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ventuals.com/trading/liquidations.md).

# Liquidations

What happens if a trade goes bad?

If a trade moves too far against you and you don’t have enough margin to support it, your position may be liquidated — meaning it gets force-closed to prevent losses from exceeding your available balance.

***

## **When do liquidations happen?**

Every position has a minimum margin requirement, based on the leverage you use. The higher the leverage, the less margin is required — but the closer you are to liquidation.

Here’s how much margin you need to maintain:

* 1x leverage → minimum margin: 50%
* 2x leverage → minimum margin: 25%
* 3x leverage → minimum margin: 16.67%
* 5x leverage → minimum margin: 10%
* 10x leverage → minimum margin: 5%
* 20x leverage → minimum margin: 2.5%

If your account value (including unrealized PnL) falls below this level, Ventuals will automatically close your position at market. If there's any margin left after closing, it stays in your account.

## **How to avoid liquidation**

To lower your chances of being liquidated:

* Use lower leverage to give yourself more breathing room
* Set stop-losses to manage downside risk
* Monitor your liquidation price (shown in the UI)
* Add more margin when you're getting close

## **How liquidation price works**

When you open a trade, we calculate a liquidation price **—** the point at which your losses become too large to support your position. This price can move over time due to funding payments or changes in your other open trades.

Higher leverage = higher risk, because even small price moves can push you into liquidation territory. Trade accordingly.


---

# 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.ventuals.com/trading/liquidations.md?ask=<question>&goal=<user_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.
