For a deeper look into our DataScope Select REST API, look into:

Overview |  Quickstart |  Documentation |  Downloads |  Tutorials

question

Upvotes
Accepted
1 0 0 1

Getting constituents on a CHAIN RIC using Rest API without extracting on DSS

We would ideally like to be able to call a chain RIC, see which RICs are returned so we can then do EOD/Intraday extractions, without doing an extraction on the entire chain which will consume our quota. sampleR RIC

0#HO:


Thank you.

dss-rest-apidssdatascope-selectchain-ric
icon clock
10 |1500

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

Upvotes
Accepted
29k 33 11 15

Hello @jose.uy0,

Understood.

The way to do so without an Extraction request, would be via Search.

And the search that supports chain expansion is HistoricalChainResolution, so I believe if the customer is DSS, they will have to expand the chain as part of their required Extraction request.

If they extract the same chain repeatedly, they may wish to store the extracted instruments returned by their first request, and submit them separately as RICs into the next requests, as potential optional approach.


icon clock
10 |1500

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

Upvotes
29k 33 11 15

Hello @jose.uy0 ,

Absolutely. Would HistoricalChainResolution Search satisfy the requirement:

{
                {protocol}}{
                {host}}{
                {api}}Search/HistoricalChainResolution

Request

{
  "Request": {
    "ChainRics": [
      "0#HO:"
    ],
    "Range": {
      "Start": "2021-06-17T00:00:00.000Z",
      "End": "2021-06-17T00:00:00.000Z"
    }
  }
}

Result

{
    "@odata.context": "https://hosted.datascopeapi.reuters.com/RestApi/v1/$metadata#Collection(ThomsonReuters.Dss.Api.Search.HistoricalChainInstrument)",
    "value": [
        {
            "Identifier": "0#HO:",
            "IdentifierType": "ChainRIC",
            "Source": "",
            "Key": "VjF8MHgzMDAwMDAwMDAwMDAwMDAwfDB4MzAwMDAwMDAwMDAwMDAwMHx8fHx8fHwwI0hPOnw",
            "Description": "Historical Chain",
            "InstrumentType": "Unknown",
            "Status": "Valid",
            "Constituents": [
                {
                    "Identifier": "HON1",
                    "IdentifierType": "Ric",
                    "Source": "",
                    "Key": "VjF8MHgzMDAwMDAwMDAwMDAwMDAwfDB4MzAwMDAwMDAwMDAwMDAwMHx8fHx8fHxIT04xfA",
                    "Description": "Historical Instrument",
                    "InstrumentType": "Unknown",
                    "Status": "Valid",
                    "DomainCode": "6"
                },
                {
                    "Identifier": "HOQ1",
                    "IdentifierType": "Ric",
                    "Source": "",
                    "Key": "VjF8MHgzMDAwMDAwMDAwMDAwMDAwfDB4MzAwMDAwMDAwMDAwMDAwMHx8fHx8fHxIT1ExfA",
                    "Description": "Historical Instrument",
                    "InstrumentType": "Unknown",
                    "Status": "Valid",
                    "DomainCode": "6"
                }, 
...



icon clock
10 |1500

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

Upvotes
1 0 0 1

Hi @zoya.farberov This is great but client does not have TIck history enabled. only DSS.

Is there any other way?


Thank you

icon clock
10 |1500

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