[]
I agree with @sodha_rakesh.
If we as a community of independent algo traders won't push back on this then the incompetent authorities of the country will pass yet another incompetent law.
I, as a software engineer, will try to include few alter…
@sujith, Now that TOTP is forced on API users, any protection they received against illiquid-scrips/scrips in ASM/GSM is gone.
Users who had their own implementation to maintain this list can no longer do so.
So does Zerodha have any plans to provi…
@Matti
Question: How will Zerodha handle the trades that are currently protected via TOTP?
The use of TOTP to safeguard against suspicious trades was a helpful feature. With this change there is no protection against such trades.
__________________…
@sujith, How can I reach out to the compliance team?
I don't intend to go public for the next ~1 year, but would like to get my platform ready and test with 5-10 users. What is the recommended design for multi-user access?
I had the implementation something like:
if(order.tag == null)
printErr("TAG MISSING FROM KITE_ORDER!!"+"\nKO_ID:"+order.orderId);
else
int id = Integer.parseInt(order.tag);
This started breaking and I added …
Previously:
- Place an order via kite desktop (not API), OnOrderUpdate receives the update & tag was `null`
Now:
- Place an order via kite desktop (not API), OnOrderUpdate receives the update & tag = `"tfc"`
Never-mind, found the issue.
I was hard-coding `orderParams.exchange = Constants.EXCHANGE_NSE;` while placing the order, whereas using kite's `instrument_id` at other places.
Thanks anyway.
That's all the message returned by KiteClient.
e.message =
"Unknown `tradingsymbol`."
e.printStackTrace() =
com.zerodhatech.kiteconnect.kitehttp.exceptions.InputException
at com.zerodhatech.kiteconnect.kitehttp.KiteResponseHandler.dealWithExcepti…
Thanks for sharing this.
I have been using ex.toString() & ex.printStackTrace() to get the error details. It displays only InputException for each of these error category.
Let me try ex.getMessage() and see if it has the exact message.
` 429 Too Many Requests ` seems to be resolved for me with the above fix but the other issue of "Websocket Not Receiving Updates After a while" still persists.
This is also something which didn't happen too often till this week.
I take back my words. Issue was indeed with my code.
while(true)
{
if(!dataCollectorActive && isTradingHours())
initScripFilter();
else if(dataCollectorActive) //instead of else if(dataCollectorActive &&…
As I said earlier: There is nothing wrong with the code I am using.
Same code was working fine till last week & is behaving differently with different API keys now.
It is possible that the ones who don't face the issue anymore are the fortuna…
@sujith : I have been doing that since Yesterday. Results are the same:
com.neovisionaries.ws.client.OpeningHandshakeException: The status code of the opening handshake response is not '101 Switching Protocols'. The status line is: HTTP/1.1 429 Too …
Amazing how you make breaking changes without informing the customers. I thought you were saying max limit is 4k.
Irrespective, the issue still persists with 8 instruments across 3 sockets.
Food for thought: It would be so much better if custom…
@sujith: I am following :
"You can subscribe up to 3000 instruments/shares in a single WebSocket connection, and for one user you can have 3 WebSocket connection, so you can stream maximum of 9000 shares for one user. because all WebSockets will be…
Still facing the issue:
Error: The status code of the opening handshake response is not '101 Switching Protocols'. The status line is: HTTP/1.1 429 Too Many Requests
com.neovisionaries.ws.client.OpeningHandshakeException: The status code of the open…
Error:
```
com.neovisionaries.ws.client.OpeningHandshakeException: The status code of the opening handshake response is not '101 Switching Protocols'. The status line is: HTTP/1.1 502 Bad Gateway
at com.neovisionaries.ws.client.HandshakeReader.vali…
Just wondering: Is one time submission of PoA the only way to have a seamless experience for API users?
Also: I cannot see the 'Authorisation' button on my holdings page. Is it the behaviour for all PoA submitted users?
