Websocket return code - Close market

Hi,
We would like to know if the API allows us to know the position of the markets, whether they are open, closed or no data available.
- It does not return anything, we then consider that the market is closed
- Or, it returns a specific value, which indicates the closing of the market
- Or, inform about opening and closing hours.
Is there an error list
Thanks
Best Answer
-
Hi @Rey
The API itself is not providing the null value. You are using the Websocket API to request data for PEGDA from the Elektron feed. If you are receiving a null value, then it is the Elektron feed that is publishing the null value.
The PEGDA RIC is just one of the millions of RICs that we carry on our Elektron feed and characteristics of the data received for each RIC can vary depending on the instrument type / asset class / exchange etc.
The API will just return whatever the feed publishes - that is why I recommended you contact the Content helpdesk so they can explain how each of the instruments / markets you are interested will behave when the market is closed.
0
Answers
-
Hi @Rey,
The Websocket API can be used to consume data from a source such as Elektron Realtime in Cloud or a TREP server and is content neutral.
It cannot directly communicate the state of a particular market. Even if you request an instrument from a closed market, you canl still get a response which shows the current state of the instrument e.g. closing price etc.
To determine if the market for that instrument is open / closed or any other state e.g. halted, you will need to raise a Content Type ticket for Elektron with our Helpdesk. When you raise the ticket please provide examples of instruments / markets / asset classes you are interested in.
It would be advisable not to mention Websocket API in the query - to ensure your ticket is routed to a content specialist and not API support.
0 -
Hi Umer,
Thanks for your response. In case this is our request without the token
When the market ix close w have a null value.
Login :
{
"Domain":"Login",
"ID":1,
"Key":{
"Elements":{
"ApplicationId":"256",
"AuthenticationToken":"00000"Position":"1.1.1.1\/myhost"
},
"NameType":"AuthnToken"
}
}
Market message :
{
"ID":2,
"Key":{
"Name":"PEGDA"
}
}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 中文论坛