This is the last straw for me; I am shifting to a better platform.
The last two days went perfect and in fact, I was going to congratulate the team today. And then this happened. Historical API and web charts not working since the last 90 minutes.
More than the problem itself, I am dismayed that there is no communication from Upstox about the status, ETA, etc.
See attached screenshot:
It shows net premium as negative, which is correct. But the the total amount is being calculated as if it was positive.
@rishabhjain @orpheus Issues with fundamental correctness are happening on a daily basis. Do you guys realize that these "issues" don't affect just one developer? Now I am not sure whether my algorithms are running correctly or not, and whether the backtested results are correct or not.
You can't push financial APIs with a typical Web 2.0 Agile cadence. Please spend the time and effort to architect and design your system properly and only then publish it / charge money for it.
@excellingtrade Strategy can be to create a proxy. The strategy programs connect to the proxy program which can support multiple websockets. The proxy in turn opens a single websocket to Upstox API. Whenever data arrives on the Upstox websocket, the proxy relays the information to each local websocket.
This is similar to what you described earlier, but instead of storing the data in files, the proxy relays it via local websockets.
@excellingtrade There was news that Upstox received 25mln $ funding in June or thereabouts. How did they manage to go from that peak to this?
See attached screenshot:
It shows net premium as negative, which is correct. But the the total amount is being calculated as if it was positive.
SEBI Scores seems to be the right course of action, given the really slow response times from Upstox. Thanks for informing us.
The error has changed now:
{"code":408,"status":"Request Time-out","timestamp":"2019-02-22T11:02:55+05:30","message":"timeout","error":{"reason":"Your request has timed out"}}
I am able to modify orders through web interface, but they are failing through the API. The returned response is:
{"code":400,"status":"Bad Request","timestamp":"2019-02-22T10:04:06+05:30","message":"Can not modify this order.","error":{"name":"Error","reason":"Can not modify this order."}}
Please don't ask me to post my code or order id. My code has been working fine for the last 30+ days. And the problem is not specific to a particular order id. It's failing for all orders.
The problem is at your end.
This is the last straw for me; I am shifting to a better platform.
The last two days went perfect and in fact, I was going to congratulate the team today. And then this happened. Historical API and web charts not working since the last 90 minutes.
More than the problem itself, I am dismayed that there is no communication from Upstox about the status, ETA, etc.
@guest said in Leaving Upstox:
If u need granullar data, simply create candles on local machine from websocket data...
Note that: websocket feed is a subset of the complete feed. So the OHLC candles created from websocket data will not be exactly the same as actual candles. (But they will be reasonably similar)
@rishi123 I don't need it myself and I am not using python for my upstox client, but for other projects, I have used https://github.com/django/channels when creating websocket servers. If you are already familiar with django creating a websocket proxy is about a day's effort.
@excellingtrade Strategy can be to create a proxy. The strategy programs connect to the proxy program which can support multiple websockets. The proxy in turn opens a single websocket to Upstox API. Whenever data arrives on the Upstox websocket, the proxy relays the information to each local websocket.
This is similar to what you described earlier, but instead of storing the data in files, the proxy relays it via local websockets.
I figured it out myself: when start_date and end_date both are correctly specified, it works fine.
This is in contrast with the documentation which says that start_date and end_date have default values.