Bloomberg API request limit

mservidio picture mservidio · Jan 9, 2012 · Viewed 47.6k times · Source

Is there anyway to determine how many requests or how much data you have in your remaining request limit amount for Bloomberg API?

Answer

RockScience picture RockScience · Apr 2, 2014

from Bloomberg HelpDesk on April 2014 (this is valid for a basic desktop client):

We have 3 kind of limits..

You can have no more that 3500 real time fields open at the same time. If you exceed this limit you will see "NA Limit" as error message and you just need to delete some securities/ fields in order for the error message to disappeared and to see the values.

We have also a daily limit. The Daily API limit is 500,000 hits/per day. A "hit" is defined as one request for a single security/field pairing. Therefore, if you request static data for 5 fields and 10 securities, that will translate into a total of 50 hits. so try to refresh just the portion of the spreadsheet that really needs to be refreshed and avoid refreshing it all or reopen it many times a day.

The last limit is a monthly limit. Our monthly limits comes from a proprietary model. Only about 0.4% of our user database ever goes over this limit. This limit is based on unique securities and depends on the type of data being downloaded. For example some of the data on the system such as intra-day is valued a little bit higher than historical end of day for any given list of securities. We do not recommend more than 5000 to 7000 unique identifiers per month and the limit upgrade will only allow you to get data to complete your project. Once a security is used once in a month then if you use it again it will not count again towards the monthly limit.

We normally grant 2 resets per month in case you exceed your daily limit and if you exceed your monthly limit we grant 1 extension per month (10% more), if you breach the limit again you will then need to wait for the midnight for the daily limit to be reset automatically or the end of the month for the reset of the monthly.