Elektron Websocket API - receives null values in ASK field

I'm connecting to the ERT in Cloud Websocket API to stream market price data, and want to clarify what it means when I receive a null value for the ASK field (FID: 25) in a Refresh Message and an Update Message. E.g.
{
"ID": 3,
"Type": "Refresh",
"Key": {
"Service": "ELEKTRON_DD",
"Name": "EURQAR="
},
"Fields": {
"BID": 3.9654,
"ASK": null
...
I have seen some answers for other applications (https://community.developers.refinitiv.com/questions/48255/empty-field-value-bidask.html) but want to make sure I'm interpreting this null value correctly for the WebSocket API example. Can you confirm how I should interpret a null value for BID or ASK in both Refresh and Update messages? Thanks!
Best Answer
-
Regardless of which realtime streaming API you use - RFA, Elektron SDK or WebSocket - and whether you are consuming Elektron Data from a deployed TREP server or from the Cloud you are accessing the same underlying data from the server/cloud.
Therefore the interpretation of Null field remains the same.
0
Answers
-
Thank you. The only other thing I'm unsure about then, is that if we receive a null ASK value in the refresh message (because there is no ASK offer on the market at that point in time), and then we start to receive actual ASK values for that RIC because there is market activity again. If we later receive an update message that has a null ASK value how do we determine whether the ASK rate just hasn't changed since the last update or whether there's actually no offer on the market again?
0 -
If you don't receive an ASK field in an Update then the value has not changed since the previous update.
If you receive an explicit Null value then this means there is no ASK value on the market at this point in time and you should Blank any previous ASK value you were maintaining in your application.
For further clarifications feel free to raise a Content ticket on MyRefinitiv - don't mention an API - just select the relevant Content type question for Elektron in Cloud.
0 -
Perfect, that makes sense. Thank you!
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
- 690 Datastream
- 1.5K DSS
- 629 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 560 WebSocket API
- 39 FX Venues
- 15 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 25 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 281 Open PermID
- 46 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 724 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
- 106 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 95 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛