BLPAPI Core User Guide
BLPAPI Core User Guide
5
Last Updated: 5/19/2016
BLOOMBERG OPEN API – CORE USER GUIDE
Related Documents
Document Name
All materials including all software, equipment and documentation made available by Bloomberg are for informational purposes only. Bloomberg and its
affiliates make no guarantee as to the adequacy, correctness or completeness of, and do not make any representation or warranty (whether express or
implied) or accept any liability with respect to, these materials. No right, title or interest is granted in or to these materials and you agree at all times to
treat these materials in a confidential manner. All materials and services provided to you by Bloomberg are governed by the terms of any applicable
Bloomberg Agreement(s).
Contents
Related Documents ................................................................................................................................................................. 2
Contents .................................................................................................................................................................................. 3
1. About This Guide............................................................................................................................................................. 5
2. API Capabilities ............................................................................................................................................................... 5
2.1. Request/Response .................................................................................................................................................. 5
2.2. Subscription............................................................................................................................................................. 5
2.3. Publishing ................................................................................................................................................................ 5
3. Symbology....................................................................................................................................................................... 5
3.1. Nomenclature .......................................................................................................................................................... 5
3.2. Symbology for Bloomberg Securities ...................................................................................................................... 5
3.3. Agency Security Identifier Usage ............................................................................................................................ 7
3.3.1. Bloomberg Open Symbology .......................................................................................................................... 7
3.3.2. ISIN.................................................................................................................................................................. 7
3.3.3. CUSIP (ID_CUSIP) ......................................................................................................................................... 7
3.3.4. SEDOL ............................................................................................................................................................ 7
3.4. Loading a Security................................................................................................................................................... 8
3.5. Yellow Keys ........................................................................................................................................................... 10
3.5.1. [Govt] — Government securities ................................................................................................................... 10
3.5.2. [Corp] ............................................................................................................................................................. 11
3.5.3. [Mtge] ............................................................................................................................................................ 13
3.5.4. [M-Mkt] — Money Market .............................................................................................................................. 14
3.5.5. [Muni] ............................................................................................................................................................. 15
3.5.6. [Pfd] — Bloomberg’s Preferreds Platform ..................................................................................................... 16
3.5.7. [Equity] .......................................................................................................................................................... 17
3.5.8. [Comdty] — Commodity ................................................................................................................................ 19
3.5.9. [Index] — Bloomberg Indexes ....................................................................................................................... 21
3.5.10. [Curncy] — Currency ..................................................................................................................................... 22
3.5.11. Futures (Not a key) ........................................................................................................................................ 23
3.5.12. Options (Not a key) ....................................................................................................................................... 26
3.5.13. Pages (Not a key) .......................................................................................................................................... 29
3.6. Fields ..................................................................................................................................................................... 31
3.6.1. Looking up Bloomberg fields using FLDS <GO> .......................................................................................... 31
3.7. Parameter Overrides ............................................................................................................................................. 31
3.8. Historical Dates ..................................................................................................................................................... 31
4. Subscription Options ..................................................................................................................................................... 33
5. Schema ......................................................................................................................................................................... 34
6. Bloomberg API Products ............................................................................................................................................... 35
6.1. B-PIPE ................................................................................................................................................................... 35
6.2. DDM ...................................................................................................................................................................... 35
6.2.1. B-PIPE/Platform Packages ........................................................................................................................... 36
6.3. Server API ............................................................................................................................................................. 36
6.4. Desktop API .......................................................................................................................................................... 37
2. API Capabilities
2.1. REQUEST/RESPONSE
Data is requested by issuing a Request and is returned in one or more Messages—based on response size. A wide
variety of Requests is available from reference to historic. Some of these features are not available to all users on all
products.
2.2. SUBSCRIPTION
For most services, a Subscription is created that results in an initial starting value for all fields requested, followed by a
stream of updates as the values change until the Subscription is explicitly cancelled (unsubscribed) by the application.
2.3. PUBLISHING
The Bloomberg API allows customer applications to publish page-based, record-based data, as well as any other client-
designed data. This data can then be consumed as per any Bloomberg-provided data. Customer data can be published
for distribution within the customer’s enterprise, contributed to the Bloomberg infrastructure, distributed to others or used
for warehousing. This is done via the suitable Bloomberg Platform product. Publishing applications might simply broadcast
data or they can be “interactive,” responding to feedback from the infrastructure about the currently active Subscriptions
from data consumers. Contributions and local Publishing/Subscribing via the Bloomberg Platform are outside the scope of
this course and will be discussed in their own course.
3. Symbology
3.1. NOMENCLATURE
Access to data via the API is keyed by a topic. This topic may only contain alpha numerics, non-leading spaces and ‘/’.
All topics begin with “//” followed by provider name, a “/”, the provider service name, a “/” and the unique Identifier within
that particular service.
The API allows setting a default provider name and service name in which case just the unique identifier can be used. For
example, “//blp/mktdata/IBM US Equity” can be accessed as “IBM US Equity” if “//blp/mktdata” is set as
default.
<Identifier Value> Unique identifier value according to <Identifier Type>. For /ticker—
this is the Ticker name and is required.
[Provider] Optional mnemonic that has contributed pricing for the given
security preceded by a “@”. If <Provider> is not specified, a
default value may apply depending on product.
[Pricing Source] Optional, generally two-character mnemonic for the data source
where the security is traded. For example, in the Equities Business,
the Data Source is the Exchange.
<Yellow Key> Text equivalent of one of the Bloomberg yellow function keys:
Govt
Corp
Mtge
M-Mkt
Muni
Pfd
Equity
Comdy
Index
Curncy
The default identifier type for a security is the Bloomberg Ticker format, for example, “IBM US Equity”. This would be
equivalent to “/ticker/IBM US Equity”. Since all data is provided on services, this can be fully expanded to
“//blp/mktdata/ticker/IBM US Equity”.
3.3.2. ISIN
A 12-character identifier assigned by the local national numbering agency. The International Securities Identification
Number (ISIN) consists of a two-letter country code, followed by the nine character alphanumerical national security
identifier and a check digit (for example: US4592001014).
Equity Options: ISIN is supported for BMF, South Korea and certain European equity option exchanges only.
API: current value available.
3.3.4. SEDOL
Stock Exchange Daily Official List number (SEDOL) issued by the London Stock Exchange to identify foreign stocks,
especially those that are not actively traded in the U.S. and do not have a CUSIP number. SEDOL numbers issued prior
to March 8, 2004, have seven digits. SEDOLs issued after this date have seven alphanumeric characters, with the first
character always a letter. This SEDOL is associated with the country listed in the field SEDOL1 ISO Country (ID208,
SEDOL1_COUNTRY_ISO).
A security can have multiple SEDOL numbers assigned to it. The order in which the various SEDOL fields (ID_SEDOL1,
ID_SEDOL2, ID_SEDOL3, ID_SEDOL4 and ID_SEDOL5) are populated does not have any real significance. It simply
depends on the order in which they are assigned by the SEDOL Master file.
For example, to load BAC 6.625 12/31/49 <Pfd>, enter BANK OF AMERICA in the command line, then select the
security that is desired from the list of suggestions.
Note: To refine the list of security matches to those most relevant to a specific market sector, press the
associated <Yellow Key>.
2. Security Finder (SECF): To search Bloomberg’s database of security tickers using basic lookup criteria, enter
SECF <GO>. For preferred securities, select the FI tab, then select the Pfd sub-tab.
3. (Ticker) <Yellow Key> <GO>: To directly load a security if the user already knows the Ticker, enter the Ticker in
the command line, press the security’s yellow market sector key, then press <GO>.
For example, to directly load the HSBC Holdings preferred security with a coupon of 8% and a perpetual maturity,
enter HSBC 8 12/31/49 <Pfd>.
Note: On Bloomberg, preferred securities with a perpetual maturity use 12/31/49 as a maturity date.
4. Additionally, shortcuts are available to help users quickly load securities.
Shortcuts
In addition to the methods above, to load any type of security on Bloomberg, shortcuts and tips designed specifically to
assist in finding securities are available.
Users can use the following shortcuts and tips to find and load securities:
▪ (Unique Identifier) <Yellow Key> <GO>: To directly load a security if a user already knows a unique identifier
assigned to the security, such as a Committee on Uniform Security Identification Procedures (CUSIP) number, an
International Securities Identification Number (ISIN) or a Bloomberg ID (BBGID), enter the identifier in the command
line, press the yellow key, then press <GO>.
▪ For example, to load the preferred security assigned CUSIP 060505344, enter 060505344 <Pfd> <GO>.
▪ ID (Unique Identifier) <GO>: To directly load a security if a user already knows a unique identifier assigned to the
security, such as a Committee on Uniform Security Identification Procedures (CUSIP) number, an International
Securities Identification Number (ISIN) or a Bloomberg ID (BBGID), in the command line enter ID followed by the
identifier, then press <GO>.
▪ For example, to load the preferred security assigned CUSIP 060505344, enter ID 060505344 <GO>.
The ID (Unique Identifier) shortcut applies to all fixed income securities with unique identifiers.
Index <F10> Generic interest rates, Economic indices such as CPI, GDP, Equity, Indices
Note that Yellow Keys are case sensitive and must be spelled exactly like the above.
Defaults to change the default behavior are available on the Terminal for all products, with the exception of B-PIPE
applications.
3.5.2. [CORP]
Bloomberg's suite of Credit <Corp> functionality provides an integrated fixed income platform to support user’s workflow
from idea generation to execution. Access to market-moving news, research and economic data combined with real-time
market monitors, yield curve analytics and fundamental data provide a broad market perspective that can help shape the
user’s investment strategies and trigger new trade ideas.
CDS
Issuer x CDS x Currency x Debt Type x Tenor x Pricing Source x Yellow Key
MS CDS USD SR 5Y CBVAL Corp
BARC CDS EUR SUB 5Y CBVAL Corp
CDS and CDS indices are covered by both <Corp> or <Curncy> as follows:
CDS/CDS Indices Description
MS CDS USD SR 5Y CBVAL Corp Morgan Stanley CDS USD Senior 5-Year, Source CBVAL
or CMWD1U5 CBVAL Curncy
ITRX EUR CDSI GEN 5Y Corp Markit iTraxx Europe Generic 5-year CDS Index
or ITRXEBE Curncy
3.5.3. [MTGE]
Bloomberg’s suite of Mortgage <Mtge> functionality provides an integrated Platform to support a user’s workflow from
idea generation to decision making. Access to market-moving news, research and economic data combined with real-time
market monitors and interest rate analytics provide the broad market perspective that can help shape the user’s
investment strategies and trigger new trade ideas.
The security type that is on the Mtge yellow key is mainly mortgage-backed securities. Within this category are Residential
MBS (RMBS), ABS, Commercial MBS (CMBS), CDO, CLO, Pools, Generic and TBAs (to be announced).
Note that the most of Mortgage Tickers are currently available to Bloomberg users only on B-PIPE, with the data
being available through Data License. Mortgage data is available via Server API.
Mtge TK <GO> —This is a Mortgage Ticker lookup where the user can find a list of Tickers for Pool, Agency CMO,
Generic and TBAs.
3.5.5. [MUNI]
The <MUNI> yellow key is specifically dedicated to U.S. municipal bonds. Most of the munis are only available to
Bloomberg users on B-PIPE; the data is available via Data License. Municipal data is available via Server API.
Muni Description
969737BS Muni Williamson County, IL. Build America Bonds-Taxable-Alt rev source B-direct
pmt
249174MQ Muni Denver City & Country SCH Dist #1, Taxable-SER C-Build America Bonds
Direct Pmt to issuer
3.5.7. [EQUITY]
Instruments covered under the Equity key include stocks (listed and OTC), American Depositary Receipts (ADRs)/Global
Depositary Receipts (GDRs), closed-ended funds, Exchange-traded funds, options, warrants, open-ended mutual funds
and hedge funds.
Equity Description
Mutual and hedge fund Tickers on Bloomberg consist of a proprietary 7-character Ticker root symbol code that, as much
as possible, is made up of the first characters of the asset management company’s name as well as the fund’s name.
Asian funds tend to have 8-digit numbers as root symbol code. If there are different share classes, then the share class
type is also incorporated within the Ticker root symbol. This is again followed by the Exchange code, which for open-
ended funds represents the country code of the country of domicile of the fund.
For example:
FIDSPSA LN Equity — Fidelity Investment Funds ICVC – Special Situations Fund – Accumulation (A) Retail Shares
FIDESSY LN Equity — Fidelity Investment Funds ICVC – Special Situations Fund – Accumulation (Y) Retail Shares
FIDSPWA LN Equity — Fidelity Investment Funds ICVC – Special Situations Fund – Accumulation (W) Retail Shares
Certain U.S. hedge funds’ data is protected by SEC under Regulation D. To be able to view or consume its data via
Bloomberg, customers would need to be registered as Accredited Investors (investors who are financially sophisticated
and have a reduced need for the protection provided by certain government filings).
PDFE <GO> Historical convention defaults and quick links to other settings for equity
DPDF <GO> Dividend and Corporate Action settings
IFTD3DBM Index Imarex TD3 Bal of Month Arabian Gulf to Japan (VLCC) Shipping Rate $/Day
S&P 500 FUTURE Dec15 SPZ5 ELEC Index //blp/mktdata/ticker/SPZ5 ELEC Index
Bloomberg’s Commodities Search functionality is broken down into different databases that cover a wide array of items,
such as futures contracts, energy assets, storm and weather coverage, and power data, which users can use to search an
extensive list of Tickers and assets. After accessing Tickers, they can develop their analysis with related data, charts,
research and news, as well as real-time chat rooms with commodities professionals. Sector-specific monitors and
analytics help narrow their focus, so they target exactly the data they need.
The main Commodity Markets (CMDTY) menu provides a summary of key Commodities functionality.
Users can drill down to identify the functions best suited to their workflow, from monitors and Ticker search engines to the
electronic trading menu where they can access the full set of electronic trading capabilities offered by the Bloomberg
Professional service. The path at the top of each menu shows them where they are in the overall menu hierarchy.
Users can drill down to identify the functions best-suited to their workflow, from monitoring equity indexes to building their
own custom indexes. The path at the top of each menu shows them where they are in the overall menu hierarchy. Index
Note: Users can click “Home” to browse Bloomberg’s full set of market sector offerings, products, communication
tools and Help resources.
1. Most-active Tickers — These Tickers always end with an A, e.g., CLA COMB Comdty. They always represent the
most-active contract (pointing to the actual contract Ticker rather than generic). “Active” is normally determined based
on the number of open interests (exceptions may apply).
2. Generics — These Tickers end with numbers starting from 1 (1st contract month), e.g.,. CL1 COMB Comdty. The
Ticker will roll to the next contract upon expiry of current contract. When requesting historical data, generics string
together contracts based on the generics’ settings and go back in history as long as data is available (in contrast,
individual contract Tickers would only have historical data up to its first trading date).
Futures Description
IBMF=Z5 GR Equity IBM stock future, expiring in Dec 2015, traded at Eurex
CLZ2 COMB Comdty WTI Crude oil future, expiring in Dec 2022, Day&Night session, traded at
NYMEX
TYM5 PIT Comdty 10yr T-bill future, expiring in Jun 2014, Day session, traded at CBT
VGZ4 Index Euro Stoxx 50 future, expiring in Dec 2014, traded at Eurex
URU5 Curncy RUB currency future, expiring Dec 2015, traded at RTS
C A ELEC Comdty Corn future, Active contract, Night session, traded at CME
st
NG1 COMB Comdty Natural Gas future, 1 contract month generic, Day&Night session, traded at COT
Most Active A
Jan F Jul N
Feb G Aug Q
Mar H Sep U
Apr J Oct V
May K Nov X
Jun M Dec Z
1. Normal futures
Root Ticker x Month x Year x Session x Yellow Key
CL Z 5 COMB Comdty
2. Most-Active Ticker
Root Ticker x A x Session x Yellow Key
CL A COMB Comdty
4. Equity futures
Root Ticker x = x Month x Year x Exchange x Yellow Key
IBMF = Z 5 GR Equity
Sessions
Many futures have two trading sessions.
PIT = Day Session and ELEC = Night Session. COMB combines both PIT and ELEC. If users need only one Session,
they can designate the Session by replacing COMB with either PIT or ELEC.
Please note that some futures do not have multiple Sessions, and users will not have to specify the Session in the
Ticker code.
EDM4 Jun14
EDN4 Jul14
EDQ4 Aug14
EDU4 Sep14
EDV4 Oct14
EDX4 Nov14
EDZ4 Dec14
EDH5 Mar15
EDM5 Jun15
EDU5 Sep15
EDZ5 Dec15
………
VOD GR 12/16 C200 Equity Vodafone Call 200 option, expiring in Dec 2016, Eurex
Root Ticker x Exchange Code x Expiry MM/DD/YY (or Expiry M/Y only) x C or P x Strike Price x Yellow Key
IBM UO 01/15/16 P 200 Equity
SPZ5C 1865 COMB Index S&P 500 Future Comb session Jun contract Call 1865 option, expiring Dec 2015
ESH5C 1840 Index S&P 500 Mini Future Sep contract Call 1840 option, expiring Mar 2015
JBU4C 145 PIT Comdty Japanese Gov Bond future June contract Call 145 option, expiring Sep 2014
EDZ5C 98.75 Comdty Euro$ Future Dec 2015 contract Call 98.75 option, expiring in Dec 2015
Short Code (2 or 3 letters) x Month x Year x C or P x Strike Price x Session x Yellow Key
SP Z 5 C 1865 COMB Index
Mar H Sep U
Apr J Oct V
May K Nov X
Jun M Dec Z
Swaption Description
BPVEF1 CMPL Curncy GBP Swaption Black vol ATM 6m x 1y
BPSP011 CMPL Curncy GBP Swaption Spot Premium ATM 1yr x 1yr
CL JUL14 25DP VOL BVOL Comdty CLN4 Comdty Implied vol for 25 Delta
IBM US APR14 95 VOL BVOL Equity IBM Apr 14 option 95% moneyness vol
Underlying Ticker + OMON <GO> Option monitor — to find options for an underlying Ticker
*
OSCH <GO> Option search by condition
*
Underlying Ticker + OMST <GO> Most active options by underlying asset
*
MOSO <GO> Most active options by Exchanges
*
OVI <GO> Most active options by volume increase
CTM <GO> Listed spot options (FX, bond, index, non-equity index, weekly
options)
*
CERT <GO> To find listed certificates and warrants
*
WSRC <GO> To find warrants by conditions
*
Underlying Ticker + WMON To find warrants for an underlying Ticker
<GO>
OPDF <GO> Derivatives settings, users can change estimate dividend source, curve ID for interest rates,
etc.
SWDF <GO> Curve and contributor preferences
Each data point is tickerized and stores historical data on the Ticker plant. Users can run functions on each Ticker and
use the Tickers for API. If a user clicks on the values on the screen, the Ticker code will be listed on the top left of the
user’s screen. Alternatively, users can use the Pushpin, which is listed at the top right of the GDCO page (green arrow on
a “piece of paper” icon) and drag and drop the Pushpin onto the spreadsheet to download all Tickers on the page.
Text Format Data (i.e., GPGX page).
For a GPGX page, no history is stored, and no Tickers are associated with the page. If users would like to subscribe to
the page, they will need the GPGX number, which can be found by pressing the Tab key when on the screen—e.g.,
GPGX 0509 012 0001 is the page number. The Subscription string would look like: //blp/pgdata/page/509/12/1
Users can locate contributor pages from the MRKT <GO> function. Please note that some contributor pages are
restricted, and users may not access the page without entitlement. Entitlements are controlled directly by the contributor’s
administrator , therefore, if a user would like to access a specific page that he or she is not able to view, the user would
need to contact the contributor directly. Users can usually find the contact information on the contributor’s page itself or hit
the <HELP> key on the page, then click on Contact Information on Help page.
3.6. FIELDS
Requests and Subscriptions require the user to specify which fields from the Bloomberg data model to receive. Fields are
specified using the field mnemonic. Similar fields are available for Subscriptions and requests; for Subscriptions, the bid
price would be “BID”, for a Request, “PX_BID”.
The first screen when {FLDS <GO>} is run will display FIELD SEARCH.
FLDS <GO> provides the ability to query the API Data Dictionary as well as view static
values for each queried field.
Load “IBM US Equity” on the quote line of the Terminal and execute {FLDS <GO>}.
The security will be displayed in the top-left field, the field below will be empty.
Enter the query string (e.g., enter “pricing fields” and press {<GO>}. The result set is
displayed in the table below that field.
Some of the field mnemonics are displayed in white text. This denotes a real-time
subscription field as opposed to the orange-text fields, which are static-request fields.
Clicking on one of the rows will display that field’s information as well as modify the
values for any override field and allow you to view the values of all related/reactive
fields.
Select “Mid Price (decimal)”. Along the top is displayed that field’s CALCRT number
(PR998), its equivalent mnemonic (PX_DEC_MID) and its description.
Below that section will be displayed: a list of all of the overrides and reactive and
relative (also used with) fields. In this area “what-if” scenarios can be performed by
changing the value of any override field(s) and seeing how such change impacts the value
of the reactive field, which, in this case, is PX_DEC_MID.
A maximum of 20 overrides can be specified in a single Request. The overrides are specified in the Request as an array
of name/value pairs.
4. Subscription Options
Subscriptions are ideal for data that changes frequently and/or at unpredictable intervals. Instead of repeatedly polling for
the current value, the application gets the latest value as soon as it is available without wasting network bandwidth or
system and application resources.
Subscriptions on some services result in an initial starting value for all fields requested followed by a stream of updates as
the values change until the Subscription is explicitly cancelled by the application.
Each Subscription is for a single security. Subscriptions pass Identity objects to get permissioned data. While this is not
required for Desktop API, this is recommended to allow later usage of that code with other products with minimal changes.
Subscriptions can have multiple fields that are specified in a string, for example:
“LAST_PRICE, ASK, BID”
Subscriptions can have options:
interval = x
This will intervalize the Subscription stream by conflating the data to x number of seconds between updates. The
value of x may be specified as a decimal, for example, .5 will update every half second
delayed
This forces a real-time stream to use the delayed steam if available. For Desktop API and Server API, a delayed
stream will be used if not permissioned for the real-time stream.
For additional information, refer to the “Core Developer Guide”.
5. Schema
The Bloomberg API is service-based. Requests, Subscriptions and other functionality are provided by services. The
services provided by Bloomberg L.P. are all in the form “//blp/<servicename>”.
The role of the schema is to define the format of Requests to a service, as well as the Events returned from that service.
Within a service, one or more Event types may exist, each having its own schema. The schema will also define the shape
of the data. For instance, market data is flat, while reference data is nested (like XML).
Each schema element has the following properties and attributes:
▪ Name: The name of the Element.
▪ Status: ACTIVE — Available; INACTIVE — Unavailable
▪ Type: Data type of that Element. This includes SEQUENCE (group), ENUMERATION, BOOL, STRING, etc.
▪ Minimal Occurrence: 0 — Optional; 1 — Required
▪ Maximal Occurrence: 1 — Element; -1 — Array
A schema describes the structure of a service. It provides a list of fields and sub-Messages with their attributes. It defines
the Request details and overrides and may describe the structure of responses.
Data Distribution Management schemas allow client-defined schemas for use in local Publishing and contributions.
Every service has its own schema:
▪ //blp/refdata — Service for reference data
▪ //blp/mktdata — Service for market data
▪ //blp/mktbar — Service for market bar data
For additional information, refer to the “Reference Services and Schemas Guide”.
6.2. DDM
DDM is a managed service that extends beyond traditional industry solutions for market data distribution by providing real-
time/delayed streaming and historical market data, as well as local Publishing, contributions and trusted entitlements. It is
a complete high-volume, low-latency service for end users and applications—it displays throughout an entire financial
firm.
DDM enables clients to publish their own data within their firm or externally to their customers. Published data is
distributed locally to entitled subscribers anywhere within a site. Optionally, the published data can also be simultaneously
sent to a Bloomberg Data Center for storage in managed, high-speed, in-memory caches and persistent databases. This
is known as Contributions. Once data is published into the managed Bloomberg environment, that data is available to
individuals or applications anywhere in the firm as long as the appropriate permissions have been granted.
Bloomberg’s data management and distribution are offered through the Bloomberg Appliance, the same infrastructure that
delivers the Bloomberg B-PIPE data feed. Depending upon which product a client has purchased, various types of
Appliances are available.. Note: no equivalent development instance is available for DDM to be hosted on the customer’s
Linux server as is the case for B-PIPE.
Key features include:
▪ Historical databases with market data history per instrument—an intraday tick-by-tick history may be retained for days
or weeks; or closing prices may be retained for days or weeks; or closing prices may remain available for years.
▪ Bloomberg-provided trusted Entitlements Management & Reporting System (EMRS). Bloomberg data Subscriptions
and publications are protected by strong service-based entitlements.
▪ Distribution for internal use or for select clients.
▪ Low-latency local Publishing.
▪ Launchpad Page Monitor allows client-generated as well as Bloomberg-supplied data to be displayed within a single
Launchpad window on the Bloomberg Professional service.
▪ Intraday tick and historical data storage with access through the Bloomberg Professional service analytics and APIs.
Single-Server API
It is intended for use solely with a single approved registered third-party application (e.g., Sophis, Murex, Front Arena,
etc.). Single-Server API has a data tier of up to 500 securities a month. Only for third-party-approved applications (not for
in-house applications). They MUST be registered with a third party.
Server API
Server API allows Bloomberg Professional service and end-user applications to obtain data from the Bloomberg Data
Center for up to 5,000 securities. Note that Server API cannot be plugged in to black box applications.
Server API Plus
Server API Plus is identical to Server API with the additional option of using EMRS to manage entitlements and BAMS to
monitor hardware and software. It can be installed either on customer hardware or managed on a Bloomberg Appliance.
Server API Premium
High-end version of Server API that allows up to 10,000 unique streaming securities a month and 3m static hits a day.
Managed products have the Server API process residing on the Bloomberg Appliance; unmanaged products have that
process hosted on a dedicated host server. Both Single Server API and Server API are unmanaged products; both the
Server API Plus and Server API Premium products can either be managed or unmanaged.
The Server API allows end-user applications running on a Bloomberg Professional service–licensed PC to obtain data
from the Bloomberg Data Center via a connection to a Server API process. It provides clients with better use of network
resources when compared with the Bloomberg Desktop API, which shares the same libraries. Server API end-users do
not connect to a local BBComm process running on a local PC. Instead, the Server API applications either connect in
Single-User Mode or Multi-User Mode.
7. API Features
7.1. INTERVALIZATION
Intervalization occurs when an application makes an interval-based Subscription for tick data by setting its “interval” option
to a specific value between one-tenth of a second (.10) and 86,400 seconds (24 hours). It is possible to specify an interval
in situations where either the application doesn’t need to receive every single tick or is having trouble processing the
incoming tick data fast enough and falling behind.
All incoming ticks sent from the Bloomberg API infrastructure populate the communication server’s cache and then, at the
“interval” specified, a summary of any of the updated fields since the last summary are sent to the subscribing application.
The Bloomberg communication server is bbcomm for Desktop API, serverapi for Server API and the apics process for B-
PIPE. These are the last hops before the client application.
In Intervalization, the communication server sends SUMMARY/INTERVAL messages at the specified interval. QUOTE or
TRADE market Event–type Messages will never be sent.