question

Upvotes
Accepted
vinaya avatar image
0 ●2 ●0 ●4

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?

tick-history-rest-api
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 5.0 MiB each and 10.0 MiB total.

4 Answers

Upvotes
Accepted
Christiaan Meihsl avatar image
13.7k ●26 ●8 ●12

@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.

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 5.0 MiB each and 10.0 MiB total.

Upvotes
veerapath.rungruengrayubkul avatar image
11.3k ●25 ●8 ●13

Hi @vinaya.shetty,

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.

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 5.0 MiB each and 10.0 MiB total.

Upvotes
Christiaan Meihsl avatar image
13.7k ●26 ●8 ●12

@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".

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 5.0 MiB each and 10.0 MiB total.

Christiaan Meihsl avatar image Christiaan Meihsl

@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) .

Upvotes
awilson1 avatar image
1 ●0 ●0 ●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?

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 5.0 MiB each and 10.0 MiB total.

Click below to post an Idea Post Idea