How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Bloomberg APIs refdata API

Reference Data Service operations — request/response paradigm

Bloomberg APIs refdata API is one of 12 APIs that Bloomberg APIs publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include refdata. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 6 operations across 6 paths, and defines 20 schemas. It is described by OpenAPI 3.1.0, at version 2.54.

Requests are made against a single base URL, blpapi+session://{session}.

6 operations 6 paths 20 schemas 6 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
2.54
Server
blpapi+session://{session}
Authentication
API Key, API Key, HTTP Bearer
License
Permissive (Bloomberg sample license terms)
Terms of Service
Resource Areas
1

Authentication & Security 3

Bloomberg APIs refdata API declares 3 security schemes for authenticating requests. An API key is passed in the header as X-BLPAPI-Session (desktopAPI). An API key is passed in the header as X-BLPAPI-ASID (serverAPI). It accepts HTTP bearer tokens (BLPAPI-Token) (bpipeToken). By default, every request must be authenticated.

  • desktopAPI — Desktop API authorization is handled by the local Bloomberg Professional terminal. Applications open a session against localhost:8194 and the terminal context…
  • serverAPI — Server API authorization is by ASID and registered IP address. The application's IP must be entitled in the Bloomberg Anywhere permissioning system; an Authori…
  • bpipeToken — B-PIPE applications acquire a token via the AuthorizationTokenRequest operation, then submit the token in an AuthorizationRequest to obtain an Identity object.…

Paths & Operations 6

Across 6 paths, the API surfaces 6 operations — 6 POST. Each is listed below with its method, path, parameters, and response codes.

refdata 6

Reference Data Service operations — request/response paradigm

POST
/refdata/ReferenceDataRequest
Request reference data for one or more securities
referenceDataRequest body → 200
POST
/refdata/HistoricalDataRequest
Request end-of-day historical data over a date range
historicalDataRequest body → 200
POST
/refdata/IntradayTickRequest
Request tick-by-tick history for a single security
intradayTickRequest body → 200
POST
/refdata/IntradayBarRequest
Request intraday bar (OHLCV) history for a single security
intradayBarRequest body → 200
POST
/refdata/PortfolioDataRequest
Request portfolio positions and member data
portfolioDataRequest body → 200
POST
/refdata/BeqsRequest
Request data for a Bloomberg Equity Screening (EQS) screen
beqsRequest body → 200

Schemas 20

The contract defines 20 schemas that model the data the API accepts and returns. The most detailed are HistoricalDataRequest (21 properties), IntradayTickRequest (11 properties), IntradayBarRequest (11 properties), ReferenceDataRequest (7 properties). Each schema is shown below with its type and property counts.

FieldData
object
A single returned (field, value) datum.
1 property
BeqsResponse
HistoricalDataRequest
object
21 properties 3 required
IntradayBarRequest
object
11 properties 5 required
ReferenceDataRequest
object
7 properties 2 required
Field
string
Bloomberg field mnemonic (e.g. PXLAST, LASTPRICE, BID, ASK) or alpha-numeric CALCRT id (e.g. pq005).
IntradayBarResponse
object
3 properties
EidData
object
Entitlement Identifier(s) attached to a security or user.
4 properties
IntradayTickRequest
object
11 properties 4 required
Security
string
Bloomberg security identifier in the form [Topic Prefix]/SYMBOLOGY[@Pricing Source][Exchange] with optional Yellow Key. Default Topic Prefix is ticker. Example…
ReferenceDataResponse
object
2 properties
ErrorInfo
object
Standard error envelope used in BLPAPI responses.
5 properties 4 required
BeqsRequest
object
5 properties 1 required
PortfolioDataResponse
IntradayTickResponse
object
3 properties
HistoricalDataResponse
object
2 properties
PortfolioDataRequest
object
3 properties 2 required
FieldException
object
Indicates a field could not be returned for a security.
2 properties 2 required
SecurityData
object
Per-security data block in a Reference / Historical / BEQS response.
5 properties 1 required
Override
object
A name/value override applied to a derived field calculation.
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

bloomberg-apis-refdata-api-openapi.yml Raw ↑

Other APIs Bloomberg APIs publishes across the network.

Bloomberg Market Data Feed
Bloomberg News API
Bloomberg Data License API
Bloomberg APIs apiauth API
Bloomberg APIs apiflds API
Bloomberg APIs instruments API
Bloomberg APIs mktbar API
Bloomberg APIs mktdata API
Bloomberg APIs mktvwap API
Bloomberg APIs pagedata API
Bloomberg APIs tasvc API
Where this information came from

This is an independent, third-party profile of Bloomberg APIs refdata API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.