Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Circuit Limits in Websocket Calls #179

Open
CasCard opened this issue May 21, 2023 · 2 comments
Open

Circuit Limits in Websocket Calls #179

CasCard opened this issue May 21, 2023 · 2 comments

Comments

@CasCard
Copy link

CasCard commented May 21, 2023

It seems the circuit limit calls are not implemented in the Websocket of Kite Ticker, they seem to be available in the Kite Connection function of kite quote. Still, I would like to know if this feature is also available for the WebSocket Ticker.

@ranjanrak
Copy link
Member

The circuit limit fields are not included in the binary packets received from the exchange, hence they are not available in the websocket streaming response. For detailed information about the packet structure, please refer to the documentation.

@rahulswaminathan
Copy link

Hello Rakesh,

Similar to instrument_token in the quote packet, can the circuit values be injected into the quote packet before streaming? This would bring parity with the /quote API and if an instrument breaks through its circuit levels, thereby changing the circuit levels, the quote packet would work like a notification of this change.

Note: I'm assuming the instrument_token values are specific to Kite and not the exchange. Please correct me if I'm wrong.

Regards
RS

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants