Exchange Stream API Release - Connection Throttling - 26th February
13-02-2020, 11:46 AM
To improve performance and stability we are introducing Exchange Stream API connection throttling as part of a release on the 26th February
The changes in this release are to protect our systems against excessive or improper use and will have no impact on customers who are managing their Stream API connections correctly.
Please Note: If you would have been impacted by this change based on your Stream API usage over the last 3 weeks we’ll inform you directly in a separate communication so you can make the required changes before the release.
Following this release any excessive connection requests will return the below error during authentication:
Failure code returned when a client makes too many requests within a short time period
The MAX_CONNECTION_LIMIT_EXCEEDED will continue to be returned during normal usage (i.e. if you attempt to create more connections than the available limit before closing existing connections).
New Status / StatusMessage Field
To help with connection management, in this release we will also add a new field, connectionsAvailable, to the StatusMessage returned from authentication requests. This field tells you how many new streaming connections you are able to open at this moment in time. If you adhere to this you should avoid TOO_MANY_REQUESTS and MAX_CONNECTION_LIMIT_EXCEEDED errors.
The new throttling behavior and connectionsAvailable field will be in the Stream API integration environment (stream-api-integration.betfair.com) from Monday 17th February.
Betfair Developer Program
Last edited by BetfairDeveloperProgram; 25-02-2020, 03:20 PM. Reason: Release date updated to 26th February
Admin я спрашиваю, сколько 1-2-3-4? Stream API connections?