I am being throttled by the usage limits for the Eikon Data API when I have played fairly

Matt.Whiteley
Matt.Whiteley
in Eikon Data APIs

I am using the Eikon API with Python on Windows (with a desktop session). I am instantiating a historic_pricing.Definition class and calling .get_data() to retrieve a time series of hourly prices per RIC.


query_definition = historical_pricing.summaries.Definition(
        universe=refined_rics,
        interval=interval,
        fields=[pricing_field],
        start=query_start.strftime("%Y-%m-%d %H:%M:%S"),
        end=query_end.strftime("%Y-%m-%d %H:%M:%S"),
        sessions=[
            historical_pricing.MarketSession.NORMAL,
        ],
    )

1714147581891.png

As you can see in the log, I have batched the requests to be a max of 50 RICs and the date filter restricts the amount of historical price points returned. Typically I am receiving around 5000 data points back per request, which doesn't seem like a problem when I look at the usage limits. Additionally, I am making synchronous calls so I am not going to breach 5 requests per second. Lastly, the daily limit of 5Gb and minute limit of 50Mb are much larger than the data I am requesting per day.


Therefore I cannot understand why I am getting this error: 

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

Best Answer

Answers

  • Matt.Whiteley
    Matt.Whiteley
    Hi Aramyan,


    It shouldn't (in theory!) be anywhere close to 10,000 requests. Of course, I am counting one method call of 'get_data()' as one request, which may not be strictly true. One thing to note is that my internet was very intermittent that day, and perhaps the poor connection was triggering a lot of retry requests, which is why I was then throttled. That's my best guess, as I don't know how it works under the hood.


    Thanks

    Matt

  • aramyan.h
    aramyan.h
    Hi @Matt.Whiteley ,


    As you perhaps rightfully noticed the get_data request with several RICs is not a single call. You can refer also to this thread, which provides more light on it.

    Try Except would be another thing obviously which will result in additional API calls.

    Best regards,

    Haykazs

  • Matt.Whiteley
    Matt.Whiteley

    Hi @aramyan.h - thanks, I read through the thread and that makes a lot more sense, I didn't know the RICs were being iterated over and thus it was one API call per RIC. Is this also how it worked in the 'eikon' library? I see that price streaming is another option but that doesn't seem to let me access historic data, which is critical for my application.

  • Matt.Whiteley
    Matt.Whiteley

    Hi @aramyan.h - thanks, I read through the thread and that makes a lot more sense, I didn't know the RICs were being iterated over and thus it was one API call per RIC. Is this also how it worked in the 'eikon' library? I see that price streaming is another option but that doesn't seem to let me access historic data, which is critical for my application.

  • aramyan.h
    aramyan.h
    Hi @Matt.Whiteley ,


    That should be the same for Eikon as well. I realize your usecase might be different I just provided that thread as an explanation of the situation, but perhaps, you can build the history in a couple of days and then use the streaming, if an option for your use case at all. You may also want to talk to your Account Manager who may suggest another product or workflows.


    Best regards,

    Haykaz

  • Matt.Whiteley
    Matt.Whiteley
    For reference, this
    thread suggests the original eikon library didn't make a request per RIC. I have also checked the source code for the eikon implementation and it appears to send one payload per function call. This will solve my problem but I will verify that with some tests today and confirm here, if that is useful.
  • aramyan.h
    aramyan.h
    That would be very useful indeed, would appreciate you posting your test results here, thank you!

Categories