Bloomberg Data License Per Security

Prev Next

FINBOURNE’s Bloomberg Data License Per Security (BBG DLPS) integration allows you to select the Bloomberg content you need to meet your business priorities, and schedule delivery into LUSID.

Bloomberg Data License Per Security is one of Bloomberg’s enterprise Data License products, allowing requests for individual securities on a pay-per-use model across:

  • Reference

  • ESG

  • Pricing

  • Risk

  • Regulation

  • Fundamentals

  • Estimates

  • Historical data

More information on Bloomberg Data License.

Prerequisites

Before getting started, ensure you have:

Supported data types and methods

Instrument enrichment

You can use the Integrations dashboard to enrich existing LUSID instruments with the data points you need, including groups of data points such as shareholding disclosure. Keep reading this article to learn more.

Entities and instrument creation

You can use our suite of Luminesce providers to build bespoke data import requests, which you can schedule or run on demand. Read more.

Setting up the integration

Step 1: Obtain Bloomberg application credentials

First, you must create an application in the Bloomberg Enterprise Console to get your credentials for LUSID:

  1. Sign in to your Bloomberg Enterprise Console portal.

  2. Navigate to Connectivity > WEB API > Monitor and manage.

  3. Select Create new application.

  4. Specify the following values for the application:

    • Product: DATA LICENSE

    • Product ID: Your Bloomberg account number

    • Application Name: LUSID

  5. Create the application and securely store the generated credentials. Note the client_id and client_secret values - you’ll need to provide these in LUSID.

  6. Add the Allowed IPs provided by your FINBOURNE representative.

Step 2: Create an integration instance

An integration instance is a configuration of data points to import from Bloomberg.

  1. Navigate to Integrations > Dashboard.

  2. Select Create instance.

  3. Specify the following:

    • Name: A friendly name for this integration instance

    • Description: A detailed description of the instance

    • Client Id and Client Secret: Your Bloomberg credentials retrieved in step 1

    • Download Drive File Path: Optional; a path starting with LUSID-Horizon to download data import troubleshooting files in

    • Use AdHoc Mode:

      • Leave the box unticked to have Bloomberg execute your request in One Shot mode (batch processing with a 15 minute delay). This option can help to manage Bloomberg costs; read more.

      • Tick the box to have Bloomberg execute your request in AdHoc mode (immediately when Bloomberg receives your request)

    • Create Legal Entities:

      • Tick the box if you want to create legal entities in LUSID using mappings from certain pairs of Bloomberg fields; read more.

    • Scopes of Interest: The instrument scopes LUSID should use to look for instruments with the Instrument/LUSIDConfig-Bloomberg-DLPerSecurity/RefreshReferenceData property; read more.

    • Optionally, Bloomberg Professional Services users can complete the following fields to link your Bloomberg Terminal personal defaults:

      • User Number: You can locate this (and the following fields) by running IAM<GO> in Bloomberg Terminal

      • Serial Number: The number to the left of - within the S/N. For example, <Serial Number>-<Work Station>

      • Work Station: The number to the right of - within the S/N

      • Price Source: Optionally, a pricing source to apply to all instruments in the request, for example BGN, EXCH, or CMPN

  4. Click Edit imported properties > Add properties and select which Bloomberg data fields to import.

    Note

    You can select the View imported fields button and inspect the Source Fields and Transformation Description columns to see how LUSID maps your data.

  5. Click Save to create the integration instance. Note the Instance ID, which you need for the next step.

Step 3: Select the instruments to import data for

LUSID selects instruments to import Bloomberg data for using the Instrument/LUSIDConfig-Bloomberg-DLPerSecurity/RefreshReferenceData property.

  1. Ensure your instruments have at least one of the following identifiers:

    • BloombergUniqueId (recommended, ensures result is unambiguous)

    • Figi

    • Cusip

    • Sedol

    • Isin

    • Ticker (must include the Bloomberg yellow key suffix, for example VOD LN Equity)

    Note: All of the above identifier types have a three-stage key beginning with Instrument/default/<identifier-type>, for example Instrument/default/BloombergUniqueId.

  2. Follow these steps to add the instrument property with Scope LUSIDConfig-Bloomberg-DLPerSecurity and Code RefreshReferenceData to one or more instruments you want to include in the Bloomberg integration instance import.

  3. Set the property value to your integration Instance ID from step 2. You can enter more than one ID if you want to include the instrument in multiple integration instances.

Running the integration

See how to run an integration instance.

Monitoring and troubleshooting integration runs

See how to monitor integrations and troubleshoot general issues.

Note

The Bloomberg integration utilises the Bloomberg once/snapshot trigger type, so runs take a minimum of 15 minutes to complete.

LUSID adds Bloomberg data to instruments as properties in the LUSID-Bloomberg-DLPerSecurity scope. The Instrument/LUSID-Bloomberg-DLPerSecurity/BBG_Retrieval_Date property tells you when data was last extracted for each instrument.

Monitoring run details

The Log ID data in the below screen-shot has the following usage for monitoring purposes.

  • 1: You can enter the Source Primary ID Value within Insights > Request Logs to view the request made to LUSID to locate instruments to include for the run, and LUSID’s response.

  • 2 or 3: Details the LUSID instruments included in this integration run and the identifier used to locate the data in BBG DLPS.

  • 4: You can use the Source Primary ID Value to view the request within the Bloomberg Data Portal at https://data.bloomberg.com/per-security/<Bloomberg Account ID>/requests/<Source Primary ID Value>. You can expand the row to view details of the response file from Bloomberg; LUSID saves this file to your specified Download Drive File Path.

  • 5or 6: Details the data mapping between each instrument identifier in the Bloomberg response and the updated LUSID instrument.


Troubleshooting

Error: Unauthorized

UnexpectedException
Failed when calling Bloomberg HAPI   
Uri          : https://api.bloomberg.com/eap/catalogs/
Errored with : Unauthorized
Details : {"errors":[{...
                      "errorCode":"unauthorized-client",
                      "status":401,
                      "detail":"Invalid IP, IP 123.12.123.12 not whitelisted"}],
                      "error":"unauthorized_client"}

If you experience this error, check that the IP listed in the detail has been added to the authorised set in step 1.

Error: Forbidden

UnexpectedException
Failed when calling Bloomberg HAPI   
Uri          : https://api.bloomberg.com/eap/catalogs/
Errored with : Forbidden
Details      : {"error_description":"Error verifying JWT signature.",
                "error":"access_denied",
                "errors":[{"title":"access_denied",
                           "detail":"Error verifying JWT signature.",
                           "meta":{"server-time":1757436416},
                           "errorCode":"forbidden",
                           "id":"2c9da3aa-390e-87b3-63a6-b261313587f3",
                           "status":403}]}

If you experience this error, check the values you’ve entered for your Bloomberg credentials in step 2.

Final Status: ResourceFailed Description: Unable to process row

Bloomberg provides a Return Code (RC) to LUSID in each response:

  • A value of 0 represents a success

  • A non-zero value sets the Final Status column to ResourceFailed

For such errors, view the logs Description column to see the RC code and a description, if known, of the related error.

Final Status: PayloadExtracted Description: Extracted 0 record(s) from LUSID.

If you experience this error, check the following:

No Bloomberg data imported for instruments

Check the following:

  • Your connection to Bloomberg is working

  • Instruments are configured correctly. See troubleshooting, “PayloadExtracted : Extracted 0 record(s) from LUSID”.

  • The integration instance is configured to import the relevant fields

  • A minimum of 15 mins have elapsed since the integration instance was triggered

Appendix A: Usage and cost management

Usage costs incurred from Bloomberg can depend on a variety of factors. LUSID’s BBG DLPS integration can help you to manage your usage costs by:

  • Processing your requests in cost-effective batches

  • Allowing you to:

    • Create different integration instances for different update frequencies, such as static reference data versus intraday pricing

    • Choose which instruments or commercial categories you want to receive data for

    • Select and import only the data fields you want

Contact your Bloomberg account representative for more details on your usage.

Appendix B: Legal entity field mapping

LUSID uses the following Bloomberg field mappings to create legal entities:

Legal entity type

Legal entity name

Unique identifier

Issuer

LONG_COMP_NAME

ID_BB_COMPANY

Parent company

LONG_PARENT_COMP_NAME

ID_BB_PARENT_CO

Ultimate parent company

ID_BB_ULTIMATE_PARENT_CO_NAME

ID_BB_ULTIMATE_PARENT_CO

Guarantor company

GUARANTOR_NAME

ID_BB_GUARANTOR

Ultimate CAST (capital structure) parent

CAST_PARENT_NAME

CAST_PARENT_ID

Obligor

OBLIGOR_NAME

OBLIGOR_BID

Parent obligor

PARENT_OBLIGOR_NAME

PARENT_OBLIGOR_ID

Ultimate obliger

ULTIMATE_OBLIGOR_NAME

ULTIMATE_OBLIGOR_ID

Note

You must specifically request the relevant pair of Bloomberg fields for LUSID to successfully create a legal entity.

For example, if you want to ensure LUSID creates a legal entity for an instrument issuer, you must include LONG_COMP_NAME and ID_BB_COMPANY in your Imported properties. Note that ID_BB_COMPANY is a mandatory property that LUSID includes in imports by default.