Says, something went wrong. please contact us. What kind of error is this?
Yes the API is not working and throwing below error:
{āstatusā:āerrorā,āerrorsā:[{āerrorCodeā:āUDAPI100500ā,āmessageā:āSomething went wrongā¦ please contact usā,āpropertyPathā:null,āinvalidValueā:null,āerror_codeā:āUDAPI100500ā,āproperty_pathā:null,āinvalid_valueā:null}]}
Yes, I am also getting the same error.
Replicable when multiple days data is requested(>5-6 days approx). At first I thought its a v2 issue. After upgrading to v3, same issue exists. @Ketan @Ketan_Gupta
āGET /v3/historical-candle/NSE_EQ|INE002A01018/minutes/1/2025-07-17/2025-07-05 HTTP/1.1\r\nā
API Error: {
status: 'error',
errors: [
{
errorCode: 'UDAPI100500',
message: 'Something went wrong... please contact us',
propertyPath: null,
invalidValue: null,
error_code: 'UDAPI100500',
property_path: null,
invalid_value: null
}
]
}
Hi @dsouzaedison @Aman_Jha @AMIT_21710050
We have investigated the issue and found that the requests are being rejected due to the large volume of data being requested, which is placing additional load on our servers.
We apologize for the inconvenience caused. To ensure successful responses, we kindly recommend limiting your request to a smaller range of candle data. Specifically, we suggest requesting a maximum of 3ā4 days of 1-minute interval data at a time.
Thank you for your understanding and cooperation.
Thanks you @Ketan ! Is this temporary untill the issue is resolved?
But it was working fine till yesterday? and what if we need more data for our analysis?
1 Like
@Ketan It seems python API library which upstox has developed does not support from_date, only to_date when getting historical data. This means I canāt fetch only 4 days of data. What do you recommend in this case ?
@yuvika_9347091
Here is a function which takes both from date and to date
import upstox_client
apiInstance = upstox_client.HistoryV3Api()
try:
response = apiInstance.get_historical_candle_data1("NSE_EQ|INE848E01016", "days", "1", "2025-03-01", "2025-01-01")
print(response)
except Exception as e:
print("Exception when calling HistoryV3Api->get_historical_candle_data1: %s\n" % e)
@Ketan Our systems arenāt built that way. Its not possible to change the implementation to load 4 days data on a short notice. From date/to date is computed dynamically based on indicators that are being generated. Also, splitting into multiple calls would result in hitting rate limits if we do this for all indicators. At least one monthās minute historical candles should be supported. Please let us know when this will be fixed. Otherwise our systems wonāt run.
1 Like
What you are saying that Upstox just changed the data period which we can request without any prior notice?
1 Like
@Ketan Seriously you guys just decided to reduce data period to 3-4 days with no advance notice to users? That makes the API use-less, please confirm if this is your official response, so we can look for alternate solutions
3 Likes
@Ketan please respond if this will change tomorrow or it will remain same. Since everyone is waiting for a proper response.
2 Likes
@Ketan I donāt understand why your replies are like you donāt want to fix bugs in your system instead you inform your user to do this and that. I think your development teams are too weak that they canāt even validate these things. This is your serverās issue not API userās. You should increase capability of your servers. Are you trying to say that you will not solve issue from your single application but millions of users need to change their application / script to work according to your faulty API?
6 Likes
we too received same error even try to download 1 days data..
to_date = today - datetime.timedelta(days=1)
print(f"Today is not Thursday - using data up to {to_date}")
from_date = to_date - datetime.timedelta(days=2)
# Convert to string format
from_date_str = from_date.strftime('%Y-%m-%d')
to_date_str = to_date.strftime('%Y-%m-%d')
if firstMessage:
print(f"from_date: {from_date_str}, to_date: {to_date_str}")
firstMessage=False
logging.info(f"Getting data for {symbol} from {from_date_str} to {to_date_str}")
# Use correct API call format for HistoryApi
api_response = api_instance.get_historical_candle_data1(
instrument_key=instrument_key,
interval=interval,
from_date=from_date_str,
to_date=to_date_str,
api_version='2.0'
It broke my code as well and there is no prior notice. very disappointing to see @Upstox being such unprofessional.
1 Like
Issue hasnāt been resolved yet. Hard to believe the reason given earlier. Itās likely a bug introduced in the latest release. Unsure if any attention is being paid to userās concerns. If this isnāt fixed then we wonāt be able to place orders via algos tomorrow. With frequent issues like these, Upstox is becoming really tough to rely on. TBH, your engineering team needs to do a better job at analysing the impact before shipping buggy features. And avoid releasing mid-week at least. Iād rather focus on integrating stable broker APIs rather than spending time on adding work-arounds for unstable APIs at unprecedented timings! cc: @mike @Sachin_Khodpia @Ushnota
4 Likes
I am just glad that I had stopped my intraday algo earlier, with positional algos atleast we can try and manage manually. Need to think twice before starting an intraday algo with the approach shown on this thread. It clearly means there is no monitoring on their end, no auto scaling, not sure what level of tests they have.
1 Like