historical Search

what does the Key in the response of historical search refer to ? Does it keep changing assigned to a RIC? If it change, how often does it change
Best Answer
-
Please refer to this previous discussion thread for the discussion of this topic.
Hope that this information is of help
0
Answers
-
Thanks Zoya for feedback,
I see the below last line on the reference provided- Could you please advise that the key would never change that is assigned against the instrument.
"The part of your question of whether the keys are guaranteed to stay the same for the same instrument, or ever update, we am going to research further and get back to you on."
Please also feedback if there is a business defnition to each of the response that we get- I could find anything against what validity means in the documentation under dev portal
"@odata.context": "https://selectapi.datascope.refinitiv.com/RestApi/v1/$metadata#Collection(DataScope.Select.Api.Search.HistoricalSearchResult)",
"value": [
{
"Identifier": "0#BL2:",
"IdentifierType": "ChainRIC",
"Source": "",
"Key": "VjF8MHgzMDAwMDAwMDAwMDAwMDAwfDB4MzAwMDAwMDAwMDAwMDAwMHx8fHx8fHwwI0JMMjp8",
"Description": "Historical Chain",
"InstrumentType": "Unknown",
"Status": "Valid",
"DomainCode": "6",
"FirstDate": "1998-02-03T00:00:00.000Z",
"LastDate": "2021-11-14T00:00:00.000Z",
"History": []
}Regards,
0 -
Hello @shwetha.krishnaiah02 ,
In REST API Reference Tree specification for HistoricalSearch request, Results, please find:
Key is "Unique identifier for the instrument".
As part of the research conducted, to provide the answers, to the question from the referenced thread, we have escalated the inquiry to Datascope product team, and have received the confirmation verbatim: "the key information is retrieved from the source as part of Tick History HistoricalSearch which is assigned to an instrument and this will not get changed." Therefore, I confirm, per product guidance, that key as assigned will not change.
For the complete interface, including the meaning of the Enum values in ValidityStatus field within response, please refer to REST API Reference Tree=> HistoricalSearch=> Enums:
Hope that this information is of help
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
- 684 Datastream
- 1.4K DSS
- 615 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
- 249 ETA
- 554 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
- 643 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
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 192 TREP Infrastructure
- 228 TRKD
- 915 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
- 46 中文论坛