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

Bloomberg SFTP Authentication – IP Allowlist and SSH Key Setup

 

Bloomberg SFTP Authentication 

This document explains the Bloomberg SFTP authentication failure observed while connecting through an SFTP client. The error occurred during public key authentication and was further validated from the Bloomberg Enterprise Console monitoring screen.

Error observed:

“Authenticating with public key ‘rsa-key’. Authentication failed.”

The root cause identified was that the connecting public IP was not added to the Bloomberg IP Allowlist.

Authentication log (see session log for details): Using username "<Username>".

Authenticating with public key "rsa-key". Authentication failed.

Step 1: Review the Bloomberg SFTP Monitoring Screen

The Monitoring screen shows the current SFTP connection activity, including uploads, downloads, login attempts, logout activity, and alerts.

In this case, the dashboard shows one critical alert under authentication failure. This confirms that the SFTP connection reached Bloomberg, but the connection was rejected during authentication.

The event displayed is:

“Authentication Failure: IP not in allowlist”

This clearly indicates that the issue is not with the SFTP client alone. The Bloomberg server rejected the request because the source public IP address was not authorized.

Step 2: Validate the Error from the SFTP Client

The SFTP client shows the following error:

“Authenticating with public key rsa-key”

“Authentication failed”

This means the client attempted to authenticate using the configured SSH private key, but Bloomberg rejected the login.

At this stage, the possible causes are:

1. Public IP not allowlisted

2. Incorrect username

3. Public key not mapped to the Bloomberg SFTP user

4. Wrong private key selected in the SFTP client

5. Incorrect SFTP environment, such as UAT instead of PROD

Step 3: Open the Authentication Failure Details

The detailed alert confirms the exact failure reason:

“IP authentication failure”

“Auth Type: IP”

“IP Address: 2.51.115.227”

This confirms that Bloomberg rejected the connection because the source public IP was not added to the SFTP IP allowlist.

Action required:

The same public IP address must be added under the Bloomberg Enterprise Console IP Allowlist section.

Step 4: Add the Public IP Address in Bloomberg IP Allowlist

Navigate to:

Enterprise Console → SFTP → IP Allowlist

Select Internet and enter the public IP address.

Example:

IP Address: 2.51.115.227

CIDR Mask: /32

Host: 1

Alias: Palane_Test

Use /32 when allowing one specific public IP address.

After entering the details, click “Add Internet IP”. Once saved, retry the SFTP connection.

Step 5: Add or Validate the SSH Public Key

Navigate to:

Enterprise Console → SFTP → Credentials → SSH Key

Paste the SSH public key in OpenSSH single-line format.

The key should normally start with:

ssh-rsa

Bloomberg recommends that the SSH key should be at least 2048-bit RSA, preferably 4096-bit. The public key must be in OpenSSH single-line format and mapped to the correct SFTP user.

Important:

Only the public key should be shared or uploaded. The private key must remain secure and should be used only in the SFTP client.

Final Checklist

1. Confirm Bloomberg SFTP username is correct.
2. Confirm SFTP hostname and port are correct.
3. Confirm whether the connection is for UAT or PROD.
4. Confirm the public IP is added in Bloomberg IP Allowlist.
5. Confirm the SSH public key is added in Bloomberg Credentials.
6. Confirm the private key used in the SFTP client matches the uploaded public key.
7. Confirm the key format is OpenSSH single-line format.
8. Retry the connection after saving the IP and SSH key configuration.

Conclusion:

Connect to the SFTP of the bloomberg

Root Cause:

The Bloomberg SFTP connection failed because the source public IP address was not added to the Bloomberg IP Allowlist.

Resolution:

The public IP address was added under Bloomberg Enterprise Console → IP Allowlist with /32 CIDR, and the SSH public key was validated under Credentials.

Bloomberg SFTP Data Extraction: Step-by-Step Guide

 

 Introduction

Learn Bloomberg SFTP file processing data retrieval with a step-by-step guide, request file setup, scheduling, error handling, and TMS integration.”

In enterprise treasury and financial systems, accurate and timely market data is essential for decision-making, reporting, and risk management. Organizations rely on providers like Bloomberg to deliver high-quality financial data.

One of the most reliable methods for batch-based data extraction is Bloomberg SFTP file processing.

This guide explains how to:

• Configure Bloomberg SFTP request files
• Retrieve financial data
• Handle errors and validation
• Integrate with Treasury Management Systems (TMS)

Bloomberg SFTP file processing is a batch data retrieval mechanism where:

1. A request file (.req) is created
2. Uploaded to Bloomberg via SFTP
3. Bloomberg processes the request
4. Output data is generated (.out)
5. Errors (if any) are returned in (.err)

Step 1: Prepare Instrument and Field List

Once you complete the field and instrument list and are ready, then we can use this in two methods to get the data via SFTP or via REST API

Step 2: Download Bloomberg SFTP Request File

• Download the Bloomberg SFTP request file template (.req)
• This file contains:
  • Instrument definitions
  • Field mappings
  • Output configurations

Step 3: Upload Request File to SFTP

• Place the .req file into the Bloomberg SFTP inbound folder
• Once uploaded:
• Bloomberg automatically processes the request
• No manual execution is requried automatically bloomberg reads the foler and request file 

 Step 4: Modify Bloomberg SFTP Request File

Configure Reply File Name

REPLYFILENAME=FXDATA_26042026

Rules:

• Maximum 25 characters
• No special characters
• No spaces or tabs
• Cannot end with .req

Schedule at  12 PM, then add the time and frequency. In our case, we are doing it daily, so for multiple times in daily need to change the time and create multiple files 

Configure Scheduling (Daily Execution)

# Scheduling headers

PROGRAMFLAG=daily

TIME=1200

TIME=1200 → Runs at 12:00 PM

For multiple daily runs:

• Create multiple .req files with different times

Once you place the adhoc file in the SFTP folder, it will get the file 

Adhoc Execution

• Upload .req file → executes immediately
  Useful for testing and one-time data requests

 Step 5: File Processing and Output

After submission:

• Bloomberg processes the request
• Output files are generated

Output Types:

File	Description
.out	Data output file
.err	Error file
.req	Request file

In case of error 

Check the .out file, which talks about the exact error. In this case, we have a reply file name that is more than 25 characters, which is not allowed in the Bloomberg 

#############################################################################

## There were errors detected within the request file. Please correct and

## then resubmit the resulting file.

##

## Source:   dl64961 (ftp)

## Filename: /bb/data/tmp/tmp76tx_56s/dl64961/Palane_SFTP_24062026.req

##

## The following errors were found:

##

## >>REPLYFILENAME=PALANE_TICKERT26042026.bbg<<

##

## Line 7,   E3008: REPLYFILENAME exceeds 25 characters

##

## Reply files names should be ASCII names with the following

## restrictions:

##

## o Cannot contain the following characters -

##

## `  ~  !  @  #  $  %  &  *  (  )  [  ]  ,

## {  }  ;  '  "  >  <  /  ?  |  =

##  

## o Cannot contain ':' or '\' for FTP requests.

##

## o Cannot contain blanks nor tabs.

##

## o Cannot begin with '-' nor '.'.

##

## o Cannot end on '.req' nor 'req.enc'.

##

## o Not exceed 25 characters in length for FTP requests or 12

##   characters for SEND requests.

##

## REPLYFILENAME is optional. For FTP request the default is <request>.out,

## where request is the request filename less the ".req" extension.

## For SEND requests the default is "reply.txt"

##

#############################################################################

## There was 1 error encountered within the request file.

## The request file has been moved to PALANE_TICKERT26042026.bbg.err

##

## Make sure no unprintable characters, such as tabs are present in the

## definitions and all the required statements (eg. 'START-OF-DATA'

## are present.

##

## Please consult the "Per Security Product Manual" for more information on

## the request file structure and program options, plus the periodic

## "Data Service Enhancement Notice(s)" about interface changes.

Process Flow:

1. Request file created (.req)
2. Uploaded via SFTP
3. Bloomberg processes request
4. Output generated (.out)
5. Errors captured (.err)
6. TMS reads output file

Best Practices for Enterprise Implementation

• Use standard naming conventions
• Maintain separate environments (DEV / UAT / PROD)
• Monitor .err files proactively
• Align schedules with treasury cut-off timings
• Validate data before production deployment 

Conclusion

Bloomberg SFTP file processing provides a reliable, scalable, and automated solution for financial data retrieval.

By implementing structured request files and proper validation:

• Data accuracy improves
• Manual effort reduces
• Integration with TMS and ERP becomes seamless 

#bloomberg sftp  #bloomberg data extraction  #financial data automation  #Treasury System Integration

#Bloomberg req file #sftp data processing