There are many duplicate SEM_TRADING_SYMBOL values in https://images.dhan.co/api-data/api-scrip-master.csv; are these valid ones? For example:
“199036 EQUITY ICICINFINAV ICICI Pru Nifty 100 ETF”
“199122 EQUITY ICICINFINAV INAV ICICI PRU NIFTY INFRA ETF”
When there are duplicate entries, how do we decide the correct one? Do you have plans to correct these?
Welcome to Dhan Community! There are no duplicate entries as such in the Security ID Master. Over here, in the example shared by you, it is clear that both the scrips are completely different. One of the is ‘ICICI Pru Nifty 100 ETF’ whereas the other one is ‘INAV ICICI PRU NIFTY INFRA ETF’ which are two different scrips.
Hope this answers your question!
If both are different scrips, why are the trading symbols same for both?
We checked for this instance and it turns out both the scrips are suspended for trading on Exchange. This might be one of the reason for having duplicate trading symbols. There are hardly few such cases where trading symbols are duplicate.
Moreover, all Dhan APIs work on ‘Security ID’ to avoid such instances of duplicacy or consistency in Trading Symbols across platforms. Also, there are additional columns available for you to verify the other scrip details.
CHOLAFIN are still duplicates. I am looking at all equity types, on NSE exchange.
SEM_EXM_EXCH_ID SEM_SEGMENT SEM_SMST_SECURITY_ID SEM_INSTRUMENT_NAME SEM_EXPIRY_CODE SEM_TRADING_SYMBOL SEM_LOT_UNITS SEM_CUSTOM_SYMBOL SEM_EXPIRY_DATE SEM_STRIKE_PRICE SEM_OPTION_TYPE SEM_TICK_SIZE SEM_EXPIRY_FLAG
226584 NSE E 20217 EQUITY 0 ATUL 1.0 ATUL NaN NaN NaN 5.0 NaN
227437 NSE E 263 EQUITY 0 ATUL 1.0 ATUL NaN NaN NaN 5.0 NaN
226260 NSE E 19257 EQUITY 0 CHOLAFIN 1.0 CHOLAMANDALAM IN & FIN CO NaN NaN NaN 5.0 NaN
228643 NSE E 685 EQUITY 0 CHOLAFIN 1.0 Cholamandalam Investment NaN NaN NaN 5.0 NaN
Welcome to Dhan Community!
This should not happen, will check the filtering here. Thank you for highlighting this.
We are introducing two other columns which will help you filter based on Instrument Type. This will solve the issue that you earlier highlighted.
Meanwhile @tradata’s highlighted issue is different, which we are looking into.
@Hardik Any ETA for the issue I raised. The last ETA was 1 week in Sep
Will release this week itself, should be visible from next week. I will confirm you about the same once it is live.