Trading halts interrupt the orderly flow of quotes and can reprice a stock faster than any headline. A volatility pause, news pending halt, or LULD band breach stops trading for a defined period, and the resumption often gaps from the last trade. Desks that monitor halts in real time avoid sending orders into a frozen symbol and can prepare for the reopening print.
Vantafin does not stream opening auction indications or net order imbalance data. What we do provide is the H WebSocket channel for trading halts and resumptions, with reason codes and LULD pause threshold prices where applicable. This tutorial builds a halt monitor that surfaces active pauses across your coverage universe. New to streaming? See the WebSocket API overview.
Subscribe to halt events
Connect with your API key and subscribe to the H channel for symbols in your watchlists. Send {"action":"subscribe","params":"H.AAPL"} for a single symbol, or batch subscriptions via the channels array documented in the WebSocket docs. Halt messages arrive when an exchange pauses or resumes trading) not continuously like OHLCV, but at the moments that matter for execution and risk.
Each message carries the fields surveillance teams need. Reason codes classify the halt (volatility, news pending, regulatory, LULD, and others) so you can route alerts by severity. For LULD-related pauses, the pause_threshold_price field tells you the band that triggered the event. Treat halt messages as authoritative for whether a symbol is currently tradeable; do not rely on stale quote snapshots alone.
Wire alerts on names where halts have historically preceded large moves, or enable filing and news alerts alongside halt monitoring so you can connect a pause to its catalyst. A well-tuned alert fires when a holding halts and stays quiet on the rest of your universe.
Build the halt dashboard
Maintain a table of currently halted symbols sorted by halt time and reason. Color rows by halt type (news pending in one tone, volatility in another) and show pause_threshold_price for LULD events so traders know the band context. Cross-reference tickers on company pages like Microsoft when a halt follows an 8-K or press release; open the calendar to see if earnings or a corporate action explains activity that otherwise looks idiosyncratic.
When a halt lifts, switch attention to the live OHLCV stream to capture the reopening bar. The gap between the last pre-halt quote and the first post-resumption trade is useful feedback for execution quality and risk reviews. Some desks log halt frequency by symbol to tune position sizing on volatile small caps.
Consider pairing halt monitoring with the F channel for SEC filing metadata and the N channel for live news on the same symbols. A news pending halt that coincides with a fresh 8-K filing on the F stream is a different urgency than a routine volatility pause on a quiet afternoon.
After the halt
When trading resumes, archive the halt record with timestamp, reason, and threshold price for compliance and post-mortems. The MCP server can help summarize recent filing activity for a halted symbol using search_filings or list_filings while you wait for the reopening print.
Full message reference lives in the WebSocket docs. Compare plan limits on pricing before you scale subscriptions to an entire sector watch. Halt monitoring rewards disciplined state management: know which symbols are paused before your algos or traders send the next order.
Trading halts over the H channel
Pre-market volatility is not only about where a stock might open) it is also about whether it can trade at all. Vantafin's H channel on wss://socket.vantafin.com/v1/stocks pushes NASDAQ trading halt and resumption events the moment status changes. Subscribe to H.AAPL for one ticker or H.* for every halt market-wide; messages include halt reason codes, human-readable explanations, and expected resumption times in US/Eastern.
Connect with your API key per the WebSocket overview, then load symbols from today's watchlist before the session. A halt board that ranks active halts by time stopped and reason code gives risk teams a cleaner pre-open read than polling news sites and hoping coverage is complete. When a name resumes, the next H message clears the row so your UI does not require a manual refresh.
Cross-reference halt traffic with the calendar for earnings, splits, and dividend dates on the same symbols. Halts ahead of a scheduled print carry different weight than halts on a quiet Tuesday, and conflating the two produces false urgency in morning reviews. Link each halted ticker to its company page so operators see context without leaving the board.
Pairing halts with live quotes and news
Once a stock resumes, switch attention to LS or LM on the same socket for per-second or per-minute quotes that show how the reopen print behaves. Many halted names gap on resumption; watching LS confirms whether volume follows through or fades within the first few minutes. Throttle UI updates if you run both H and LS on a busy day. Halts arrive rarely but quotes arrive continuously.
Subscribe to N.{ticker} when you need headlines that might explain a halt before the official reason code updates. News streams around the clock, unlike quote channels, so overnight articles are already flowing when you connect at 7:00 AM. For filings that often precede halts) late 8-K items, for example (F.{ticker} delivers metadata the moment EDGAR indexes a new submission.
Configure email alerts on halt-adjacent names so you are not glued to a dashboard every morning. Price alerts on resumption levels and filing alerts on 8-K forms complement the H stream: the socket tells you status changed, alerts tell you when to re-read the thesis.
Research and production habits
Persist halt events alongside subsequent quote paths for event studies. Over time you build an internal dataset on which reason codes predicted sustained moves versus quick mean reversion after resumption. Ask the MCP server for recent news and filings on a halted ticker while you wait for the next H message) get_news, list_filings, and search_filings chain cleanly in Cursor without a custom integration.
Treat halts as one input among several, not a standalone trade signal. Regulatory pauses, volatility halts, and news pending states each carry different follow-through profiles. Confirm entitlements on pricing for WebSocket symbol counts before subscribing H.* market-wide in production; sector-scoped watchlists usually suffice for desk workflows.