For bots owners.

[napshnap]

Bots owners be warned, without any notification Betfair changed their IP address used for sessiontoken receiving and sessionkeepalive, it was static 84.20.200.150 for years, and now it randomly jumps over several different IPs.
So if you have strict firewall rules for identification page access, then you are in trouble now.
Very unfriendly and unnecessary move from Betfair .
Hope it's temporary and won't get worse.

[jimibt]

yup -this b@ggers up a little routine that i have in .net to transfer funds from the exchange games=>main wallet and vice a versa. will investigate and fix this. thanks for the heads up

[ShaunWhite]

Bots owners be warned, without any notification Betfair changed their IP address used for sessiontoken receiving and sessionkeepalive,

LinusP posted about this in November
viewtopic.php?f=55&t=17743&p=173684&hil ... nt#p173684

https://forum.developer.betfair.com/for ... n-endpoint

BUT although I made the code change weeks ago, I had problems yesterday as you'll see from the BF Down thread. I thought the old endpoint was retired on 22 Jan so figured I'd breezed through it untouched. I still can't connect today.

Can I just check with you guys which url's you're using ...

API_ENDPOINT = "https://api.betfair.com/exchange/betting/json-rpc/v1";
LOGIN = "https://identitysso-cert.betfair.com/api/certlogin";
KEEP_ALIVE = "https://identitysso.betfair.com/api/keepAlive;

Napshnap : did you have to change your KeepAlive ? I've only changed my Login endpoint ?

[jimibt]

Bots owners be warned, without any notification Betfair changed their IP address used for sessiontoken receiving and sessionkeepalive,

LinusP posted about this in November
viewtopic.php?f=55&t=17743&p=173684&hil ... nt#p173684

https://forum.developer.betfair.com/for ... n-endpoint

BUT although I made the code change weeks ago, I had problems yesterday as you'll see from the BF Down thread. I thought the old endpoint was retired on 22 Jan so figured I'd breezed through it untouched. I still can't connect today.

Can I just check with you guys which url's you're using ...

API_ENDPOINT = "https://api.betfair.com/exchange/betting/json-rpc/v1";
LOGIN = "https://identitysso-cert.betfair.com/api/certlogin";
KEEP_ALIVE = "https://identitysso.betfair.com/api/keepAlive;

Napshnap : did you have to change your KeepAlive ? I've only changed my Login endpoint ?

Shaun - i can login fine, i can get the balances on the MAIN and XG wallets fine. My problem is that I can't UPDATE/TRANSFER between the wallets anymore. This is a bespoke piece of HttpWebRequest coding using the https://myaccount.betfair.com sub domain, so is probably a different issue. just seems strange that its timing is tied to other changes.

[ShaunWhite]

Shaun - i can login fine, i can get the balances on the MAIN and XG wallets fine. My problem is that I can't UPDATE/TRANSFER between the wallets anymore.

I can login & my listMarketCatalog works fine, but I can't connect to the price stream. I know others who made the change and are up and running ok.
So have we got 3 different issues here? Yours, mine and napshnap's ?

[jimibt]

Shaun - i can login fine, i can get the balances on the MAIN and XG wallets fine. My problem is that I can't UPDATE/TRANSFER between the wallets anymore.

I can login & my listMarketCatalog works fine, but I can't connect to the price stream. I know others who made the change and are up and running ok.
So have we got 3 different issues here? Yours, mine and napshnap's ?

mine is NOT related to the API per-se as i'm doing some HTTP hacks to get this wallet stuff to function. however, it could be related and is not an API issue, rather an infrastructure/config issue.

[ShaunWhite]

Mine seems to be fixed. Dunno if it helps you but I'd missed a reference to it in one of my configs. I must have checked it dozen times but once your brain has gone into 'I've done this' mode you look at these things but stop seeing it. 'Fresh eyes' are the only thing I miss about not working in a team.

Hopefully yours will be something simple like that.

All goes to show the old url wasn't retired on the 22nd. By my reckoning it was 10:52am on the 28th.