The log said:
2019-04-03 09:19:42,118 -- pyeikon -- DEBUG -- Request:{'Entity': {'E': 'TimeSeries', 'W': {'rics': ['.GDAXI'], 'fields': ['*'], 'interval': 'monthly', 'startdate': '1850-01-01T00:00:00', 'enddate': '2019-04-03T00:00:00'}}}I re-ran the code that both you and Jason gave and I am still only getting one month of data. This doesn't happen for other codes, like '.SPX'.
Does it have to do with my permissions?
Trying to get .GDAXI history, but Eikon only returning the last data point?

>>> start = datetime.datetime(1850, 1, 1)
>>> end = datetime.datetime.now()
>>> ek.get_timeseries(".GDAXI", interval="monthly", start_date=start, end_date=end)
.GDAXI HIGH CLOSE LOW OPEN COUNT
Date 2019-03-31 11823.29 11526.04 11299.8 11584.24 -1.0
>>>
Best Answer
-
@handrew11
The behavior you experienced is unexpected. Since it is specific to your Eikon account, as I cannot reproduce it on my end, the only way we can investigate it is by opening a ticket with Refinitiv Helpdesk and working together in direct contact with you. I would happily open a ticket on your behalf, however you chose to register on this portal with a personal rather than a business email address, which effectively makes you anonymous on these forums.
For this reason you need to reach out to Refinitiv Helpdesk yourself and open a support case. Refinitiv Helpdesk can be reached by either calling the Helpdesk phone number in your country or by using Contact Us capability in your Eikon application.0
Answers
-
Hi @handrew11: The reason its failing is that you are trying to pass a datetime to a function that is expecting a string - see correct code below:
start = str(datetime.datetime(1850, 1, 1).date())
end = str(datetime.datetime.now().date())
print(start, " ", end)
df2 = ek.get_timeseries(".GDAXI", interval="monthly", start_date=start, end_date=end)
df20 -
One should be able to use datetime for start_date and end_date arguments of get_timeseries method. I have no problem executing the code snippet @handrew11 provided, and I retrieve full timeseries going back to 1987.
@handrew11, I suggest you use Fiddler to capture the HTTP request going on the wire. Alternatively you may enable logging in eikon library as followsek.set_log_path(r'C:\Temp')
The log file name will be pyeikon.%Y%m%d.%H-%M-%S.log
ek.set_log_level(10)
After you started Fiddler or enabled logging in eikon library reproduce the issue and see the request captured in Fiddler or in the log file.
The request going on the wire should be{'Entity': {'E': 'TimeSeries', 'W': {'rics': ['.GDAXI'], 'fields': ['*'], 'interval': 'monthly', 'startdate': '1850-01-01T00:00:00', 'enddate': '2019-04-03T11:04:51.059467'}}}
Is this what you get? Or is the request generated on your end different?
0 -
The log said:
2019-04-03 09:19:42,118 -- pyeikon -- DEBUG -- Request:{'Entity': {'E': 'TimeSeries', 'W': {'rics': ['.GDAXI'], 'fields': ['*'], 'interval': 'monthly', 'startdate': '1850-01-01T00:00:00', 'enddate': '2019-04-03T00:00:00'}}}
I re-ran the code that both you and Jason gave and I am still only getting one month of data. This doesn't happen for other codes, like '.SPX'.
Does it have to do with my permissions?
0 -
The request looks correct and I don't think the problem is due to your entitlements. Could you also post the response to the request as it appears in the log file you created?
0 -
2019-04-03 09:19:42,266 -- pyeikon -- DEBUG -- HTTP Response code: 200
2019-04-03 09:19:42,266 -- pyeikon -- DEBUG -- HTTP Response: {"timeseriesData":[{"dataPoints":[["2019-03-31T00:00:00Z",11823.29,11526.04,11299.8,11584.24,-1]],"fields":[{"name":"TIMESTAMP","type":"DateTime"},{"name":"HIGH","type":"Double"},{"name":"CLOSE","type":"Double"},{"name":"LOW","type":"Double"},{"name":"OPEN","type":"Double"},{"name":"COUNT","type":"Long"}],"ric":".GDAXI","statusCode":"Normal"}]}0 -
any idea @Alex Putkov.1? I also tried with a different app key and still had the same problem. I'm on a Mac using Python 3.7 with the latest version of Eikon too. I think also .FTSEMIB has the same problem
0 -
This is very puzzling. Everything looks normal except the response from the Web service. I don't understand what could possibly be the reason you and I get different results. Could you try this request:
ek.get_timeseries(".GDAXI", interval="monthly", start_date='2016-01-01', end_date='2019-04-03')
I just changed the value of the start_date to be more recent. Does it make any difference? Do you still only retrieve one row of data timestamped 2019-03-31? What if you change the interval to "weekly" or "daily"? Are you able to display monthly price chart for .GDAXI in Eikon application?
0 -
A later start date doesn't change anything. Neither does doing 'weekly'. 'Daily' seems to work as expected. The monthly price chart still works in the Eikon application.
0 -
Hi @Alex Putkov.1 thank you for response. I would love if you could open a ticket for me. My email address on this forum is also the one associated with my Eikon account, so you can go ahead and use that one. Thanks!
0 -
@handrew11
Sure, no problem. I was able to locate you in Eikon user database and opened support ticket on your behalf. Refinitiv Helpdesk will reach out to you to investigate the issue. Just in case you need a reference to communicate with the Helpdesk, your support case number is 07504050.0
Categories
- All Categories
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 684 Datastream
- 1.4K DSS
- 613 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
- 248 ETA
- 552 WebSocket API
- 37 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
- 628 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
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 191 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 84 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛