question

Upvotes
Accepted
16 2 2 9

I have already used the historical search on REST API. But the issue is that it is for a single Isin or a single Sedol. We need an API which will help us to get the Ric codes for a list of Isins/Sedols/Cusips. Is there a way?

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.

Upvotes
Accepted
13.7k 26 8 12

@Manigandan.R, it is not quite clear what you are trying to achieve, there seem to be 2 different queries here.

In the title you ask: "We need an API which will help us to get the Ric codes for a list of Isins/Sedols/Cusips. Is there a way?".

Answer 1: you can use a Historical Reference extraction request, which takes as input a list of instruments (you can mix ISIN, CUSIP, SEDOL etc.) and return the corresponding RICs. In other words, this will do a bulk conversion of ISINs/SEDOLs/CUSIPs into RICs. As there will be several RICs per input instrument, you can also request the currency and/or exchange code in order to filter the results.

Note that this can be done easily in the API with an On Demand request, which does not require a instrument list to be present on the server. Instead the instrument list is passed as a parameter.

This is described in REST API tutorial 10 (which was recently changed to illustrate an HR (Historical Reference) call instead of a T&C (Terms & Conditions) call, because T&C will not return historical results whereas HR will). The corresponding Postman HTTP requests are available in the latest downloadable Postman collection, under the downloads tab.

Then I see a different query: "how do I import a LIST of ISINs or CUSIP or SEDOL or RICs at a time". Is this related to the above query, or is it unrelated ?

Answer 2: if it related, then the answer is that it is not necessary to load the list of ISINs, CUSIPs and SEDOLs in the server to be able to retrieve the equivalent RICs, as explained in Answer 1.

Answer 3: if it is not related, am I right in guessing you just want to create a list of instruments on the server, for later usage in scheduled queries ? If yes, then you can easily create a list, and add instruments, using the API. That is described in detail in steps 3 and 4 of the REST API Tutorial 12.

Maybe I have misinterpreted your query ? If yes, then please provide more details on what you are trying to achieve.

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
38.1k 71 35 53

You can use On Demand Term and Conditions extraction. The request contains the list of identifiers with different types and the list of required content fields.

{
  "ExtractionRequest": {
    "@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.TermsAndConditionsExtractionRequest",
    "ContentFieldNames": [
     "RIC", "CUSIP", "ISIN", "SEDOL", "Issuer OrgID", "Currency Code"
    ],
    "IdentifierList": {
      "@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
      "InstrumentIdentifiers": [
        {
          "Identifier": "00209tab1",
          "IdentifierType": "Cusip"
        },
        {
          "Identifier": "IBM.N",
          "IdentifierType": "Ric"
        },
        {
          "Identifier": "US4592001014",
          "IdentifierType": "Isin"
        },
        {
          "Identifier": "B1YW440",
          "IdentifierType": "Sedol"
        }
      ]
    }
  }
}

The response will contains the requested content fields.

{
  "@odata.context": "https://hosted.datascopeapi.reuters.com/RestApi/v1/$metadata#Collection(ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.ExtractionRow)",
  "value": [
    {
      "IdentifierType": "Cusip",
      "Identifier": "00209TAB1",
      "RIC": "00209TAB1=RRPS",
      "CUSIP": "00209TAB1",
      "ISIN": "US00209TAB17",
      "SEDOL": "2166502",
      "Issuer OrgID": "172642",
      "Currency Code": "USD"
    },
    {
      "IdentifierType": "Ric",
      "Identifier": "IBM.N",
      "RIC": "IBM.N",
      "CUSIP": "459200101",
      "ISIN": "US4592001014",
      "SEDOL": "2005973",
      "Issuer OrgID": "18228",
      "Currency Code": "USD"
    },
    {
      "IdentifierType": "Isin",
      "Identifier": "US4592001014",
      "RIC": "IBM.N",
      "CUSIP": "459200101",
      "ISIN": "US4592001014",
      "SEDOL": "2005973",
      "Issuer OrgID": "18228",
      "Currency Code": "USD"
    },
    {
      "IdentifierType": "Sedol",
      "Identifier": "B1YW440",
      "RIC": "LP71000002",
      "CUSIP": null,
      "ISIN": "GB00B1YW4409",
      "SEDOL": "B1YW440",
      "Issuer OrgID": "100691344",
      "Currency Code": "GBp"
    }
  ]
}

For more information, please refer to REST API Tutorial 10: On Demand T&C extraction.

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
16 2 2 9

cusersu6031025documentsisin.txtThank you for the response. If I may clarify the question -

Historical Search allows you to verify just ONE RIC or ISIN or CUSIP or SEDOL at a time. The customers question is how do I import a LIST of ISINs or CUSIP or SEDOL or RICs at a time. On the TRTH v2 GUI, you have the BULK Search option in Historical BULK SEARCH is the option that can be used to achieve this. What is the TRTH v2 REST API equivalent? And if you could provide the API code that demonstrates how the attached list of ISINs can be imported will be great. We are aware that ISINs need to be saved in Column B, RICs in column A, CUSIPS in Column C and SEDOLs in Column D. I have saved the list of ISINs in in the attached file. Please provide the REST API code to bulk import these identifiers in TRTH v2. @

jirapongse.phuriphanvichai


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.

@Manigandan.R

Refer to the REST API Reference Tree in Search section, I couldn't find a function that is equivalent to Bulk Search. However, you can use the TermsAndConditionsExtractionRequest mentioned in the first answer or HistoricalReferenceExtractionRequest to retrieve the required data.

Click below to post an Idea Post Idea