Change to Session Expiry Time from 8th June

[BetfairDeveloperProgram]

We are reducing the current API session expiry time from 12 hours to 1 hour from the 8th June. Therefore, if your application currently calls Keep Alive with less frequently than every hour you will need to update your code to make this call within an hour to prevent your session from expiring.

Betfair Developer Program

[Grantay.]

Session Expiry Changes

BDP Team,

To save you and others much anxiety, can you please confirm that the changes to the Session expiry time REQUIRE a keepAlive to be made at least every 59 minutes after login?

Searching earlier posts while building this I saw many comments saying keepAlive is not required if you are calling for markets, placing orders etc.

The documentation says "Session times aren't determined or extended based on API activity". So that leads me to think that my programs could time out after 1 hour despite regular activity.

And for any other .net developers, be sure to use the System.Net.HttpWebRequest rather than a WebRequest to allow you to add the .Accept = "application/json" instruction.

A png response means you have omitted that instruction.

[PeteTheBloke]

I am already getting logged out before 12 hours despite constant use, so I can confirm that api activity makes no difference.

What's the point of this?

[dsfibber]

This change has caused quite a problem with my application. I've never had to call keepAlive before in all the years I've been working with the Betfair API.

But anyway, this session timeout is surely not working correctly. The first session timeout I get is when calling listCurrentOrders to track the status of unmatched bets. But whilst I am getting session timeouts with that call, I can call listMarketBook and placeOrders (amongst others) absolutely fine with the same sessionId.
This all means users have been placing bets and not getting the bet updates causing some of them to place more bets because they think the old bets haven't been matched when sometimes they have.

I haven't timed the timeout from login myself but from my guess its not been 1 hour, more like 3 or 4.

Can someone explain whats going on there? Is that expected behaviour?

[doctormike]

Session expiry issues

dsfibber, See thread I initiated indicating a similar issue: http://forum.bdp.betfair.com/showthread.php?t=2887

Mike

[zeal]

We are reducing the current API session expiry time from 12 hours to 1 hour from the 8th June. Therefore, if your application currently calls Keep Alive with less frequently than every hour you will need to update your code to make this call within an hour to prevent your session from expiring.

Betfair Developer Program

I think it was not a good idea. :/ Actually, I just wanted to ask the support about changing the session expiry time to be longer. (24h)
And it is not one hour in the practice. Usually 2-4 hour. Calling keepalive does not matter either. It expires anyway. Then I have to login again (manualy, yepp, I use the interactive login method).
Any idea about this? Or it is not possible in the future to use the session tokens from the cookies?

[zeal]

I have managed the non interactive login. It was not as hard as I imagined before.

[BetfairDeveloperProgram]

This change to a 1 hour session expiry time has been delayed and the session expiry time is currently set at 4 hours.

We'll provide an update for the new delivery date of the 1 hour session expiry time once we have it.

Betfair Developer Program