GetInstruments doesn't do authentication. You can ignore first API call working.
Maybe don't do Base64 encoding while fetching historical data.
PS: Do you have add-on historical data subscription?
@hrp,
I am afraid that is not possible and there is no cache data like that. You can generate candles at your end using the live market data. You may check out this thread to know more.
Kite Connect API doesn't retry placing orders. It could be the okhttp library doing the retry. I would suggest sending GUID for each order to avoid this.
You can check out the login flow documentation here.
You may also check out this thread to know more about the request token and access token handling.
You can refer to the example here.
PS: Please don't post app or client specific tokens on public threads. You may private message, if you have to share any of the tokens.
It is not a re-use of token issue. It is how the Kite Ticker works. Kite Ticker sends a last stored cached tick first time when user subscribes for a token. Post that a tick is sent only when there is a change in any of the values.
We handle the exchange token reuse and you get the OI of the current instrument under that instrument token. If they want historical for expired instruments then you may use continuous mode.
Order update is not pushed when order is placed on Kite app but it will be pushed only when there is a partial fill or the trigger is hit or order is modified.
This is the formula and everything is available in the API. Latest LTP is available on Quote API or Websocket API.
pnl = (sellValue - buyValue) + (netQuantity * lastPrice * multiplier);
@ashishbajaj,
You won't receive postbacks if order is not originated from your app. You will have to create a websocket and listen to order updates on that. You may use that order update as an event to fetch orderbook and check order status or do an…
@MayurVirkar,
You can read the support article that is pointed out there and create a support ticket if you want more explanation. Kite Connect forum is dedicated only for technical queries only.
@sathyatej,
Kite Connect is purely an execution platform. We don't provide one to one support or coding support.
We are all developers like you, we work on our projects and take some time out to help community members. Kite Ticker doesn't have any i…
An order id and tag will never change once created in the system. Only new trade entries will be there for that order. For partial fills, you can check filled_quantity field.
Kite Ticker doesn't have any issue. It is used by thousands of production apps. You need to check code at your end. Add logs and also make sure to enable Kite Connect debug logs as well.
Every instance of KiteException has a message attribute like this.
Can you print the same in the catch block and paste the message here? If you are placing order then it could be the exception from the http API as well.
You shouldn't block the thread that is retrieving data. It should be always available to receive ticks. If you are doing some operation inside onTick, then you should move everything to a different thread.
We will discus internally and take the decision.
This merge is a huge change for existing users, we will do it with next release if we are going to merge your changes.
Kite Connect offers much more with just Rs 2000.
> Kite Connect APIs are simple, robust and reliable.
> The Rs 2000 for Kite Connect charges include GST.
> Kite Connect API's historical dataset is bigger than any other offering.
> Kite C…
Instruments segments are obsolete, it was used in margins data API. You can use the new margins calculation API.
Kite Connect API supports CDS and BCD exchange for currency instruments. You can check all the values in the instruments master file.
CN…
It is mandatory by the regulators that a user has to login manually at least once a day. We don't recommend automating login. We don't recommend sharing credentials with any third party.
It was a legacy decision. Back in v1 of Kite Connect APIs, buy value and sell value wasn't there. It was calculated in the front end. Now that API is sending those values, it makes sense to change it to quantity.
We will change it in next release.
