famous Backend error. 400 Bad Request starting from yesterday

The api works fine until yesterday. Starting from yesterday, i keep getting the 404 bad request. I simply just wrote a try catch loop for 3 times and it worked through.
However, starting from this morning, my try catch loop could not give me any result. I increased the repeat time to 20 times, and it didn't succeeded once.
To replicate:
python 3.6
import eikon as ek
ek.set_app_id(app_id)
ek.set_timeout(120)
date = '2018-03-28'
symbol_ric = ['AUDCAD=', 'AUDCHF=', 'AUDJPY=', 'AUDNZD=', 'AUD=', 'CADCHF=', 'CADJPY=', 'CHFJPY=', 'EURAUD=',
'EURCAD=', 'EURCHF=', 'EURGBP=', 'EURJPY=', 'EURNZD=', 'EUR=', 'GBPAUD=', 'GBPCAD=', 'GBPCHF=',
'GBPJPY=', 'GBPNZD=', 'GBP=', 'NZDCAD=R', 'NZDCHF=R', 'NZDJPY=', 'NZD=', 'CAD=', 'CHF=', 'JPY=']
req, error = ek.get_data(symbol_ric, parameters={'SDate':f'{date}', 'EDate':f'{date}'}, fields=['TR.ASKPRICE','TR.BIDPRICE'], debug=True)
some times the result is timeout, sometimes it is returns a dataframe with some ric missing
full log on one trial with debug=True on is attached.trdebug-log.txt
I tried to get the rate one by one, and it always stuck on AUDCHF=
please advise how to fix this!
Answers
-
Thank you for reporting this issue. I have reproduced and escalated it. I will post on this thread as soon as I hear back from the resolver team. As an immediate workaround you can retrieve yesterday's closing bid and ask rates for FX RICs using CLOSE_BID and CLOSE_ASK fields, e.g.
ek.get_data(symbol_ric, fields=['CLOSE_BID','CLOSE_ASK'])
0 -
thanks, the close_bid works.
0 -
I also have the same problem starting yesterday........
0 -
So right now the TR.ASK and TR.BID is working, but no matter what SDATE and EDATE i post to the request for ['CLOSE_BID','CLOSE_ASK'], it will give me todays data. any thoughts on that?
ek.get_data('JPY=', parameters={'SDate':'2018-03-01', 'EDate':'2018-04-01'},fields=['CLOSE_BID','CLOSE_ASK'], debug=True)
0 -
CLOSE_BID and CLOSE_ASK fields can only provide bid/ask rates as of yesterday's close. SDate and EDate parameters are not applicable to these fields and are ignored in the request. In general field names that do not start with TR.* come from the real-time data stream and do not provide timeseries of history.
0 -
ok, only found out that today. I will keep using TR.askprice and TR.bidprice since it was fixed(I assume?)
0 -
We identified one possible source of the problem, but not yet sure if this was indeed the root cause. We're still continuing the investigation.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 685 Datastream
- 1.4K DSS
- 615 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 252 ETA
- 556 WebSocket API
- 38 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 652 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 27 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 193 TREP Infrastructure
- 228 TRKD
- 917 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛