Subject: Clarification needed on Kite /instruments CSV exchange/segment and option identity validati

santoshzain
Hello Zerodha Team,

I am developing a personal, read-only Kite Connect instrument ingestion system for NIFTY and SENSEX paper-trading research.

I have captured a genuine authenticated `/instruments` CSV and am validating it offline.

I need clarification on three schema questions:

1. Can a noncore exchange identifier legitimately appear alongside an NSE/BSE cash or index segment? Is there an authoritative exchange-to-segment compatibility reference?

2. Does the consolidated instrument CSV contain valid exchange identifiers that are not currently listed in the official Kite SDK exchange constants? How can developers verify such identifiers safely?

3. For NFO/BFO options, should the `name` field always agree with the underlying inferred from `tradingsymbol`? Are incomplete CE/PE strike pairs expected in the instrument master?

My application currently rejects ambiguous records rather than treating them as valid option contracts.

Could you clarify the documented validation rules, and advise whether there is a secure private channel for reviewing a few specific schema examples if necessary?

I am not posting API credentials, instrument tokens, raw CSV records, or private account data.

Thank you.
Sign In or Register to comment.