Bloomberg

Bloomberg EMSX

Provider ID74

Bloomberg EMSX order execution on Obermind Stream. Route equities and ETFs, futures and options to EMSX brokers through the Bloomberg Server API or a logged-on Terminal, with a broker and account per asset class, broker algorithms read from Bloomberg, and prices from another provider in the deployment.

  • Equities
  • Equity Derivatives
  • ETF
  • Futures
  • Integrations
  • OMS / EMS
  • Options
  • Order Execution

Overview

Obermind Stream connects to Bloomberg EMSX as an execution venue.

  • Orders are created and routed with CreateOrderAndRouteEx and cancelled with CancelRoute.
  • Fills, broker rejects and cancels arrive on the EMSX order and route subscriptions.

Three EMSX asset classes are supported: equities (EQTY, including ETFs), futures (FUT) and options (OPT). Each class has its own broker, account and hand instruction.

The provider reads the brokers and broker strategies Bloomberg enabled for each class, so traders and administrators can only pick what the broker actually offers.

Markets

The instrument type in the Obermind catalogue decides the EMSX asset class:

  • Equities (EQTY): instrument types Stock, ETF and Index.
  • Futures (FUT): instrument type Future.
  • Options (OPT): instrument type Option, covering equity options, index options and options on futures.

Each class has one broker, account and hand instruction. Any other instrument type (FX, crypto, CFDs, bonds) is rejected with "Instrument type … is not supported for this venue".

The sections below cover each class: ticker, side, quantity, broker and what to configure.

  • Equities
  • ETFs
  • Indices
  • Futures
  • Options

Order Types

  • Market (EMSX_ORDER_TYPE MKT) and Limit (LMT) go to EMSX. Quantity is a whole number.
  • Stop and Stop Limit are held on the platform and released as market orders through the Aggregator's synthetic order types.
  • Modify is not supported: cancel and send a new order.
  • Market Order
  • Limit Order
  • Stop Order (synthetic)
  • Stop Limit Order (synthetic)
  • Broker Algorithms

Time in Force

Day only. Set the Aggregator's VenueTimeInForce so any other value is rewritten to Day before the order is sent.

  • DAY

Real-time Market Data

Server API mode has no market data entitlement. Prices then come from another provider (see Prices from another provider).

  • Top Of Book (Terminal mode)
  • Trades (Terminal mode)

Historical Market Data

  • Intraday Bars (Terminal mode)
  • Intraday Ticks (Terminal mode)

Connectivity

Terminal mode (ServerAPI false, the default):

  • Connects to a Bloomberg Terminal logged on to the same machine at localhost:8194.
  • Has market data, intraday history and EMSX.
  • Orders show on that user's blotter.

Server API mode (ServerAPI true):

  • Connects to a Bloomberg Server API instance.
  • Authorizes every request with a non-BPS UUID and the IP address Bloomberg registered for the Obermind Stream host.
  • Has no market data entitlement: it carries orders, fills and the strategy catalogue only.
  • Orders from a non-BPS UUID do not appear on a trader blotter unless Bloomberg adds the UUID to the desk's Teamview.
  • Terminal (Desktop API)
  • Server API (SAPI)

Obermind Platform is integrated with the Bloomberg EMSX API.

Equities and ETFs (EQTY)

Stock, ETF and Index instruments are sent as EQTY.

  • Ticker: the instrument's alternative id on the Bloomberg provider, written exactly as the Terminal shows it, with the market code and the yellow key. Examples: AAPL US Equity, VOD LN Equity, SPY US Equity for an ETF.
  • Side: BUY or SELL.
  • Quantity: a whole number of shares.
  • Broker: set EQTY in BrokersStr to a broker Bloomberg enabled for equities, and give that broker its account in AccountsStr.
  • Broker strategies: an equity order offers that broker's EQTY strategies, for example VWAP or DMA.
<property name="BrokersStr" null="false">{"EQTY":"BRKA","FUT":"","OPT":""}</property>
<property name="AccountsStr" null="false">{"BRKA":"ACC-0001"}</property>

Futures (FUT)

Instruments of type Future are sent as FUT.

Use the ticker of the specific contract month with its yellow key, as the Terminal shows it:

  • ESZ6 Index: December 2026 E-mini S&P 500.
  • CLF7 Comdty: January 2027 WTI crude oil.
  • TYH7 Comdty: March 2027 10-year Treasury note.
  • ECZ6 Curncy: December 2026 euro FX future.

Generic tickers such as ES1 Index roll on their own and are not order tickers. At each roll, add the next contract as an instrument (or change the alternative id) before trading it.

  • Quantity: a whole number of contracts.
  • Broker: futures need their own broker. Set FUT in BrokersStr to a broker Bloomberg enabled for futures (often not the equity broker), with its account in AccountsStr. Leave FUT empty until Bloomberg enables a futures broker on the connection.
  • Side: buy or sell to open or to close, worked out from the account's position (see Open and close side).
<property name="BrokersStr" null="false">{"EQTY":"BRKA","FUT":"BRKF","OPT":""}</property>
<property name="AccountsStr" null="false">{"BRKA":"ACC-0001","BRKF":"ACC-0002"}</property>

Options (OPT)

Instruments of type Option are sent as OPT. The type is set when the instrument is created, so create options as Option from the start.

The ticker is the full Bloomberg option ticker with underlying, expiry, put or call, strike and yellow key, copied from the Terminal security lookup:

  • AAPL US 12/18/26 C200 Equity: equity option.
  • SPX US 12/18/26 P5000 Index: index option.
  • ESZ6C 5000 Index: option on a future.
  • Quantity: a whole number of contracts.
  • Broker: set OPT in BrokersStr to a broker Bloomberg enabled for options, with its account in AccountsStr, and OPT in HandInstructionsStr if the broker asks for something other than ANY.
  • Side: buy or sell to open or to close, from the account's position.
  • Broker strategies: an option order offers the broker's OPT strategies only.
  • Server API mode: each option also needs an alternative id on the price provider, or it has no price.
<property name="BrokersStr" null="false">{"EQTY":"BRKA","FUT":"BRKF","OPT":"BRKO"}</property>
<property name="AccountsStr" null="false">{"BRKA":"ACC-0001","BRKF":"ACC-0002","BRKO":"ACC-0003"}</property>
<property name="HandInstructionsStr" null="false">{"EQTY":"ANY","FUT":"ANY","OPT":"ANY"}</property>

Open and close side (futures and options)

EMSX takes an opening or closing side on futures and options. The platform order is a plain buy or sell, so the provider decides from the account's current position on that instrument when the order is sent. Equities always send BUY or SELL.

  • Buy with a short position: B/C (buy to close)
  • Buy with no short position: B/O (buy to open)
  • Sell with a long position: S/C (sell to close)
  • Sell with no long position: S/O (sell to open)

Instruments and AltIds

Orders go to EMSX with the Bloomberg ticker held in the instrument's AltId on provider 74. The instrument type decides the asset class (see Markets).

The AltId fields:

  • Provider: 74.
  • Symbol: the Bloomberg ticker exactly as the Terminal shows it, with the market code and the yellow key, for example AAPL US Equity.
  • Exchange: leave empty. It is not sent to Bloomberg.
  • Alt currency: the instrument currency. It is not sent to Bloomberg.

In Server API mode the instrument also keeps its AltId on the price provider: prices come from that provider and orders go to Bloomberg (see Prices from another provider).

Examples:

InstrumentTypeSymbolExchangeAlt currency
AAPLStockAAPL US Equity(empty)USD
MSFTStockMSFT US Equity(empty)USD
SPYETFSPY US Equity(empty)USD
ESZ6FutureESZ6 Index(empty)USD
AAPL 18 Dec 2026 200 callOptionAAPL US 12/18/26 C200 Equity(empty)USD

Adding AltIds in Dash

EMSX has no instrument download and no order status request, so the instruments come from your price provider:

  1. 1.Create or import them on the price provider (Obermind Dash, Data Manager, Import Instruments) with the right instrument type: Stock or ETF, Future, or Option.
  2. 2.In Obermind Dash, open Instruments, select the instrument and press Update.
  3. 3.Under Alternative IDs, press Add AltId, choose provider 74 under Provider, and enter the Bloomberg ticker in Symbol.
  4. 4.Press Save.

With several instruments selected, editing Alternative IDs replaces the list on all of them. Add AltIds one instrument at a time.

What to request from Bloomberg

Bloomberg provisions the Server API instances, the identities and the broker setup. Request all of these before installing.

  • Server API: up to two instances, usually one UAT and one PROD. Both are production grade
  • Two non-BPS UUIDs (UAT and PROD), each tied to the IP address Bloomberg sees for the Obermind Stream host
  • EMSX broker code setup per asset class (EQTY, FUT, OPT) with the exchanges you need, an administrator UUID and an order owner UUID
  • Algo setup for each broker, or the strategy lists come back empty
  • The broker account (FIX tag 1) for each broker, agreed with that broker
  • Optional: the non-BPS UUIDs added to the trading desk's Teamview

Install the Bloomberg Server API

  1. 1.Sign in to the Bloomberg developer portal (or run BDEV <GO> on a Terminal: Products, Trading API Products, EMSX API Developer's Guide, Trading API Server) and download the current API deployed installer and the SDK.
  2. 2.Install on the server that will host the instance: Windows, or Linux with kernel 3.10 or later (Red Hat 8 or later). Place it close to Bloomberg's data centre for your region, on the network path Bloomberg specifies (for example leased lines).
  3. 3.Run the installer and follow the prompts. It ends with a registration key.
  4. 4.Send the key to Bloomberg. They configure the instance on their side. Repeat for the second instance.
  5. 5.Start the Server API. It can run in a console window for testing or as a service.
  6. 6.Allow the Obermind Stream host to reach the Server API port, 8194 by default. When Obermind Stream runs on the same machine, ServerHost is localhost.

How a broker is chosen

Each order goes to one EMSX broker, the first of the three below.

  • Once Bloomberg has listed the brokers for the order's asset class, the broker must be one of them. Otherwise the order is rejected with "Broker … is not enabled for … orders on this connection".
  • A class with no broker set and no broker on the order is rejected with "No broker is configured for … orders".
  • The algorithm's broker, when the order uses a broker strategy
  • The broker chosen on the order ticket in Obermind Flow
  • BrokersStr for the instrument's asset class

Brokers and accounts

  • BrokersStr is a JSON object with the keys EQTY, FUT and OPT, each set to an EMSX broker code or left empty. Only select a broker that Bloomberg enabled for that class; leave a class empty until it is enabled.
  • AccountsStr maps each broker code to its account, sent as EMSX_ACCOUNT (FIX tag 1), up to 29 characters.
  • DefaultAccount is used for a broker with no entry in AccountsStr.

The broker's default account in FNAB <GO> only fills the Terminal drop-down and is not applied to API orders. A missing account is often rejected by the broker as an unknown client.

With RequireAccount on (the default), Server API orders with no account are rejected by Obermind before they are sent.

<property name="BrokersStr" null="false">{"EQTY":"BRKA","FUT":"BRKF","OPT":"BRKO"}</property>
<property name="AccountsStr" null="false">{"BRKA":"ACC-0001","BRKF":"ACC-0002","BRKO":"ACC-0003"}</property>
<property name="DefaultAccount" null="false">ACC-0001</property>
<property name="RequireAccount" null="false">True</property>

Hand instructions

HandInstructionsStr sets EMSX_HAND_INSTRUCTION per asset class: ANY, AUTO, DOT or MAN.

  • ANY leaves the choice to the broker and is the default for every class.
  • Use the value each broker asked for.
  • A class with no value is rejected with "No hand instruction is configured for … orders".

<property name="HandInstructionsStr" null="false">{"EQTY":"ANY","FUT":"ANY","OPT":"MAN"}</property>

Broker algorithms

When EMSX opens, the provider calls GetBrokersWithAssetClass, GetBrokerStrategiesWithAssetClass and GetBrokerStrategyInfoWithAssetClass for EQTY, FUT and OPT. It keeps each broker's strategies with their parameters in Bloomberg's order.

A strategy belongs to one class and one broker, so an option order only sees the brokers' OPT strategies.

How parameters are sent:

  • Parameters are positional: every order sends one strategy field and one indicator per parameter, with the value when it is set and the broker default otherwise.
  • Bloomberg returns parameter names only, so the broker validates the values.
  • An order with no strategy is sent with strategy NONE.

In the Obermind web and mobile apps the picker appears on the trade ticket when:

  • the platform switch Provider algos enabled is on;
  • the account's configuration group has Provider Algos Enabled set to true;
  • the account routes to a venue that offers algorithms.

Administrators can pick an algorithm on the Dash order ticket. Algorithm orders accept Market and Limit, are Day only, go only to the algorithm's venue and cannot be modified.

Fills, rejects and cancels

A broker can reject a route after EMSX accepted the order:

  • The route subscription reports EMSX_STATUS REJECTED.
  • The reject reason is EMSX_BROKER_NOTES, the broker's FIX tag 58 text. Obermind rejects the order with that text.
  • EMSX_NOTES is the instruction sent to the broker, not the reason.

A cancel made on the Terminal or by the broker cancels the order on the platform. After a reconnect the initial paint reconciles working orders without repeating fills.

Prices from another provider

Server API mode publishes no prices, for any asset class. Give each instrument two alternative ids, one on the price provider and one on the Bloomberg provider, and set the Aggregator properties below on ObermindStream.ObermindSTREAMSettings.

  • VenuePriceSources takes the price provider's quotes (88 here) and tags them as provider 74, so best price routes to Bloomberg.
  • Futures and options need a price provider that carries them too.
  • Internaliser must be false, or orders execute on the platform's own book.
  • SyntheticOrderProviders keeps Stop and Stop Limit on the platform and releases them as market orders.
  • VenueTimeInForce replaces the built-in rules for every venue once set, so list your other venues in it too, for example 74:Day:Day;88:GTC,IOC,GTD.

The pairing is decided per instrument, from the alternative ids it carries:

  • Both ids: priced from the price provider, executed on Bloomberg only. The price provider is not quoted or routed to separately on that instrument.
  • Bloomberg id only: no price, because the Server API has no feed of its own.
  • Price provider id only: no price and orders are rejected, unless the price provider is also in LiquidityProviders.

To trade the instruments Bloomberg does not list on the price provider instead, add it to LiquidityProviders too, for example LiquidityProviders 74,88 with VenuePriceSources 74:88. Those instruments are then priced and executed on 88, and instruments with both ids still execute on Bloomberg only. Another liquidity provider that lists the same instrument still competes on price.

<Property name="Internaliser">False</Property>
<Property name="LiquidityProviders">74</Property>
<Property name="VenuePriceSources">74:88</Property>
<Property name="SyntheticOrderProviders">74:Market,Limit</Property>
<Property name="VenueTimeInForce">74:Day:Day</Property>

Assembly registration

Register the provider in Obermind Stream Configuration (OberMind.Configurations.Configuration), then restart Obermind Stream.

  • Id 0 uses the id from the class, which is 74.
  • Only include this provider's assembly block.
  • The Bloomberg API libraries ship with Obermind Stream.
<Provider>
  <TypeName>OberMind.BBG.API.Bloomberg, OberMind.BBG</TypeName>
  <Id>0</Id>
  <X64>true</X64>
</Provider>

Stream provider XML

Paste this provider element into OberMind.XmlProviderManagerSettings. Once the type is loaded, Obermind Dash, Providers, Configuration edits the same element, and the info icon next to the provider lists every setting with its current value.

The sample is Server API against the PROD service, with a broker and account for each of equities, futures and options.

  • Replace the host, the UUIDs, the IP addresses, the brokers and the accounts with the values Bloomberg and your brokers issued.
  • Leave FUT or OPT empty in BrokersStr until Bloomberg enables a broker for that class.
  • UsersStr lists the identities; the first enabled one is used.
  • LogPath must be a folder the Obermind Stream service can write.
  • Keep SUBSCRIPTION_DATA logging off in production.
<provider>
  <id>74</id>
  <instance>1</instance>
  <properties>
    <property name="IsServerAPI" null="false">True</property>
    <property name="ServerHost" null="false">198.51.100.20</property>
    <property name="ServerPort" null="false">8194</property>
    <property name="IsUAT" null="false">False</property>
    <property name="UsersStr" null="false">[{"Enabled":true,"UUID":"10000001","Description":"PROD","IPAddress":"203.0.113.10"},{"Enabled":false,"UUID":"10000002","Description":"UAT","IPAddress":"127.0.0.1"}]</property>
    <property name="DefaultAccount" null="false">ACC-0001</property>
    <property name="AccountsStr" null="false">{"BRKA":"ACC-0001","BRKF":"ACC-0002","BRKO":"ACC-0003"}</property>
    <property name="RequireAccount" null="false">True</property>
    <property name="BrokersStr" null="false">{"EQTY":"BRKA","FUT":"BRKF","OPT":"BRKO"}</property>
    <property name="HandInstructionsStr" null="false">{"EQTY":"ANY","FUT":"ANY","OPT":"ANY"}</property>
    <property name="LoggingEnabled" null="false">True</property>
    <property name="LogPath" null="false">C:\ObermindPlatform\logs\bloomberg\</property>
    <property name="LogEventsStr" null="false">{"SUBSCRIPTION_DATA":false}</property>
    <property name="Enabled" null="false">True</property>
    <property name="AutoReconnect" null="false">True</property>
    <property name="AutoReconnectInterval" null="false">10</property>
  </properties>
</provider>

Switching UAT and PROD

Disconnect provider 74 in Obermind Dash, make three edits, then connect it again:

  1. 1.ServerHost: localhost when the UAT Server API runs on the same machine, the PROD host otherwise.
  2. 2.IsUAT: true uses //blp/emapisvc_beta, false uses //blp/emapisvc.
  3. 3.UsersStr: enable the identity for that environment.

Terminal mode needs only ServerAPI false and a logged-on Terminal on the same machine.

Settings

Property names are case-sensitive and written exactly as below in the provider XML. Values are text: True or False for switches, JSON on one line where noted. A value that cannot be read is ignored and the provider keeps its previous value.

  • IsServerAPI (ServerAPI): False for a Terminal (default), True for a Server API
  • ServerHost, ServerPort: host and port, localhost and 8194 by default
  • UsersStr (Users): JSON list of Server API identities with UUID, IPAddress, Description and Enabled
  • IsUAT (UAT): True for the EMSX test service (default), False for production
  • DefaultAccount (Account): FIX tag 1 when the broker has no entry in AccountsStr
  • AccountsStr (Broker accounts): JSON broker code to account, up to 29 characters
  • RequireAccount (Require account): Server API, reject an order with no account before sending (default True)
  • BrokersStr (Brokers): JSON broker per asset class, keys EQTY, FUT and OPT
  • HandInstructionsStr (Hand instructions): JSON per asset class, ANY, AUTO, DOT or MAN (default ANY)
  • LoggingEnabled, LogPath: Bloomberg message log, one file per day
  • LogEventsStr, LogMessagesStr: JSON event or message type to true or false; only listed types change
  • Enabled, AutoReconnect, AutoReconnectInterval: shared by every provider

Dash tools

Obermind Dash, Providers, Bloomberg shows:

  • the connection status: mode, environment, open services, whether the catalogue loaded for each asset class, and the authorized identity;
  • the brokers per asset class with their accounts and hand instructions;
  • every strategy with its parameters, filterable by asset class;
  • the working routes with Bloomberg sequence and route ids.

Actions:

  • Refresh catalogue re-reads brokers and strategies after Bloomberg changes a broker setup.
  • Re-authorize users renews the Server API identity.

The info icon next to the provider on the Providers list opens the settings reference, with a guide for each asset class and a sample configuration.

Troubleshooting

  • Unknown client from the broker: send the right account in AccountsStr or DefaultAccount
  • No account is configured for broker: add the broker to AccountsStr, or turn RequireAccount off
  • No broker is configured for FUT or OPT orders: set that class in BrokersStr
  • Broker not enabled for FUT or OPT orders on this connection: ask Bloomberg to enable it, or use a broker from the Dash Brokers list
  • Strategy not available for broker: refresh the catalogue; the strategy is not set up for that broker and asset class
  • Instrument type not supported: only Stock, ETF, Index, Future and Option are sent to EMSX
  • Quantity must be a whole number: shares and contracts only, no fractions
  • Option or future rejected as an unknown security: check the ticker is the specific contract with its yellow key
  • Realtime data is not available: expected on the Server API; use VenuePriceSources
  • Orders reach the simulator: set Internaliser to false
  • Orders go to the price provider instead of Bloomberg: VenuePriceSources is missing or was skipped (look for the VenuePriceSources log line), or the instrument has no Bloomberg alternative id
  • Authorization failure: the UUID and IP address pair must match what Bloomberg registered
  • Empty strategy list: ask Bloomberg for the broker's algo setup
Alipay
Stripe
Eurex
AWS
Azure
Google Cloud
Currenex
Velocity Trade
Bitcoin
CME
Interactive Brokers
Kraken
FIX API
XTX
Bloomberg
Binance

अपने प्लेटफ़ॉर्म को लॉन्च करें।