Hi @sujith - I'm calculating the following way:
net_change = ohlc.open - ohlc.close;
change_percent = (net_change / ohlc.open) * 100
Should not be a problem right? Asking a 2nd opinion.
@sujith It's basically a web app - I'm storing the access token in a localStorage key which is extremely vulnerable.
Another option is storing access token in a cookie which is also vulnerable. Can't make the right decision
@heisenBerger The sandbox simply mocks the Zerodha Kite and Coin REST APIs. It's like interacting with any other REST APIs. So it's independent of any type of language. There are no specific steps for any specific language. Use the same endpoint for…
@sujith @ZI4453 My question is why is the 400 a response? The parameters are perfectly all right I believe. I tried version to be a string too. Do you see any logs on your servers?
@rishiswethan thanks for the help here! I'm able to get the entire flow going. Thanks a lot! The original issue was that I was passing API secret instead of access_token in the Holdings API. You can close this thread and thanks a lot for being so he…
@rishiswethan This is getting crazy now! I got the request_token from Login API in the redirect url query param. I'm concatenating api_key, request_token and api_secret at Online hash generator. All the required info is being passed to Token API but…
@rishiswethan I'm not understanding why the documentation https://kite.trade/docs/connect/v3/portfolio/#holdings only talks about API key and secret only. The request/access token is not mentioned in the API calling flow. Are you sure I really need …
@rishiswethan The APIs are not fully automated? I was assuming that Kite APIs are stateless APIs so only the API key and secret should have done the trick. I'm going through the webinar now to get a better understanding