rhnvrm

About

Username
rhnvrm
Joined
Visits
13
Last Active
Roles
Member

Comments

  • Based on feedback, we have made a new beta1 release: https://github.com/zerodha/gokiteconnect/releases/tag/v4.0.0-beta1 Feel free to report issues or feedback on the issues page of the github repository.
  • This is fixed. Thanks for reporting
    in Typo Comment by rhnvrm March 2021
  • Hey We support go modules for our package. You can read more about modules here (https://github.com/golang/go/wiki/Modules). For example, for starting a new project, the following should work: ``` cd myproject go mod init github.com/rhnvrm/mytest…
  • Hey Currently we don't support tag in GTT, and we may consider supporting it at a later date. At the moment, even the python api docs do not mention tag. (https://github.com/zerodhatech/pykiteconnect/blob/b00a4b56581a50586d3139c204c72de317913c5c/k…
  • In case of single leg GTTs, `last_price` determines the direction of the trigger. Say you place a GTT for 100, now if you send `last_price` as 125, the trigger will check for Last Traded Price < 100. > Kite can itself check last price easily?…
  • Hey @Gafoor This feature (Buy OCO) is currently available only on Kite web and will be launched on the mobile app soon, therefore "Trigger/Stoploss" in mobile UI does not match.
  • Hey Based on the json format you shared above, my guess is that you have incorrectly given the values as strings: ["175","196"] Also, I'm not sure if you are using the PHP client correctly. Please refer to the example (https://github.com/zerodhate…
  • @tahseen, I guess I understand what you are confused with. It seems to be there in the docs. The condition is separate from the orders, unlike what you have posted above. curl https://api.kite.trade/gtt/triggers \ -H 'X-Kite-Version: 3' \ …
  • @tahseen Hey, The last_price is required for two reasons: 1. Validation of trigger conditions at time of placement 2. The single leg trigger decides the direction for triggering itself using the last_price
  • @nisarg001 Updated the docs. Thanks for reporting.
  • Hey We have just updated the go client package to v3.0.1 with a fix.