Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Table of Content Zone

Development & Testing

You should use the Delayed Application Key for any initial development and functional testing.  Historical data is made available via for strategy modelling & analysis.

Only apply for Live Application Key access once you are ready to start transacting on the Exchange using your Live Application Key.

Please see the Personal Betting Access Overview for more details regarding the difference between  Delayed an Live Application Keys.

Login & Session Management

Use Login to create a new session and Keep Alive to extend the session beyond the session expiry time. A single session can and should be used across multiple API calls/threads simultaneously. 

Please be aware that: 

  • Logins sessions last up to 12 hours by default and you can use Keep Alive to extend the session beyond the stated session expiry time.  
  • A single session can be used across multiple API calls/threads simultaneously.  Please note:  you don't need to make a new login request for every API call.
  • You should ensure that you handle the INVALID_SESSION_TOKEN error within your code by creating a new session token via the API login method.
  • If login limits are exceeded, you'll be automatically prevented from making further login requests for a period of 20 minutes.  During this time all existing sessions will remain valid.

General Tips

  • Make the minimal number of transactions/changes possible when transacting.
  • Observe the Market Data Limits when making requests to listMarketCatalogue, listRunnerBook, listMarketBook and listMarketProfitandLoss
  • Always prefer leaving an order in place rather than canceling/re-placing it – stay at the front of the queue to be matched!
  • Use the Stream API instead of polling wherever possible, particularly if you are running a high-frequency trading application.
  • Log as much as possible to aid queries/problem investigation (especially connectionid when using the Stream API)
  • Make use of betting enhancements

API Status 

Use the API status page to check the health of the API. 

The API Status:

  • Measures response latency and error rate against a number of operations every second
  • Automatically toggles the status page if certain thresholds are breached

Please check the API status before contacting Developer Support regarding API problems.

Expect: 100 - Continue Header


Sending this header will result in the error: "The remote server returned an error: (417) Expectation Failed."

You should be aware that if using the .Net Framework you will need to set the relevant property in the ServicePointManager which then prevents the "Expect" header from being added:

System.Net.ServicePointManager.Expect100Continue = false;

Enabling HTTP Compression

HTTP compression is a capability built into both web servers and web clients to reduce the number of bytes transmitted in an HTTP response. This makes better use of available bandwidth and increases performance while reducing download time. When enabled, HTTP protocol data is compressed before it is sent from the server. Clients capable of receiving compressed HTTP data announce that they support compression in the HTTP header. Almost all modern web browsers support HTTP Compression by default.

The Betfair API uses HTTP to handle communication between API clients and servers. Therefore, the JSON messages can be compressed using the same HTTP compression used by web browsers. Custom API applications may need some modification before they can take advantage of this feature. Specifically, they need to send an additional HTTP header to indicate they support receipt of compressed responses from the API. In addition, some environments require you to explicitly decompress the response.

We would therefore recommend that all Betfair API request are sent with the ‘Accept-Encoding: gzip, deflate’ request header.

HTTP Persistent Connection

We recommend that Connection: keep-alive header is set for all requests to guarantee a persistent connection and therefore reducing latency. Please note: Idle keep-alive connection to the API endpoints are closed every 3 minutes.

Although maintaining long-lived connections is actively encouraged (for the Stream API for example), for a number of reasons within & beyond our direct control, we cannot guarantee that keep-alive connection won't be forcibly closed.  We, therefore, advise all customers to ensure that they have reconnection logic in place to handle any connection termination scenarios.

Other Performance Tips

Additional advice regarding optimizing HTTPClient performance can be found here