/quote and /quote/ltp returning empty data {} despite valid authentication

sunitster

Hi Team,

I’m facing an issue where market quote APIs return empty data, even though authentication and instruments work correctly.

What works

/user/profile → success

/instruments → success

API key active (₹500 Connect plan)

Token freshly regenerated

SDK + raw HTTP both tested

What fails
GET /quote/ltp?i=NSE:NIFTY
→ HTTP 200
→ {"status":"success","data":{}}


Same empty {} for:

NSE:INFY

NSE:RELIANCE

/quote

/quote/ltp

SDK kite.quote() and kite.ltp()

This happens even during market hours.

Evidence

I have attached:

test_kite_api_basic.py

test_kite_api_raw.py

Full raw HTTP output

This suggests market data entitlement is missing or index symbols are not mapped correctly for my app.

Can someone please check backend entitlement for:

API key: ************

User ID: YL6002

Thanks
Sunit Singh

salim_chisty

We have verified the WebSocket connection on our end and found no issues.
Please review the WebSocket example code and ensure you are using the correct instrument token from the instrument list to check for any errors.
Additionally, you can refer to the Python WebSocket streaming FAQs for further guidance.

sunitster

Hi Team,

I’ve isolated the issue conclusively.

Using raw HTTP calls with valid headers:
- Authentication works
- Instruments API works
- Derivative instruments return LTP correctly

Example (WORKS):
GET /quote/ltp?i=BFO:BANKEX25DECFUT
→ last_price returned

Example (FAILS):
GET /quote/ltp?i=NSE:NIFTY
→ HTTP 200, status=success, but data={}

This confirms:
• Futures / derivatives market data is enabled
• Index spot symbols (NSE:NIFTY / NSE:NIFTY 50) are not enabled or mapped for my app

This is not a formatting, token, or timing issue.

Please enable index spot market data entitlement or correct symbol mapping for:
- User ID: YL6002
- API key: *************

I’m attaching:
- test_kite_api_raw.py
- Raw API output showing futures working and index spot missing

Thanks
Sunit Singh

salim_chisty

The API response data will be empty if the instrument identifier is not passed correctly. Please ensure that the instrument identifier is provided accurately to avoid this issue.

Note: Please avoid sharing API key and client-specific tokens on any public forum.