'Processing power: Prior to the release of Microsoft Excel 2007, all spreadsheets were single threaded and could not take advantage of today's multi-core technology. 25K valid mnemonics in the Bloomberg API data dictionary. To put it into perspective, there are approx. One final note concerning the data limits, I am not sure of the actual limit numbers for each product, but I am very sure that 1,000,000 mnemonics requested in one day would be far too many and put you over the daily limits for both products. Cofibreak (great user name) is referring to Bloomberg's Data License product, which provides customers a way to obtain large volumes of static data within a file via FTP.

To address the FTP solution, as a side note. Therefore, if you make s historical or subscribe type call that requests 10 securities and five fields at once, it will still be counted by the Bloomberg backend as 50 hits.

The limits are not based on the number of function calls you make.

If you surpass this, you will receive a -3001 error code. It is measured in numbers of unique securities being subscribed to at any one time. There is also a limit for the number of concurrent real-time subscriptions that can be made. NET, a DataLimitExceededException will be thrown. If you hit your monthly limit, the error code will be -4002 or an error message of ' #N/A Mth Lmt' (ActiveX Data Control or BDx() functions in Excel).

If you hit your daily limit you will receive a -4001 error code (if using C API), or the error message ' #N/A Dly Lmt'.

Obviously, if you then continue to make this same static request (also called polling), it will be 50 hits each time it is sent out. For instance, if you make a static request that contains 10 securities and 5 fields, then that would be a total of 50 hits. However, for a static request, your hit total will increase by the aggregate of each security/field pairing.

The number of fields does not impact your hit total on a real-time request. To you this means less hits, as your daily hit total will only be increased by the total number of securities in the real-time request. This is far much less taxing on the Bloomberg backend.

After that point, tick updates are sent from the Bloomberg backend until you either desubscribe or disconnect. The reason for that is that a real-time subscription only entails a single header request (for the initial paint of real-time data) and a tick monitor request.

Real-time requests are always preferred to repeated static requests.

However, the objective of Bloomberg is the same for both and the tips for managing your API limits are also the same. Please be aware that the limits for the desktop are much lower than those for the server license.

Bloomberg api call