Migration of Eikon get_timeseries "tick" interval calls to rd.get_history
When requesting get_timeseries from Eikon Python API with interval ‘tick’, it would return Date,VALUE,VOLUME data:
Date,VALUE,VOLUME
2024-06-27 13:30:00.135,135.79,200
2024-06-27 13:30:00.357,135.86,14
I would call it like this:
while (rows == 50000): #and (df.index[0] >= start_date_time_obj ) :
dfloop = ek.get_timeseries([Symbol_T], start_date = ek_Start_T, end_date = str(df.index[0]), interval = Interval_T)
shape = dfloop.shape
rows = shape[0]
df = pd.concat([dfloop,df], axis=0)
What are the field names to call using Workspace’s rd.get_history?
Is the 50,000 limit still applicable?
Is there a code sample somewhere I can refer to?
Thank you
Best Answer
-
Hi @dgarrard ,
Regarding the related article, Upgrade from using Eikon Data API to the Data library,
For RD library rd.get_history, fields parameter are not required, all available historical fields of instrument will be returned in the result if no field is specified. While the ek.get_timeseries retrieves data only from the default view and map them to OPEN, HIGH, LOW, and CLOSE fields.
However, the field names to be used in Workspace will be suggested to you by the Content team via ticket number 13696720 that was raised on behalf of you and the support team is going to contact you soon to assist with this.
About the limit, for RD library Desktop session, it was also mentioned in the same article that
Usage and Limits Guideline
If you are connecting using a desktop session to Eikon or Workspace via RD Library - the same limit as Eikon Data API applies - as the RD Library is mimicking the Eikon API and still sourcing its data from Eikon. We will keep you posted in case there is any update on this.
Hope this help and please let me know in case you have any further questions
0
Answers
-
Following up on this Question, I have discovered, with the support team help, that whereas the Interval in Eikon was 'tick' to get the data we wanted, in Workspace I must use "tas" to get the Time and Sales data. The following fields worked to give me individual trade price and quantity data:
df = rd.get_history(universe = "MSFT.O", start = "2023-12-20", end = "2023-12-21", fields=["TRDPRC_1","TRDVOL_1"], interval = "tas")
1
Categories
- All Categories
- 6 AHS
- 37 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛