Navigation

    SmartAPI Forum
    • Register
    • Login
    • Search
    • Categories
    • Popular
    • Groups
    • FAQs
    • API Docs
    1. Home
    2. Rathnadhar K V
    R
    • Profile
    • Following
    • Followers
    • Topics
    • Posts
    • Best
    • Groups

    Rathnadhar K V

    @Rathnadhar K V

    SmartAPI Group

    0
    Reputation
    3
    Posts
    1
    Profile views
    0
    Followers
    0
    Following
    Joined Last Online

    Rathnadhar K V Follow
    SmartAPI Group

    Best posts made by Rathnadhar K V

    This user hasn't posted anything yet.

    Latest posts made by Rathnadhar K V

    • Option Greeks: The strikePrice must be integer, but returned as float (string).

      Namaskara,

      The response value of Option Greeks, is listed as follows in the documentation:

      Sample Response:

      {
      "status": true,
      "message": "SUCCESS",
      "errorcode": "",
      "data": [
      {
      "name": "TCS",
      "expiry": "25JAN2024",
      "strikePrice": "3900.000000",
      "optionType": "CE",
      "delta": "0.492400",
      "gamma": "0.002800",
      "theta": "-4.091800",
      "vega": "2.296700",
      "impliedVolatility": "16.330000",
      "tradeVolume": "24048.00"
      },
      {
      "name": "TCS",
      "expiry": "25JAN2024",
      "strikePrice": "4000.000000",
      "optionType": "CE",
      "delta": "0.239000",
      "gamma": "0.002200",
      "theta": "-3.033500",
      "vega": "1.785400",
      "impliedVolatility": "22.190000",
      "tradeVolume": "12976.00"
      }

      Here the option strikePrice is returned as 3900.000000

      this is wrong.

      The above is string representation of a float value.

      Option Strike price is never float. It must a integer ... say as 3900 (no decimal point and digits after that).

      If the conversion from the float string representation to integer is executed, then it results in rounding errors (the value will be nearest approximation) which cannot be equated with Integer (non decimal number).

      In this case to convert the string to integer, we must first strip all digits after decimal (including the decimal point) and then convert to integer.

      It is ideal and highly recommended that this value is returned as 3900 (with no decimal point) rather than 3900.000000.

      Regards
      Rathnadhar K V
      (Writing the C++ api for Angel One connector)...

      posted in Bugs
      R
      Rathnadhar K V
    • Modify Order, what are the fields for ROBO orders?

      Namaskara,

      I am currently implementing the API in C++,

      I find that in : order -> Modify Order

      The Modify Order Request parameter list are as follows:

      {
      "variety":"NORMAL",
      "orderid":"201020000000080",
      "ordertype":"LIMIT",
      "producttype":"INTRADAY",
      "duration":"DAY",
      "price":"194.00",
      "quantity":"1",
      "tradingsymbol":"SBIN-EQ",
      "symboltoken":"3045",
      "exchange":"NSE"

      ==============

      How to do I?

      For ROBO (Bracket orders):

      1. Modify Target (square off) price?
      2. Modify Stoploss price?
      3. Modify Stoploss Trigger price?
      4. Modify trailing Sl steps?

      This has not been documented,

      Kindly let me know.

      Regards
      Rathnadhar K V

      posted in General Discussion
      R
      Rathnadhar K V
    • Modify Order: Need provision to modify squareoff, stoploss and trailingStopLoss

      Namaskara,

      Currently, for Modify Orders Request has following fields:

      {
      "variety":"NORMAL",
      "orderid":"201020000000080",
      "ordertype":"LIMIT",
      "producttype":"INTRADAY",
      "duration":"DAY",
      "price":"194.00",
      "quantity":"1",
      "tradingsymbol":"SBIN-EQ",
      "symboltoken":"3045",
      "exchange":"NSE"
      }

      however for the ROBO orders three other fields are present:

      1. SquareOff (target)
      2. Stoploss
      3. Trailing Stoploss.

      I am not sure if these fields can be modified independently... as there is no documentation as such.

      If these fields are indeed modifiable using API for ROBO orders,
      then kindly update the documentation,

      If these fields have not been implemented then kindly implement
      then kindly implement this facility.

      Regards,
      Rathnadhar K V

      Smart API : Version 1.

      posted in General Discussion
      R
      Rathnadhar K V