Thursday, April 23, 2026

Bloomberg Data License: Step-by-Step Guide to Create Schedule Requests & Fetch Market Data

 


Introduction

In this blog post, we discuss why accessing reliable, timely market data is critical for treasury operations, ERP integrations, and analytics. The Bloomberg Data License (DLGO) enables organizations to automate the extraction of financial data, including FX rates, interest rates, and corporate information.

In this blog, we will walk through the end-to-end process of creating a schedule request in Bloomberg Data License, including instrument selection, field configuration, and automated data retrieval.

The Bloomberg Data License allows organizations to request, schedule, and automate the delivery of financial data, such as FX rates, pricing, and reference data, directly into enterprise systems. It supports delivery via API, SFTP, and cloud platforms, enabling scalable data integration across treasury and ERP systems.

Prerequsit 

Before starting, ensure the following:

  • Access to Bloomberg Data License (DLGO)
  • Required user permissions
  • List of required instruments (FX pairs, indices, etc.)
  • Defined business requirement (real-time, historical, or snapshot data)

Real-World Integration Use Case

  • Treasury Management System (TMS)
  • Oracle Fusion ERP
  • Risk & reporting platforms

Example:

In enterprise environments, Bloomberg Data License is commonly integrated with Treasury Management Systems (TMS) and ERP platforms to automate FX rate updates, valuation, and financial reporting.

Overall process flow for Bloomberg Data go 

Instrument List + Field List → Schedule → Data Output → Integration 

Step-by-Step Process

Step 1: Log in to the Bloomberg Data GO, Choose the Data license Per Security 




Step 2: Choose the DataLicense per security. You will land on this page to choose the instrument and the field list with the data fetching mechanism  




We need to choose the appropriate data-fetching mechanism to retrieve the data. Please refer to the table below and fetch the data accordingly 
    

Option

Technical Name

Meaning

Current Data

getData

Latest available value

Historical Data

getHistory

Past time-series

Tick History

getTickHistory

Tick-level trades

Pricing Snapshot

getSnap

Point-in-time valuation

Corporate Actions

getActions

Dividends, splits

Entity Data

getCompany

Company info



Step 3: Create the Instrument List 
Go to the Instrument list and select the tickers to fetch for the integration. We need to create two different lists: the instrument list and the field list. Please click the button to create a new list







 
Once you define the tickers, you can download them as an Excel file and verify the data. We had created the two tickers for our exercise. You can create as much as you can, as per the business requirement 







Step 4: Filed List 

getData → Daily FX rates / real-time pricing

getHistory → Yield curves / historical trends

getTickHistory → Trade analytics

getSnap → End-of-day valuation 


Add the related fields  to fetch the data 


Add the related files that we require to have the data, based on the business requirement


Once the file list is added, we are now ready to create the 

Step 5: Creation of the Schedule 



Select the Load from the saved list, as we had saved the list 



Add the field list, and if required, add new fields also 


Add the Instrument list 



Create the schedule via ad hoc or schedule 






With this, we complete the process of running the request and fetching the necessary tickers from the Bloomberg 

Target data flow 

Bloomberg Data License → Scheduled Delivery (SFTP/API) → TMS

Conclusion 

By implementing Bloomberg Data License scheduling, organizations can automate market data extraction, reduce manual effort, and ensure accurate and timely data availability for financial operations.

#Bloomberg Data License #Market Data Integration Schedule Request #Tickers and Fields #Treasury Systems #ERP Integration

No comments:

Post a Comment