For a deeper look into our Eikon Data API, look into:

Overview |  Quickstart |  Documentation |  Downloads |  Tutorials |  Articles

question

Upvotes
Accepted
13k 32 12 18

Eikon API proxy timeseries start date ignored

A call to

ek.get_timeseries(["aUSCPTANIFR"], start_date="2015-01-01", end_date="2017-01-1")

returns data beginning from year 1917, while end date is respected. Specifying other date formats, does not work either.

eikoneikon-data-apiworkspaceworkspace-data-apirefinitiv-dataplatform-eikonpythonproxy
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 5.0 MiB each and 10.0 MiB total.

Upvotes
Accepted
591 3 2 3

Hi Gurpreet,

We have identify a server issue causing this behaviour and a fix is planned to return an appropriate error in this scenario. This should be rolled out within the next few weeks.

Thanks

Iain

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 5.0 MiB each and 10.0 MiB total.

Upvotes
4.3k 2 4 5

Available timeseries data for this RIC are only monthly, quarterly or yearly values.

Any request with other interval (tick, minute, hour, session, daily and weekly) returns all data from 1917.

Example :

>>> ek.get_timeseries(["aUSCPTANIFR"], start_date="2015-01-01", end_date="2017-01-1", interval='quarterly')
aUSCPTANIFR VALUE
Date
2015-03-31 -0.062705
2015-06-30 -0.038560
2015-09-30 0.109506
2015-12-31 0.467297
2016-03-31 1.081141
2016-06-30 1.047253
2016-09-30 1.117932
2016-12-31 1.801049

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 5.0 MiB each and 10.0 MiB total.

Thanks for the reponse. It still doesn't make sense why invalid data would be returned, if interval was omitted. At least, a user would like to see an error message stating a required field is missing.

Click below to post an Idea Post Idea