Price History Exchange Value

If I request a price history is the API returning the price for the Nasdaq exchange or an average amongst other exchanges?
Request:
{
"ExtractionRequest": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.PriceHistoryExtractionRequest",
"ContentFieldNames": [
"RIC",
"Trade Date",
"Universal Close Price",
"Volume"
],
"IdentifierList": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers": [
{
"IdentifierType": "Ric",
"Identifier": "DWAQ.O"
}
]
},
"Condition": {
"AdjustedPrices": false,
"QueryStartDate": "2019-05-17",
"QueryEndDate": "2019-05-28"
}
}
}
Response
RIC,Trade Date,Universal Close Price,Volume
DWAQ.O,2019/05/17,,
DWAQ.O,2019/05/20,,
DWAQ.O,2019/05/21,111.79,
DWAQ.O,2019/05/22,111.36,
DWAQ.O,2019/05/23,108.8476,
DWAQ.O,2019/05/24,110.58,
DWAQ.O,2019/05/28,110.9,
Best Answer
-
\*.O (e.g. DWAQ.O) is a consolidated quote from all US trading venues, \*.OQ (e.g. DWAQ.OQ) is NASDAQ only. The close price for \*.OQ is NASDAQ Official Closing Price (NOCP), the close price for \*.O is the consolidated last sale price. For illustration of the difference see the closing prices for AAME between 28-May-19 and 30-May-19.
https://www.nasdaq.com/aspx/historical_nocp.aspx?symbol=AAME
https://www.nasdaq.com/symbol/aame/historical
and compare them to close prices returned by TRTH for AAME.OQ and AAME.O.0
Answers
-
the RIC you use (in this case DWAQ.O) determines where the data is taken from. As an example:
- DWAQ.O is data from the Nasdaq exchange.
- DWAQ.B is data from the Boston exchange.
- Etc. (there are more RICs ...)
Now, effectively, I see that DWAQ.O is labeled as "NASDAQ Global Market Consolidated". Not being a data specialist I don't know exactly what this means. This forum is for software developers using Refinitiv APIs, and technical discussions. For data content query like this one, the best and speediest way to receive an answer is to open a content-related enquiry via MyRefinitiv or to call the Refinitiv Help Desk directly.
0 -
Where can I find the documentation for generation the consolidated ric for a security symbol
0 -
Assuming the question is about US stocks, for NASDAQ stocks consolidated RIC has ".O" exchange suffix (e.g. "AAPL.O", "FB.O", "MSFT.O"), for NYSE stocks consolidated RIC has no exchange suffix (e.g. "KO", "C", "GE", "GM").
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
- 622 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
- 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
- 676 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
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 91 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛