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

# News trading

Use Proliquid News to move from market-moving headlines to Hyperliquid, Binance, Bybit, and OKX execution with a clear validation and monitoring flow.

Use the news trading workflow when a headline, social post, listing, exploit, macro event, or official announcement may move a market quickly.

Proliquid connects the [News](/features/crypto-news-feed-for-trading.md) feed with matched markets, quick LONG / SHORT actions, and the [Terminal](/features/hyperliquid-trading-terminal.md), so you can move from information to execution without switching tools.

## When to use it

Use this workflow when:

* A news item is time-sensitive.
* The item has a clear matched market.
* The market is moving from the news timestamp.
* You need to decide between fast execution and more controlled execution.

Confirm liquidity, price reaction, and whether the news is already priced in.

## Tabs to open

<table><thead><tr><th width="159.97265625">Step</th><th width="239.3359375">Open this</th><th>Why</th></tr></thead><tbody><tr><td>Detect</td><td><a href="/features/crypto-news-feed-for-trading.md">News</a></td><td>Read the item, source, matched markets, and timestamp.</td></tr><tr><td>Validate</td><td><a href="/terminal-sections/news.md">Terminal News</a> and <a href="/terminal-sections/chart.md">Chart</a></td><td>Confirm market reaction and chart context.</td></tr><tr><td>Execute</td><td><a href="/terminal-sections/trade-form.md">Trade form</a></td><td>Use full controls when quick actions are not enough.</td></tr><tr><td>Monitor</td><td><a href="/terminal-sections/positions.md">Positions</a>, <a href="/terminal-sections/trade-history.md">Trade history</a>, <a href="/terminal-sections/order-history.md">Order history</a></td><td>Confirm fills, exposure, fees, and follow-up actions.</td></tr></tbody></table>

## What to validate

Before trading from news, check:

* Source credibility and whether the item is original or reposted.
* Matched market and exchange source.
* Price change since Proliquid received the news.
* Current spread and visible orderbook depth.
* Whether related markets are also moving.
* Your account exposure, margin, and existing position on the market.

If the move is already extended, consider whether chasing with a market order still makes sense.

## Order types that fit

<table><thead><tr><th width="586.23828125">Situation</th><th>Order type</th></tr></thead><tbody><tr><td>You need immediate exposure and accept taker execution</td><td><a href="/order-types/market-orders.md">Market</a></td></tr><tr><td>You want maker-only entry near the current bid or ask</td><td><a href="/order-types/limit-orders.md">Limit ALO</a></td></tr><tr><td>You want maker-only behavior that follows the best bid or ask</td><td><a href="/order-types/chase-orders.md">Chase</a></td></tr><tr><td>You want to enter over a few minutes after the first reaction</td><td><a href="/order-types/twap-orders.md">TWAP</a></td></tr><tr><td>You want faster split execution with refill time between batches</td><td><a href="/order-types/burst-orders.md">Burst</a></td></tr></tbody></table>

## What to monitor afterward

After submitting:

* Confirm fills in [Trade history](/terminal-sections/trade-history.md).
* Confirm submitted actions in [Order history](/terminal-sections/order-history.md).
* Watch [Positions](/terminal-sections/positions.md) for PNL, funding, TP / SL, and margin.
* Keep [News](/features/crypto-news-feed-for-trading.md) open for follow-up headlines or corrections.

## Common mistakes

* Trading a headline without checking whether the price already moved.
* Using Market on thin books without reviewing slippage.
* Forgetting to set reduce-only when reacting from an existing position.
* Ignoring follow-up news that changes the original thesis.
* Treating a matched market as certainty instead of a suggested connection.


---

# 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.proliquid.xyz/workflows/news-trading.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.