Logo

Data Adapter - 3rd Party data providers


Data Adapter provides a service for clients wanting to save time implementing FundApps. Data Adapter takes a basic CSV of a client's positions, connects to 3rd party market data providers and maps the data back from them, directly into the FundApps specification for Shareholding Disclosure, Sensitive Industries and Position Limits

In order to provide the Data Adapter service we require clients choose a data vendor to source data from. Currently we support the below interfaces

FundApps has mappings for both services and are agnostic to the choice of vendor a client makes. Be aware that both vendors may have gaps in individual fields and asset class coverage. We have documented the most commonly known or broad asset class coverage in each of the Data Adapter specification pages for Shareholding Disclosure and Position Limits

LSEG - Data Scope Select

Data Adapter connects directly to LSEG's Data Scope Select product via REST API. We use the composite extraction template request located on the ExtractWithNotes endpoint. We request a static list of fields for each call and batch requests based on LSEG's recommendations.

The LSEG DSS interface supports looking up instruments via:

Bloomberg - Data Licence / Data Licence+

Data Adapter connects directly to Bloomberg's Data Licence Web Services (DLWS) interface, using the SOAP API via the submitGetDataRequest endpoint. Two modes are supported:

Both modes cover the same core Data Adapter functionality. The differences are summarised in the feature comparison table further down.

How Data Adapter calls Bloomberg (Asset Class Strategy)

To keep licensing usage efficient and avoid pulling fields that are not needed for a given instrument, Data Adapter uses an Asset Class Strategy:

  1. A small core set of Bloomberg packages is called first. The fields returned in this initial call are enough to determine each instrument's asset class.
  2. Once the asset class is known, Data Adapter then requests only the additional packages that are relevant to that class for the remaining fields.

The full set of packages Data Adapter can call is listed below. Packages marked with * are optional and can be switched off per tenant.

The table below indicates which Bloomberg packages Data Adapter may call for each asset class under the Asset Class Strategy. Packages marked with * are optional and can be switched off.
Note switching them off can cause some missing data or the use of less optimal fields.
For example, Pricing Intraday applies to all asset classes as it provides price data, though many clients choose to supply price in the input file, removing the need to call it from the vendor.

Asset Type Open Source Security Master Packaged Derived - Intraday* Derived - End of Day* Fundamentals* Pricing - Intraday* Pricing - End of Day*
Equity
(inc Closed Ended Funds/CEFs)		 ✔ ✔ ✔ x x ✔ ✔ x
ADR ✔ ✔ ✔ x x ✔ ✔ x
Preferred Equity ✔ ✔ ✔ x ✔ ✔ ✔ x
Units
(inc ETFs + open-ended funds)		 ✔ ✔ ✔ x x ✔ ✔ x
Rights ✔ ✔ ✔ x x x ✔ x
Warrants ✔ ✔ ✔ ✔ x x ✔ x
Convertible Bonds ✔ ✔ ✔ ✔ x x ✔ x
Government Bonds ✔ ✔ ✔ ✔ x x ✔ x
Single Name Equity Futures ✔ ✔ ✔ x ✔ x ✔ ✔
Single Name Equity Option ✔ ✔ ✔ ✔ ✔ x ✔ ✔
Index Derivatives ✔ ✔ ✔ ✔ ✔ x ✔ ✔
OTC Instruments x x x x x x x x


Feature comparison: DL vs DL+

The following capabilities are available today when Data Adapter calls Bloomberg. Both DL and DL+ support the same core behaviour, the only differences today are around identifier fallbacks.

Feature DL DL+ What it means
Asset Class optimisation ✔ ✔ A core set of packages is called first to detect each instrument's asset class; only the packages relevant to that class are then called for the remaining fields.
Asset class override ✔ ✔ Clients can force a specific asset class for an instrument when Bloomberg's classification is not what is needed.
Underlying asset class override ✔ ✔ Same as above, but applied to the underlying instrument of a derivative.
Turn off individual packages ✔ ✔ Optional Bloomberg packages can be disabled per tenant to control cost or data usage. The same configuration works identically in both modes.
Ad-hoc requests ✔ ✔ Requests can be sent as oneshot (default) or adhoc. Both modes check for this identically.
Primary identifier strategy ✔ ✔ Instruments are looked up using the primary identifier supplied in the input file (ISIN, SEDOL, CUSIP or Bloomberg ticker + yellowkey).
Secondary identifier fallback ✔ ✖ If the primary identifier lookup returns no data, Data Adapter can retry with a second identifier. Not currently available on DL+.
Tertiary identifier fallback ✔ ✖ A further fallback to a third identifier if both the primary and secondary lookups fail. Not currently available on DL+.

The Bloomberg Data Licence Web Services interface supports looking up instruments via: