☰
›

Node.JS client returns instrument_token for AMO order

enliyo
enliyo in API clients
Node.JS client is returning instrument_token as 1 for orders placed as AMO from getOrders() method. I placed AMO order through Android Kite this morning around 8:50 AM.

Please look into this. I wish to modify AMO orders placed using my app but instrument_token is set as 1 so I will have to again search through cached instruments to find out the correct instrument_token, which is inconvenient and should be working from API side itself.

Thanks!
Tagged:
  • sujith
    sujith
    We will ask OMS team to look into this.
  • enliyo
    enliyo
    This is still a problem. Did you get a chance to look into this?
  • sujith
    sujith
    We are following up with the OMS team. They are looking into this.

    PS: We use tradingsymbol and exchange as the key to find the instrument.
  • enliyo
    enliyo
    Sure I can do that search. But, my humble question is if other API responses return the correct instrument_token I expect orders API to return the correct token as well. The developer need not fiddle with these patches.
  • sujith
    sujith
    Since it happening from OMS vendors end, it might take a while to get it fixed. We are following up with them.
Sign In or Register to comment.