Too many requests Issue : Its really a shame with Kite API

nselvamca

@sujith , @zerodha ,

Today am getting "Too many requests Issue"
- Each call is a millisecond call to get Instrument LTP
- Though Zerodha charges 2k for API & 2k for Historical Data, but they cant handle the Milliseconds request
- And I felt really bad about their support
- I felt its a waist of money for this kinda support

Also please don't convince me that Zerodha can't handle this kinda request.


Log:

Line 18314: 09:40:53.676 [scheduling-1] INFO okhttp3.OkHttpClient - {"status": "error","message": "Too many requests","error_type": "NetworkException"}
Line 19004: 09:40:57.696 [scheduling-1] INFO okhttp3.OkHttpClient - {"status": "error","message": "Too many requests","error_type": "NetworkException"}
Line 19698: 09:41:01.711 [scheduling-1] INFO okhttp3.OkHttpClient - {"status": "error","message": "Too many requests","error_type": "NetworkException"}
Line 20407: 09:41:05.671 [scheduling-1] INFO okhttp3.OkHttpClient - {"status": "error","message": "Too many requests","error_type": "NetworkException"}
Line 21069: 09:41:09.692 [scheduling-1] INFO okhttp3.OkHttpClient - {"status": "error","message": "Too many requests","error_type": "NetworkException"}
Line 21769: 09:41:13.673 [scheduling-1] INFO okhttp3.OkHttpClient - {"status": "error","message": "Too many requests","error_type": "NetworkException"}
Line 22437: 09:41:17.649 [scheduling-1] INFO okhttp3.OkHttpClient - {"status": "error","message": "Too many requests","error_type": "NetworkException"}
Line 23138: 09:41:21.619 [scheduling-1] INFO okhttp3.OkHttpClient - {"status": "error","message": "Too many requests","error_type": "NetworkException"}
Line 23813: 09:41:25.510 [scheduling-1] INFO okhttp3.OkHttpClient - {"status": "error","message": "Too many requests","error_type": "NetworkException"}

sujith

@nselvamca,
We suggest using Websockets API for live market data.
All the API rate limits are mentioned in the FAQs.

nselvamca

@sujith the websocket is not updating millisecond and its updating in 1 secs only

sujith

We relay whatever data we get from the exchange. All the members get level 2 data only.
If you want data every millisecond then you will have to get a colocation setup at the exchange wherein ticks are broadcasted via LAN and frequency of ticks will also be more. The colocation setup costs upwards 18 lakh/annum.

You can know more about the ticks and it frequency on this TradingQnA thread.

nselvamca

@sujith the Kite is supporting the API, and a LTP request will take hardly 60 to 70 MS only via API
- In this case why you are suggesting another API/Data?
- The same MS updates are happing in Zerodha web version too but why your API server cant handled it where the service comes with a cost
- Now wondering why this conversation is misleading

sujith

The LTP request gets data from the same Websocket API, no point even if you query 100 times in a second. You will get the same data.

nselvamca

@sujith but the LTP is getting updated by only 1 sec difference which the API LTP is updated as per the Market price, so finally websocket SYNC is delay right?

rakeshr

The same MS updates are happing in Zerodha web version too

No, your conclusion on this is wrong. We just logged the kite web marketwatch ltp update and the kiteconnect websocket stream for an active NSE-EQ contract, both are matching perfectly fine, with the same packet timestamp.
If you see the difference, can you paste here the tick logs from each source with the timestamp difference?

nselvamca

Hi @rakeshr
Am taking about delays in Websocket where the tick data is happening per second and not in Milli Seconds
- So here am taking about delay and not about Price difference
- Hope I make it clear