What are the free-user request limits? Difference between the 2 application keys?

[fuzzmeister]

Hi all,

newcomer to the API-NG here and I have a few questions I'd like to try get clarified.

1. When I created my application key on the Visualiser, it presents me with two Application Keys, and each has a separate "Version".
The first is "1.0-DELAY" and the second is simply "1.0". Unsurprisingly the -DELAY has a "Yes" under the Delay attribute. What does this mean?

2. Is there any up-to-date list of the request limitations for free API users? I can't seen to find anything; in one place i read 20 requests per second, in another it's 60 per minute. I take it http://bdp.betfair.com/index.php?opt...d=36&Itemid=62 is the most up to date, however this appears to be for the old API? Can anyone clarify?

3. Why do Market ID's always have a "1." before the number. Is this referring to "/v1" of the betfair API?

4. Is KeepAlive currently necessary to keep the session open? I've been idle for far longer than 20 minutes and can all my auth details still work for new requests. Furthermore, when I POST to the keep alive url with the following header with json-rpc:

header = {  'X-Application' : myAppKey ,
            'X-Authentication' : mySsoid ,
            'content-type' : 'application/json',
         }

I receive the error (in python), straight after the request that: SSLError: hostname 'identitysso.betfair.com' doesn't match u'betfair.com'. Is this a consequence of the KeepAlive not being fully implemented as of yet?

Any clarification to the above would be greatly appreciated.

thanks!

[Daggg]

Dunno... my sys file have one heather more (Accept - code example provided in documentation). And curl also.

	$ch = curl_init();
/*
	//---- Could be useful
	curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false);
	curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, 0);  
*/
	curl_setopt($ch, CURLOPT_URL, "https://api.betfair.com/exchange/betting/json-rpc/v1");
	curl_setopt($ch, CURLOPT_POST, 1);
	curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
	curl_setopt($ch, CURLOPT_HTTPHEADER, array (
		'X-Application: '.$dagAppKey,
		'X-Authentication: '.$dagSesTok,
		'Accept: application/json',
		'Content-Type: application/json'
		));
	$postData = '[{ "jsonrpc": "2.0", "method": "SportsAPING/v1.0/' . $operation . '", "params" :' . $params . ', "id": 1}]';

[BetfairDeveloperProgram]

Hi fuzzmeister,

1. When I created my application key on the Visualiser, it presents me with two Application Keys, and each has a separate "Version".
The first is "1.0-DELAY" and the second is simply "1.0". Unsurprisingly the -DELAY has a "Yes" under the Delay attribute. What does this mean?

This indicates that price data requested via the listMarketBook operations will be delayed in the returned response. The delay is the same as a logged out user experiences when viewing the Betfair website e.g. 2 minutes for football, 1 minutes for horse racing markets

2. Is there any up-to-date list of the request limitations for free API users? I can't seen to find anything; in one place i read 20 requests per second, in another it's 60 per minute. I take it http://bdp.betfair.com/index.php?opt...d=36&Itemid=62 is the most up to date, however this appears to be for the old API? Can anyone clarify?

These limits don't apply to API-NG (only API 6.0). For API-NG, the following limits apply to requests https://api.developer.betfair.com/se...Request+Limits

3. Why do Market ID's always have a "1." before the number. Is this referring to "/v1" of the betfair API?

1. = UK Exchange 2. = AUS Exchange

4. Is KeepAlive currently necessary to keep the session open? I've been idle for far longer than 20 minutes and can all my auth details still work for new requests. Furthermore, when I POST to the keep alive url with the following header with json-rpc:

20 minutes is the minimum session expiry time, so for the avoidance of doubt you should keep your session alive within the 20 minutes window if you don't want your session to expire while making API-NG requests.

Thanks

Neil

[fuzzmeister]

Hi guys,

thank you for your replies.

I got the keep alive working; turns out I was missing the 'accept' : 'applications/json' part.

regards