Betfair Developers

Developer Program announcements

Post Reply
Betfair Developers Program Betfair Developers Program is offline
Senior Member
Exclamation New Release - Exchange API and Exchange Stream API - Wednesday 19th July

Originally Posted by Betfair Developers Program View Post
Please be aware that we’ll be making the following updates to the Exchange API and Exchange Stream API on Monday 17th July.

These changes are being made to support new Spreads & Total markets types that we’ll be releasing onto the Exchange website in early September this year.

Exchange API - Additional PriceLadderDescription object to the MarketDescription detailing the type of price ladder for the market. Adding an optional KeyLineDescription object to the MarketState containing details of the selections and handicaps forming the KeyLine.

Exchange Stream API - Additional PriceLadderDefinition, KeyLineDefinition objects added to MarketDefinition.

Betfair Developer Program
This release will now take place on Wednesday 19th July onto the Exchange API. The Exchange Stream API release will take place on the 18th July and will be to the integration endpoint ( only.

Betfair Developer Program

Last edited by Betfair Developers Program; 14-07-2017 at 05:48 PM
Betfair Developers Program Betfair Developers Program is offline
Senior Member
Exclamation New Release - Exchange Stream API - Thursday 20th July

Please see below details of up and coming release to the Exchange Stream API Production endpoint. -

This release includes the following updates:

• New Stream API ‘status’ field - We are adding a new field ‘status’ on every message both for 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 latencies 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.

Betfair Developer Program
Post Reply

api-ng, keep alive, login, logout, release

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump