Issue with upstox api. Nifty trades are not going in algo

Trading
1

I am using algorooms since 4 months.however since last 2 days trades are not going in nifty only. Algorooms team is telling that issue is from upstox api side…kindly look in to it
Regards

1 Like
2

Hi @nisha_42240240,

Welcome to the Upstox Community!

We are checking this and will get back to you soon, thanks.

3

I am facing the same problem since Friday. Is there any solution?

4

Please check it ASAP. This is the error what I am getting while modifying order. HTTPError: 400 Client Error: Bad Request for url: https://api-hft.upstox.com/v2/order/modify. Sometime it works and sometime it wont. Even historical data api is not working.

Error in Historical API:
/v2/historical-candle/intraday/NSE_FO%7C63437/1minute (Caused by SSLError(SSLEOFError(8, ‘[SSL: UNEXPECTED_EOF_WHILE_READING] EOF occurred in violation of protocol (_ssl.c:1000)’)))

5

Please share any emergency contact details so that we can get instant reply as in live market if we get errors we need to fix it ASAP.

6

Hi @Jagdish_j_ptl can you share your 6 digit user Id and give more details of the issue you are facing so we can investigate further.

Thanks!

7

68ACEW is my user id.

At 10:38:08 am I got error “requests.exceptions.SSLError: HTTPSConnectionPool(host=‘api.upstox.com’, port=443): Max retries exceeded with url: /v2/historical-candle/intraday/NSE_FO%7C63437/1minute (Caused by SSLError(SSLEOFError(8, ‘[SSL: UNEXPECTED_EOF_WHILE_READING] EOF occurred in violation of protocol (_ssl.c:1000)’)))” while fetching historical data with below URL.
https://api.upstox.com/historical-candle/intraday/NSE_FO|63437/1minute

At 9:46:17

while modifying order I got HTTPError: 400 Client Error: Bad Request for url: https://api-hft.upstox.com/v2/order/modify

This was the data I was posting.

{“order_id”: “250218025096010”, “quantity”: 150, “price”: 200.15, “disclosed_quantity”: null, “trigger_price”: 201.15, “validity”: “DAY”, “order_type”: “SL”}

8

I think it might be using older protocols, use with TLSv1.3, servers might be supporting TLSv1.2 also but not below that.