This release includes the following updates:

New Stream API ‘status’ field - We are adding a new field ‘status’ on every ChangeMessage both for the Order and Market stream, which will give an indication on the health of the stream data provided by the service. This is feature will be used in addition to the heartbeat mechanism which only gives an indication that the service is up but doesn't provide an indication of the latency of the data provided. By default, when the stream data is up to date the value is set to null and will be set to 503 when the stream data is unreliable (i.e. not all bets and markets changes will be reflected on the stream) due to an increase in push latency. Clients shouldn't disconnect if status 503 is returned; when the stream recovers updates will be sent containing the latest data. The status is sent per each subscription on heartbeats and change messages.

Example of message containing the status field:

{"op":"ocm","id":3,"clk":"AAAAAAAA","status":503," pt":1498137379766,"ct":"HEARTBEAT"}
{"op":"mcm","id":2,"clk":"AAAAAAAA","status":503," pt":1498137381621,"ct":"HEARTBEAT"}

Update conflation delay value from 2 minutes to 3 minutes.