> For the complete documentation index, see [llms.txt](https://docs.candelacharts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.candelacharts.com/statistics/ohlc-session-range-map-tm/liquidity.md).
# Liquidity
The **OHLC Session Range Map** features a sophisticated liquidity detection system designed to pinpoint and highlight areas of strong market interest. These zones represent regions where buy and sell orders tend to cluster, increasing the likelihood of price reactions—particularly when they align with key Manipulation and Distribution levels.
By visually displaying the confluence between liquidity pools and manipulation or distribution zones, the tool helps traders anticipate potential reversals and market turning points. Liquidity sensitivity is fully adjustable through a customizable threshold, enabling traders to fine-tune the level of detail to match their strategy and timeframe.
When price moves into a Manipulation or Distribution level that overlaps with a liquidity zone, it often marks a high-probability reversal area. Such confluences frequently indicate deliberate actions by larger market participants, including stop hunts or liquidity sweeps, followed by strong directional moves. Identifying these setups can significantly enhance entry precision, trade validation, and risk control.
The **OHLC Session Range Map** categorizes liquidity into two distinct types:
* **Liquidity Levels** – Active zones where liquidity remains present and price is likely to react.
* **Invalidated Liquidity Levels** – Areas where liquidity has already been absorbed or cleared.
Traders can choose to display or hide invalidated liquidity levels, allowing them to focus on untouched liquidity while still accessing historical liquidity information for deeper market insight.
---
# 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.candelacharts.com/statistics/ohlc-session-range-map-tm/liquidity.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.