Updated .
Can Freqtrade act on an outside price alert?
Freqtrade's webhook page describes the bot posting its own messages out. It does not describe an outside alert coming in. Outside data reaches a strategy when the strategy fetches it, when another Freqtrade instance sends analyzed candles, or when you call a force-entry command on the bot's own API.
What the webhook page describes
On 12 November 2026, Freqtrade's stable webhook page described messages the bot posts to an address you set. You turn the section on and set that address. The page does not describe TradingView, or any other sender, posting into the bot.
The messages cover an order that increases a position, on either side, its fill, and its cancel; an exit order, its fill, and its cancel; and a status line such as started or stopped. Discord is another address the bot can post to. The retry count defaults to 0. See when a trading webhook fails.
What one instance can send another
The producer and consumer page, opened the same day, describes one Freqtrade instance listening to another over a message websocket. The consumer sets a host, a port that defaults to 8080, and a websocket token. The page says to set the token to something random and known only to you. What moves is analyzed candle tables and the active pair list. The initial candle count must be between 100 and 1,500, and the default is 1,500. A setting can set the entry and exit columns to 0 when the table arrives. The default leaves them in place. The sender on that page is another Freqtrade instance.
Where a strategy fetches outside data
The strategy callbacks page, opened the same day, names loop start as a place for loading outside data. It runs about every 5 seconds in dry-run and live, unless you set a different pace, or once per candle in a backtest or a hyperopt run. Bot start runs once, after the strategy loads. Both samples read a remote address only in live or dry-run. The page does not describe an address that accepts an outside post.
What the REST API lets a caller do
The REST API page, opened the same day, stays off until you enable it. By default it listens on the local machine only. The page says not to expose the API to the internet, because others could then control the bot. A force-entry route runs only when a separate setting is on. The default side is long. The page does not describe a chart product posting an alert to that route.
What project members wrote
On 5 January 2026 a person asked how an outside system could send a pair, a side, and an enter or an exit into Freqtrade. On 6 January 2026 a project member wrote that the REST API already covered the request, and wrote against that approach. It said to run the backtest in Freqtrade, said a forced entry stays subject to the strategy's ordinary logic, and called this possible to some degree and not the project's main way of working. The issue closed the same day.
How a saved cursor reads each alert once
The events feed lists alerts you set, oldest first, and returns the next cursor. Store it and send it back, and you read each alert once. Latest, the default, starts after the newest alert, so the first page stays empty until a new one arrives. The feed keeps alerts for 7 days. A gap means an alert after your cursor has aged out. Read the rule's record, or one alert by its id, and drop duplicates by id.
The Freqtrade guide reads this feed on a background thread in live or dry-run. With no saved cursor, the first request starts at latest. After a restart, a readable cursor continues from that place. Alerts already read stay hidden, the in-memory list starts empty, and alerts after that cursor that are still inside 7 days come back oldest first. A missing file starts after the newest alert. If the file cannot be read, the log says the feed starts after the newest alert, and that alerts recorded while the strategy was stopped are not read.
What the helper writes
The helper starts from bot start, in live or dry-run, and sends the key as a bearer token. Loop start does not request the feed. It writes two informational columns on the latest row only. Older rows stay at 0. One counts that coin's alerts over 60 minutes, until you change it. The other is the headline of the latest alert in that window. The entry and exit columns stay at 0 until you write a condition. The helper does not place an order. Setup is in the Freqtrade guide and on how an API key is created.
What a backtest can see
A backtest does not call the API, so the alert columns stay empty. The helper does not invent past alerts.
What the free plan allows
On 12 November 2026 the home page listed an API under works today, with a key on every plan, and said Free includes 1,000 calls a month. Free, from the quotas page:
| Limit | Free |
|---|---|
| API keys | 1 |
| Included calls in a UTC month | 1,000 |
| Calls a minute, per key | 10 |
An empty events page is not counted. The per-minute limit still counts every request.
That day the developers page said the API and the MCP tools carry price, percent-move, volume, and unusual-move alerts. World-event, funding, open-interest, and index alerts stay in the app, and the events feed leaves them out. The alert schema names price above, price below, percent change, volume spike, and unusual move.
Signed webhooks to a server you choose were listed under built, opening later. Quotas show that destination on Pro, not on Free. The home page said paid plans are not open yet. The webhook page describes a post to an address you choose, not a post into Freqtrade.
Terminal reads the alerts you set into a Freqtrade strategy as informational columns, in live or dry-run mode, and never chooses a side, an amount, or a trade. It is not investment advice.
FAQ
Can TradingView post straight into Freqtrade?
No. On 12 November 2026 the webhook page described the bot posting its own messages out, not TradingView posting in. On 6 January 2026 a project member pointed that kind of request at the REST API and wrote against that approach.
Does an alert column place an order?
No. On the latest row the helper writes a count of that coin's alerts over 60 minutes, and the headline of the latest one in that window. Entry and exit columns stay at 0 until you write a condition. The helper does not place an order.
What happens to missed alerts when the bot restarts?
A readable cursor continues from the saved place. Alerts after it that are still in the 7-day feed come back oldest first, each once. Alerts already read do not. A missing or unreadable file starts after the newest alert, so alerts already recorded are not read.
Sources
Opened 2026-11-12 unless a page prints its own date.
- Freqtrade, webhook usage: outgoing messages, retry count 0.
- Freqtrade, producer and consumer mode: one instance feeds another.
- Freqtrade, strategy callbacks: outside data in live or dry-run.
- Freqtrade, REST API: local listen address, force-entry route.
- Freqtrade, issue opened 5 January 2026: reply on 6 January 2026.
- Home page, works today: key on every plan, Free's monthly calls, signed webhooks not open.
- Developers page, alert kinds: which kinds the API carries.