Trading Status

As a 24 x 7 x 365 exchange, the Bullish platform should ordinarily always be available.

From time to time there are, however, periods of platform-wide downtime for scheduled maintenance or updates. These will be communicated to participants in advance (contact Market Operations to subscribe for notifications).

Additionally, there may be reasons for individual instruments to be temporarily removed from trading.

The platform will communicate both of these situations through the TradingSessionStatus [h] message which is broadcast from Bullish.

Exchange-Wide Halt

The exchange may enter a platform-wide trading halt in exceptional circumstances. When halted:

• All order entry, amendment, cancellation, and mass-cancellation requests are rejected with OrdRejReason (103), CxlRejReason (102), or MassCancelRejectReason (532) = 2124 (EXCHANGE_HALTED)
• TradingSessionStatus [h] messages will show TradSesStatus (340) = 1 (Halted) for all instruments
• The Get Trading Status REST endpoint returns "halted"

Trading will resume via an exchange-wide unhalt, at which point TradSesStatus (340) = 2 (Open) is broadcast for all instruments.

Table 19: TradingSessionStatus [h] message

Tag	Field Name	Req'd	Type	Comments
< Standard Header >				35 = h
336	TradingSessionID	Y	String	The trading session this message relates to. 1 = Day.
325	UnsolicitedIndicator	Y	Boolean	These messages are always unsolicited Y = Unsolicited
340	TradSesStatus	Y	int	Status of the platform or instrument (where indicated) 1 = Halted 2 = Open
1368	TradSesEvent	Y	int	Identifies the event causing the state change 0 = Trading resumes 3 = Change of Trading Status
58	Text	N	String	Further detail on the reason for the status change
55	Symbol	N	String	If present, then the change in session status shall relate to this one specific instrument. If omitted, the message should be interpreted as a platform-wide status change.
< Standard Trailer >