Discover Refinitiv
MyRefinitiv Refinitiv Perspectives Careers
Created with Sketch.
All APIs Questions & Answers  Register |  Login
Ask a question
  • Questions
  • Tags
  • Badges
  • Unanswered
Search:
  • Home /
  • Eikon Data APIs /

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

Overview |  Quickstart |  Documentation |  Downloads |  Tutorials |  Articles

avatar image
Question by Nabil Edriss Sanchez1 · Jun 21, 2019 at 11:47 AM · eikoneikon-data-apiworkspacepythonworkspace-data-apirefinitiv-dataplatform-eikonerrorerror-429

Error code 429 | Client Error: Too Many Requests - Too many requests, please try again later.

Hi. We are looking for the maximum price, the minumum price, and the max and min closing price for a period for a list of RICS and Eikon API says Error code 429 Client Error: Too Many Requests - Too many requests, please try again later.

We are downloading info for less than 100 Rics.

In the image you can see some inputs and the code.

This is urgent for Banco Santander.

Thanks in advance.

PD: Please note after this error, we can download data for two single RICs. It seems
it is not related with daily limits (but we're not sure). 
<br>
captura.jpg (99.4 KiB)

People who like this

0 Show 0
Comment
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

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

4 Replies

  • Sort: 
avatar image
REFINITIV
Best Answer
Answer by Alex Putkov.1 · Jun 21, 2019 at 05:54 PM

There's indeed a limit on how many requests can be sent per second. But given that data retrieval methods of Eikon Data APIs are synchronous executing these methods in a loop or inside dataframe 'apply' method in itself is highly unlikely to saturate the throttle. I think realistically the throttle will only be saturated by code running on multiple threads. I think there must have been something else (another Julyter notebook or another script executed in a separate process) running on the machine when the issue occurred.
It may nevertheless be preferable to retrieve timeseries for multiple RICs in a single request, as @davidk suggested. However in this case I would advise using get_data method rather than get_timeseries because get_timeseries returns a max of 3K rows of timeseries per request, and this limit is shared by all RICs in the same request. get_data method does not impose such limitation.
Whichever method you choose to use, I suggest always keeping an eye open for multiple scripts running simultaneously.

Comment

People who like this

0 Show 1 · Share
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

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

avatar image
Nabil Edriss Sanchez1 · Jun 24, 2019 at 08:42 AM 0
Share
I understand. Thank you very much for the help. I'll see if I can solve the problem.
avatar image
REFINITIV
Answer by nick.zincone · Jun 21, 2019 at 11:56 AM

Hi @Nabil Edriss Sánchez,

Please see this thread regarding Error code 429.

Comment

People who like this

0 Show 0 · Share
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

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

avatar image
Answer by Nabil Edriss Sanchez1 · Jun 21, 2019 at 12:04 PM
Thank you. I have read the previous link and another related to the error.

We have not exceeded the daily data limit, since it works for a single RIC.

I understand that what happens is that queries per second are exceeded (or something related).

How can we then use the API to download historical information for a list of RICs?

Can you please review the code and give us a suggestion or solution?

If it is not possible to make such a simple query in the API, then it is not a useful API for us ...

Thanks in advance.

Comment

People who like this

0 Show 0 · Share
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

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

avatar image
Answer by davidk · Jun 21, 2019 at 01:48 PM

@Nabil Edriss Sánchez I am a quant at another firm, not from Reuters, but there is a limit of n requests per second, so running a query like this inside df.apply is always failure-prone. However you can request many RICs in a single request. My suggestion would be to refactor your request if possible to request all the RICs at once. If the time series start and end dates that you require vary by security, just get the whole date range from min start to max end for all the securities, and then subset it down ex post.

Comment
Christiaan Meihsl

People who like this

1 Show 1 · Share
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

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

avatar image
Nabil Edriss Sanchez1 · Jun 24, 2019 at 08:39 AM 0
Share
Thank you very much for your kindness and help! It is a good idea, so tedious, but there is no other way aparently

Watch this question

Add to watch list
Add to your watch list to receive emailed updates for this question. Too many emails? Change your settings >
9 People are following this question.

Related Questions

​Error code 429 - suggestions

EikonError: Error code 429 | Client Error: Too many requests, please try again later. Wait for 51602 seconds.

error line 151 data_grid.py

Eikon API proxy doesn't start (black screen after loading logging page)

Is Eikon API down?

  • Copyright
  • Cookie Policy
  • Privacy Statement
  • Terms of Use
  • Anonymous
  • Sign in
  • Create
  • Ask a question
  • Spaces
  • Alpha
  • App Studio
  • Block Chain
  • Bot Platform
  • Connected Risk APIs
  • DSS
  • Data Fusion
  • Data Model Discovery
  • Datastream
  • Eikon COM
  • Eikon Data APIs
  • Electronic Trading
    • Generic FIX
    • Local Bank Node API
    • Trading API
  • Elektron
    • EMA
    • ETA
    • WebSocket API
  • Intelligent Tagging
  • Legal One
  • Messenger Bot
  • Messenger Side by Side
  • ONESOURCE
    • Indirect Tax
  • Open Calais
  • Open PermID
    • Entity Search
  • Org ID
  • PAM
    • PAM - Logging
  • ProView
  • ProView Internal
  • Product Insight
  • Project Tracking
  • RDMS
  • Refinitiv Data Platform
    • Refinitiv Data Platform Libraries
  • Rose's Space
  • Screening
    • Qual-ID API
    • Screening Deployed
    • Screening Online
    • World-Check One
    • World-Check One Zero Footprint
  • Side by Side Integration API
  • TR Knowledge Graph
  • TREP APIs
    • CAT
    • DACS Station
    • Open DACS
    • RFA
    • UPA
  • TREP Infrastructure
  • TRKD
  • TRTH
  • Thomson One Smart
  • Transactions
    • REDI API
  • Velocity Analytics
  • Wealth Management Web Services
  • Workspace SDK
    • Element Framework
    • Grid
  • World-Check Data File
  • 中文论坛
  • Explore
  • Tags
  • Questions
  • Badges