BID and ASK rate for different Rate Types in Websocket API

We have the requirement to get update BID and ASK rate for different set of rates like
FX Rate - CCY_Pair1, CCY_Pair2, CCY_Pair3...
LIBOR -Rate1, Rate2, ....
JIBOR - Rate1. Rate2, ...
and so on...
By following provided examples, we are designing a prototype with below logic.
AtomicInteger index = new AtomicInteger();
rateTypes.forEach(rateTypeVO -> {
String rateNames = String.join(",", rateTypeVO.getRateNames());
String requestJsonString = "{\"ID\":"+index.incrementAndGet()+",\"Key\":{\"Name\":["+rateNames+"]},\"View\":[\"BID\",\"ASK\",\"BIDSIZE\",\"ASKSIZE\"]}";
websocket.sendText(requestJsonString);
});
And we are expecting to get rate updates on 'Refresh' and 'Update'
But when looking at the available fields in response we can see BID/ASK/BIDSIZE/ASKSIZE/...
Can we know for our purpose we only needs to check for BID & ASK field only always?
or there is any logic needs to apply on BID & ASK values with respect to BIDSIZE & ASKSIZE? since these two fields are not familiar to us
We have checked the response data documentation to get details on these but cannot find such one.
There is any link to refer the description for all field values in market data response?
Best Answer
-
Hi @girish
The BIDSIZE and ASKSIZE fields represent 'The number of shares, lots, or contracts willing to buy at the Bid/Ask price.'
If you don't need the fields, just remove them from your original JSON request View parameter. If you have not already done so, I recommend you refer to the Websocket API Tutorials | Refinitiv Developers
You can find a list of fields etc in the RDMFieldDictionary file located at
Real-Time-SDK/Java/etc at master · Refinitiv/Real-Time-SDK (github.com)0
Answers
-
Ok. If we specify BID & ASK in View, always it will give BID & ASK in `Update` response or only the updated fields? since as per referring the sample outputs we can see only BID/ASK with updated rates. If no, there is any option to fetch both together always in `Update` response?
0 -
Hi @girish
It is general practice for real-time streaming APIs to only provide fields that have changed since the previous refresh/update to minimize bandwidth usage & unnecessary processing of unchanged fields.
It is normal practice for the application to maintain a local cache of the most recent values and update the cache with whatever fields it receives in each update.
There is no option to force the server to send both BID+ASK in every update for a streaming subscription.
0
Categories
- All Categories
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 682 Datastream
- 1.4K DSS
- 613 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 248 ETA
- 552 WebSocket API
- 37 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
- 275 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
- 626 Refinitiv Data Platform Libraries
- 5 LSEG Due Diligence
- 1 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
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 191 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 83 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛