Errors from GET GTT orders API

The GET v3/order/gtt endpoint is erroring since morning. The same client code has been working for months now. The error can be seen with the following shell script:

curl --location 'https://api.upstox.com/v3/order/gtt' \
--header 'Content-Type: application/json' \
--header 'accept: application/json' \
--header 'Authorization: Bearer {your_access_token}'

The error is:

{"status":"error","errors":[{"errorCode":"UDAPI100011","message":"Invalid Instrument key","propertyPath":"instrument_token","invalidValue":"NSE_EQ|INF174K01Z71","error_code":"UDAPI100011","property_path":"instrument_token","invalid_value":"NSE_EQ|INF174K01Z71"}]}

Hi @HARSHAD_RA_1109131, It appears that the ISIN for Kotak Nifty 50 Value 20 has changed today from INF174K01Z71 to INF174KA1ZE1. As a result, your existing GTT order with the older ISIN is no longer valid. Could you please try deleting the existing GTT order and place a new one using the updated ISIN?

Meanwhile, we’ll forward this information to the relevant team. Thanks for bringing this to our attention.

Instrument dump has not yet updated the ISIN for the same. Not good.

const a = require('./NSE.json')

console.log(a.filter((i) => i.isin === 'INF174KA1ZE1'))

This results empty!

Thanks @Anand_Sajankar for the quick response. FYI, those orders were automatically cancelled today morning by Upstox. The GTT API errors probably started around the same time.

@Anand_Sajankar Surprisingly, “Complete“ instruments file is working but “NSE“ file doesnot.

const a = require('./complete.json')
console.log(a.filter((i) => i.isin === 'INF174KA1ZE1'))

This is working fine.

@DSingh There was a caching issue today with the NSE JSON file. We’ve refreshed and updated it, and the files are now consistent. Thanks!

@HARSHAD_RA_1109131 Let us know if you’re still facing the same error.

Yes still facing same error.

@HARSHAD_RA_1109131 Working fine. I have checked with access_token generated from Upstox api apps. Upstox Accounts

@Anand_Sajankar It seems Upstox server error where it is sending error message because of “old ISIN” based orders which it fails to recognize now. May be a better error message would help algo users and would reduce confusion.

@Anand_Sajankar Still facing the error in GET GTT orders API. I hope it gets fixed before next trading session atleast.