Urgent Help:C# LSEG.Data library

Hi Team,
We need your immediate assistance on this matter.
We're in the process of migration of our software from Eikon to the new LSEG Workspace.
One of our applications depends on auction imbalances coming from Eikon for various symbols. In the test account we currently hold for the LSEG Workspace, we can see only following imbalances available on the EU market:
- IMB_SH - imbalance shares
- IMB_SIDE - imbalance side
- IMB_TIM_MS - imbalance timestamp millisecond
Still to test the application completely before heading for deployment it would be great to confirm that also following imbalance fields work:
- IMB_PR_FR - imbalance far price
- IMB_PR_NR - imbalance near price
- IMB_PR_REF - imbalance reference price
- IMB_PR_SH - imbalance paired shares
In the LSEG Workspace we currently get imbalances only for some symbols in the European market such as (but only during an auction phase):2025-04-10 14:49:34,942 [18] INFO EikonCSharpShared.ZmqAuctionDataPublisher [(null)] - onRefresh: BMWG.DE ; json: {
"Fields": {
"CF_EXCHNG": "GER",
"CLS_AUC": null,
"CLS_AUCVOL": null,
"IMB_SH": null,
"IMB_SIDE": null,
"INDAUC_MS": null,
"INDAUC_NS": null,
"IND_AUC": null,
"IND_AUCVOL": null,
"INST_PHASE": "T ",
"INT_AUC": 66.28,
"INT_AUCVOL": 1672,
"OPN_AUC": 72.46,
"OPN_AUCVOL": 174322
},
"State": {
"Data": "Ok",
"Stream": "NonStreaming",
"Code": "None",
"Text": "All is well"
},
"Qos": {
"Rate": "TimeConflated",
"Timeliness": "DelayedUnknown"
},
"Type": "Refresh",
"SeqNumber": 21838,
"ID": 4,
"Key": {
"Name": "BMWG.DE",
"NameType": "Ric",
"Service": "Q"
}
}
For US stock MSFT.ITC , where the imbalances are observable in Eikon we get:2025-04-10 14:49:23,685 [7] INFO EikonCSharpShared.ZmqAuctionDataPublisher [(null)] - onStatus: MSFT.ITC ; json: {
"Domain": "MarketPrice",
"State": {
"Data": "Suspect",
"Stream": "Closed",
"Code": "NotEntitled",
"Text": "Access Denied: User req to PE(2678)"
},
"Type": "Status",
"ID": 2,
"Key": {
"Name": "MSFT.ITC",
"NameType": "Ric",
"Service": "Q"
}
}
Would it be possible to either:
- Let us use imbalances on EU market (if they exist)
- Or let us use some symbols on US market?
Answers
-
Thank you for reaching out to us.
It looks like to be a content and permission question ("Access Denied: User req to PE(2678)").
Please contact the helpdesk team directly to verify the content and permission.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 687 Datastream
- 1.4K DSS
- 621 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 4 Trading API
- 2.9K Elektron
- 1.4K EMA
- 254 ETA
- 557 WebSocket API
- 38 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 276 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 669 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 27 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 193 TREP Infrastructure
- 229 TRKD
- 917 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛