Thanks Kailash, it is working perfectly now. I had a few more queries: 1. Is there a way to know the validity of the current access_token, or would it be better to just create a new one every day. Also I suppose the validity is at least one day long 2. The documentation mentions that the api enforces rate limiting. So, what is the maximum number of api requests a client can send / sec, so that we can ensure not to cross this limit ourselves. 3. Also is the backtesting api live, wanted to try it out too.
Also finally thanks again, this looks like it can be a very good product.
1) The system flushes all tokens in the morning at around 8.30 AM. It's best to refresh the token every day. We're working on making long-standing tokens available, but it'll take some time.
2) Rate limiting should only kick in if a particular client is pegging system resources exclusively. Even many thousand requests per minute should not be a problem.
3) Historical data APIs are almost ready. It should be out in a few days.
Thanks! We're working really hard on the Kite Connect ecosystem and have a lot of exciting things planned.
1. Is there a way to know the validity of the current access_token, or would it be better to just create a new one every day. Also I suppose the validity is at least one day long
2. The documentation mentions that the api enforces rate limiting. So, what is the maximum number of api requests a client can send / sec, so that we can ensure not to cross this limit ourselves.
3. Also is the backtesting api live, wanted to try it out too.
Also finally thanks again, this looks like it can be a very good product.
2) Rate limiting should only kick in if a particular client is pegging system resources exclusively. Even many thousand requests per minute should not be a problem.
3) Historical data APIs are almost ready. It should be out in a few days.
Thanks! We're working really hard on the Kite Connect ecosystem and have a lot of exciting things planned.