[URGENT] Constant data miss from the API - Bot development phase

Developer API
1

Hello team,

I’m have been developing my bots since a month and for the same currently running the testing with paper trading.

I’m fetching the data from the upstox api and kept facing issues like, data not being received. you can check my previous post where i was facing the issue with Nifty50 data where for no reason the data was not received and again for no change in code, the data was received post 3:24pm

Today the same happened with every symbol that i’m subscribing to. For all the 40 symbols that i was trying to fetch the data for, none has returned any historical data and not able to get the ltp of the symbols even for the live market.

When called the customer care, I was told, I did not take any orders until date so the api was restricted.

Now the query is, how many minimum order I need to take to keep my api running in my testing phase. Presently i’m running my bots with paper trading and soon to be shifting to live testing based on the bot’s results.

Again, there is no possibility of code errors because:

  • i download the master file on daily basis
  • i keep track of the exact symbols that needs to be sent through the api for getting the subscription details fetched from the master file
  • use the try and exception methods to capture any errors (none captured during these data misses)
  • websocket heartbeat messages to confirm constant connection confirmation

Please let know what is the minimum order quantity that I need to keep flowing for the api to work properly during my testing phase.

If you still insist on rechecking my codes, please do arrange for a call back and I can explain things on the call.

I’m at the verge of completing my testing and now facing these issues halting and delaying my testing phase

2

Hi @Krishnakis_47134930

We apologize for any miscommunication regarding API usage. You can access all APIs without placing a single order.

Please ensure that you have at least one active trading segment enabled. If you are able to generate an access token, it indicates that you can successfully call all the APIs.

Could you please share the instrument keys for which you are facing this issue? This will help us investigate the matter further.

Thanks!

3

@Ketan, I’m actively trading. Even Yesterday No data was being received until 2:30pm

Today, Data reception stopped abruptly. Below the log file that prints the Nifty 50 symbol. stopped after 10:52am, but the ltp was being received. Because my paper trading order was closed based on ltp at 10:53:37 am. Which means, the socket was active and ohlc data of Nifty at 10:53am must have been logged, which did not happen

Why is this happening? If things cannot be explained, then no use of going with Upstox api

2026-03-10 10:28:05,181 [INFO] core.ohlc_builder: NSE_INDEX|Nifty 50 {‘t’: 1773118620, ‘o’: 24160.55, ‘h’: 24163.55, ‘l’: 24154.55, ‘c’: 24156.2, ‘v’: 0}
2026-03-10 10:29:00,145 [INFO] core.ohlc_builder: NSE_INDEX|Nifty 50 {‘t’: 1773118680, ‘o’: 24157.25, ‘h’: 24175.95, ‘l’: 24153.2, ‘c’: 24175.7, ‘v’: 0}
2026-03-10 10:30:00,127 [INFO] core.ohlc_builder: NSE_INDEX|Nifty 50 {‘t’: 1773118740, ‘o’: 24175.15, ‘h’: 24175.15, ‘l’: 24160.4, ‘c’: 24160.6, ‘v’: 0}
2026-03-10 10:31:00,157 [INFO] core.ohlc_builder: NSE_INDEX|Nifty 50 {‘t’: 1773118800, ‘o’: 24160.3, ‘h’: 24168.65, ‘l’: 24159.1, ‘c’: 24166.25, ‘v’: 0}
2026-03-10 10:32:00,123 [INFO] core.ohlc_builder: NSE_INDEX|Nifty 50 {‘t’: 1773118860, ‘o’: 24165.7, ‘h’: 24177.95, ‘l’: 24163.0, ‘c’: 24177.95, ‘v’: 0}
2026-03-10 10:33:00,123 [INFO] core.ohlc_builder: NSE_INDEX|Nifty 50 {‘t’: 1773118920, ‘o’: 24177.45, ‘h’: 24188.2, ‘l’: 24173.4, ‘c’: 24186.55, ‘v’: 0}
2026-03-10 10:34:00,120 [INFO] core.ohlc_builder: NSE_INDEX|Nifty 50 {‘t’: 1773118980, ‘o’: 24185.7, ‘h’: 24204.95, ‘l’: 24181.95, ‘c’: 24204.95, ‘v’: 0}
2026-03-10 10:35:00,127 [INFO] core.ohlc_builder: NSE_INDEX|Nifty 50 {‘t’: 1773119040, ‘o’: 24205.05, ‘h’: 24207.3, ‘l’: 24191.5, ‘c’: 24200.3, ‘v’: 0}
2026-03-10 10:36:00,125 [INFO] core.ohlc_builder: NSE_INDEX|Nifty 50 {‘t’: 1773119100, ‘o’: 24200.3, ‘h’: 24205.05, ‘l’: 24191.7, ‘c’: 24204.25, ‘v’: 0}
2026-03-10 10:37:00,126 [INFO] core.ohlc_builder: NSE_INDEX|Nifty 50 {‘t’: 1773119160, ‘o’: 24204.05, ‘h’: 24209.15, ‘l’: 24200.4, ‘c’: 24200.45, ‘v’: 0}
2026-03-10 10:38:00,127 [INFO] core.ohlc_builder: NSE_INDEX|Nifty 50 {‘t’: 1773119220, ‘o’: 24200.7, ‘h’: 24201.5, ‘l’: 24185.45, ‘c’: 24190.45, ‘v’: 0}
2026-03-10 10:39:00,140 [INFO] core.ohlc_builder: NSE_INDEX|Nifty 50 {‘t’: 1773119280, ‘o’: 24190.2, ‘h’: 24195.25, ‘l’: 24187.8, ‘c’: 24193.0, ‘v’: 0}
2026-03-10 10:40:00,140 [INFO] core.ohlc_builder: NSE_INDEX|Nifty 50 {‘t’: 1773119340, ‘o’: 24192.95, ‘h’: 24195.1, ‘l’: 24189.05, ‘c’: 24193.2, ‘v’: 0}
2026-03-10 10:41:00,124 [INFO] core.ohlc_builder: NSE_INDEX|Nifty 50 {‘t’: 1773119400, ‘o’: 24192.7, ‘h’: 24215.85, ‘l’: 24191.5, ‘c’: 24204.7, ‘v’: 0}
2026-03-10 10:42:00,136 [INFO] core.ohlc_builder: NSE_INDEX|Nifty 50 {‘t’: 1773119460, ‘o’: 24204.6, ‘h’: 24215.25, ‘l’: 24203.9, ‘c’: 24214.5, ‘v’: 0}
2026-03-10 10:43:00,117 [INFO] core.ohlc_builder: NSE_INDEX|Nifty 50 {‘t’: 1773119520, ‘o’: 24215.0, ‘h’: 24221.45, ‘l’: 24214.75, ‘c’: 24216.5, ‘v’: 0}
2026-03-10 10:44:00,119 [INFO] core.ohlc_builder: NSE_INDEX|Nifty 50 {‘t’: 1773119580, ‘o’: 24217.8, ‘h’: 24224.8, ‘l’: 24214.95, ‘c’: 24216.85, ‘v’: 0}
2026-03-10 10:45:00,132 [INFO] core.ohlc_builder: NSE_INDEX|Nifty 50 {‘t’: 1773119640, ‘o’: 24216.2, ‘h’: 24219.0, ‘l’: 24210.8, ‘c’: 24217.05, ‘v’: 0}
2026-03-10 10:46:00,124 [INFO] core.ohlc_builder: NSE_INDEX|Nifty 50 {‘t’: 1773119700, ‘o’: 24217.2, ‘h’: 24229.05, ‘l’: 24217.0, ‘c’: 24222.3, ‘v’: 0}
2026-03-10 10:47:00,118 [INFO] core.ohlc_builder: NSE_INDEX|Nifty 50 {‘t’: 1773119760, ‘o’: 24220.95, ‘h’: 24221.9, ‘l’: 24213.25, ‘c’: 24218.8, ‘v’: 0}
2026-03-10 10:48:00,148 [INFO] core.ohlc_builder: NSE_INDEX|Nifty 50 {‘t’: 1773119820, ‘o’: 24218.35, ‘h’: 24224.7, ‘l’: 24216.0, ‘c’: 24224.7, ‘v’: 0}
2026-03-10 10:49:00,131 [INFO] core.ohlc_builder: NSE_INDEX|Nifty 50 {‘t’: 1773119880, ‘o’: 24223.95, ‘h’: 24233.2, ‘l’: 24222.5, ‘c’: 24231.1, ‘v’: 0}
2026-03-10 10:50:00,145 [INFO] core.ohlc_builder: NSE_INDEX|Nifty 50 {‘t’: 1773119940, ‘o’: 24231.35, ‘h’: 24232.3, ‘l’: 24221.35, ‘c’: 24222.4, ‘v’: 0}
2026-03-10 10:51:00,128 [INFO] core.ohlc_builder: NSE_INDEX|Nifty 50 {‘t’: 1773120000, ‘o’: 24222.2, ‘h’: 24224.1, ‘l’: 24217.65, ‘c’: 24224.1, ‘v’: 0}
2026-03-10 10:52:00,129 [INFO] core.ohlc_builder: NSE_INDEX|Nifty 50 {‘t’: 1773120060, ‘o’: 24224.15, ‘h’: 24225.8, ‘l’: 24214.0, ‘c’: 24214.0, ‘v’: 0}

4

Hi @Krishnakis_47134930
We have not received any complaints regarding WebSocket ticks not being sent to clients. Additionally, we have reviewed the logs and statistics on our end and did not identify any issues.

Could you please verify if the mode was inadvertently switched to LTP at that time, as this would explain why you only received the Last Traded Price (LTP)?

Thanks!