TRTHv2 API do not get any data for this RIC 1ADH5
Using the TRTH API I see the below
- and do not get any data for one of these RICs.
dssConn.validateHistoricRIC(updateService, req,
"1ADH5");
3 * Client out-bound request
3 > POST https://hosted.datascopeapi.reuters.com/RestApi/v1/Search/HistoricalSearch
3 > Prefer: respond-async
3 > Content-Type: application/json
3 > Authorization: <token>
{"Request":{"Identifier":"1ADH5","IdentifierType":"Ric","Range":{"Start":"1996-01-01T00:00:00.000","End":"2016-01-04T08:59:59.999"}}}
3 * Client in-bound response
3 < 200
3 < X-App-Id: Custom.RestApi
3 < Server: Microsoft-IIS/7.5
3 < Cache-Control: no-cache
3 < X-Request-Execution-Correlation-Id: 17238c1f-6738-4fc1-9f15-1cb020b45074
3 < Set-Cookie: DSSAPI-COOKIE=R2485808843; path=/
3 < Expires: -1
3 < Pragma: no-cache
3 < Content-Length: 483
3 < X-App-Version: 11.3.575.64
3 < Date: Fri, 09 Mar 2018 17:27:07 GMT
3 < Content-Type: application/json; charset=utf-8
3 <
@{"@odata.context":"https://hosted.datascopeapi.reuters.com/RestApi/v1/$metadata#Collection(ThomsonReuters.Dss.Api.Search.HistoricalSearchResult)","value":[{"Identifier":"1ADH5","IdentifierType":"Ric","Source":"","Key":"VjF8MHgzMDAwMDAwMDAwMDAwMDAwfDB4MzAwMDAwMDAwMDAwMDAwMHx8fHx8fHwxQURINXw","Description":"Historical
Instrument","InstrumentType":"Unknown","Status":"Valid","DomainCode":"6","FirstDate":"2015-01-24T00:00:00.000Z","LastDate":"2015-03-21T00:00:00.000Z","History":[]}]}
2018-03-09 17:27:18 [main] INFO
com.fd.daas.trthClient.DssMessaging - ThreadID: 1 - validateHistoricRIC|
ClientResponse: { requestID: Validating | Status: 200 |StatusInfo: OK}
2018-03-09 17:27:20 [main] INFO
com.fd.daas.trthClient.DssMessaging - {"@odata.context":"https://hosted.datascopeapi.reuters.com/RestApi/v1/$metadata#Collection(ThomsonReuters.Dss.Api.Search.HistoricalSearchResult)","value":[{"Status":"Valid","LastDate":"2015-03-21T00:00:00.000Z","Identifier":"1ADH5","Description":"Historical
Instrument","DomainCode":"6","FirstDate":"2015-01-24T00:00:00.000Z","InstrumentType":"Unknown","History":[],"IdentifierType":"Ric","Source":"","Key":"VjF8MHgzMDAwMDAwMDAwMDAwMDAwfDB4MzAwMDAwMDAwMDAwMDAwMHx8fHx8fHwxQURINXw"}]}
InstrumentType":"Unknown",
Through the GUI, I’ve managed to create
a report using that historical search, but we need to be able to do these retrievals
through the API as well. Is there some functionality we’re not using correctly?
Best Answer
-
@awilson1, if an instrument is not found when creating an instrument list in the GUI (unless specifically using the historical search), that means it is a historical instrument, not active anymore (example: a matured bond).
You can retrieve historical data for historical RICs using the TRTH API (after all, that is what TRTH is all about, historical data), but this can depend on the query and its parameters. The request posted by Vinaya above delivers a result. If you have queries that do not, and are wondering why, could you please post them here, and we will look at them individually.
0
Answers
-
Hi @vinaya,
The HistoricalSearch is used for instrument validation. It provides the date range where a specific instrument was valid. If the instrument is valid, you can use REST API to create InstrumentList, and append the instrument to the InstrumentList. ReportTemplate and Schedule can be created via REST API as well. The InstrumentList, ReportTemplate and Schedule created via REST API will be available in the GUI as well. Please see the REST API Tutorial 12: GUI control calls: immediate extract tutorial for more information.
Moreover, REST API supports On-Demand extraction which create extractions on the fly. There is no need to create InstrumentList, ReportTemplate and Schedule. They do not have their equivalent in
the GUI. For more information, please see REST API Tutorial 3: On Demand data extraction workflow.0 -
@vinaya.shetty, the query you posted is correct, and I get the same response.
I'm just not sure what your question is about, can you please clarify ? Is it about the fact that the field "InstrumentType" contains value "Unknown" ? I tested a whole set of instruments (FX, Equity, etc), I always received value "Unknown". I will check with the development team if and when other values should be delivered.
Edit:
Answer from the development team (thank you Rick): we do not have the ability to determine the historical instrument type, hence this value "Unknown".
0 -
@Christiaan Meihsl Hi, Angus here, vinaya posted on my behalf.
The root issue is that for a number of instruments no data is returned when requested through the trth API, nor do they appear in the notes files. When creating instrument lists on the GUI they are not found unless specifically using the historical search. Therefore I cannot download historical RICs from the API. Is this correct?0 -
@awilson1, if you run a Historical Reference Extraction Request, field Asset Category will deliver some information. In the case of 1ADH5 that will be CFU (Currency Future) .
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.4K 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
- 559 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
- 280 Open PermID
- 45 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 716 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 中文论坛