It was always the lower case, we have mentioned it in the documentation. Ideally, you should be using enums like this.
It was working till last week because we were using Nginx till last week and we moved to HAProxy.
In Nginx, it modifies the URL t…
To add more info, the OHLC method returns OHLC of the day and not any intraday interval.
You need to use historical data to fetch historical OHLC data.
For live market strategies, we suggest using websocket data to generate OHLC data at your end.
Y…
@sharun, @gauravmane,
It seems to be working fine. I just tried it.
@ANAADYA,
This forum is dedicated only for Kite Connect related queries, you can contact support here.
The sign up for a broker is not that simple. It involves providing an address proof, income proof, identity proof, POA, adding nominee, IPV and much more. The process is more complex than opening a bank account.
We only provide APIs for Zerodha clie…
Hi @hmayur,
You can check out the API rate limit here.
You can either send the request for multiple instruments with more interval or use Kite Ticker from kiteconnectjs library.
The quote API expects a user to send a valid tradingsymbol and exchange or instrument token.
You can fetch all the details from the instrument dump.
You can check out quote API documentation here.
Kite Ticker provides data in only three modes, modeLTP, modeQUOTE and modeFULL.
It doesn't have a feature to fetch only partial fields. This feature something we have plans of providing in the future if it is feasible at our end.
You can subscribe t…
Kite Connect only publishes the instruments that are tradable for the day. All the equities are by default of EQ category. When exchange finds there seems like speculation or more liquidity than expected on an instrument, they move instruments from …
Are you sure you are using the same client id as mentioned there?
You will see this error only when there is a mismatch in the client id mentioned in the developers console and the Kite Connect login.
It seems to be working fine. Can you run in debug mode paste complete stack trace here and version details about the client library you are using.
Please be more descriptive about the issue with details of your setup, it will help save everyone's ti…
You can expect the response within a second with a good network.
We don't have sandbox yet we are waiting for APIs from our OMS vendor. You can place orders post market hours for testing.
Please send a mail to talk(at)rainmatter.com for payment related queries and make sure you don't post app specific or user specific details on a public thread.
We can only see one debit in your account for the historical data subscription. You seem to have activated historical data API for one of your four apps and not for the one mentioned above.
Please send a mail to talk(at)rainmatter.com for payment r…
Kite Ticker default subscription will set the mode to modeQUOTE and then another request is sent to Kite Ticker to set the mode to modeFULL, while this is happening you might receive ticks in quote mode.
The tick timestamp and last traded timestamp…
If you subscribe for tick in modeFULL then you will receive ticks for every change in the depth also. You need to set the mode to modeLTP for listening to only LTP changes.
Kite Connect only provides complete orderbook. We don't have auxiliary APIs for fetching partial orderbook.
You can check out more details about orderbook APIs here.
@rishiswethan,
As you can see in the above screenshot, you have subscribed to Kite Connect App on 10th December 2018 and it is expiring on 09th Jan 2019.
I don't see any issue here.
@Shabeershah2002,
Please write to talk(at)rainmatter.com for paym…
This is not an error message when the app is expired.
If the app is expired then a user won't be able to see the login page itself forget about generating the access token.
This error message means there was an error while generating the access tok…
Hi @pavandammalli,
These features are part of the back office. As of now, Kite Connect APIs provide only trading platform APIs.
We do have plans of providing this in the future.
We haven't changed the behavior.
I just tried with the following and it seems to be working fine.
{"a":"mode","v":["full",[265,256265,54177543,54177799]]}
