Venue clock and sessions

GET /api/v1/clock is the public snapshot for timestamp quality and the current trading-day boundary. Clients should use it instead of treating their own host clock as venue state.

Clock health

The response includes quality, accepting_timestamps, enforcement, venue_time, sequence, any current tolerance breaches, and an optional source reading. Quality is one of DISCIPLINED, OUT_OF_TOLERANCE, UNSYNCHRONISED, UNREACHABLE, or UNKNOWN.

When timestamp enforcement is active and accepting_timestamps is false, a new order or accepted RFQ that could print a trade is refused. Market-data reads remain available.

Trading session

The session object reports:

• the session date;
• open and close timestamps;
• seconds until close;
• the fixed UTC offset; and
• the configured boundary time.

The object can be null when the calendar cannot place the current venue time.

Order behavior

Resting DAY orders expire at the session close. GTC, IOC, and FOK retain their normal time-in-force behavior. Cancellation uses the venue time but remains available to an eligible trading membership when controls block new exposure, so a desk can remove resting risk.

Realtime clients can subscribe to the venue channel for CLOCK_HEALTH changes and refresh this route for the complete snapshot.