Which DSS API context should I use to send multiple ISINs and receive them back with their respec...

...tive "RIC Codes"?

I am using the DSS API dlls to obtain the "RIC Codes" of the ISINs and I only found the "SearchContext" context that has the "InstrumentSearch" to return one "RIC Code" at a time.

I would like to know what context and which method should I use to send multiple ISINs and receive their respective "RIC Codes".

I only need the "Ric Codes" identifier

For example:

ISIN BRB1234569 -> RIC ABCD12

ISIN BRB4569012 -> RIC FGHIJ34

And so on.

Could I ask this question in Portuguese?

Best Answer

  • Hi @everton.solon

    You can use this sample for Terms and Conditions template:

    POST /RestApi/v1/Extractions/ExtractWithNotes HTTP/1.1
    Host: hosted.datascopeapi.reuters.com
    Prefer: respond-async
    Content-Type: application/json
    Authorization: Token <your valid token>

    {
        "ExtractionRequest": {
            "@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.TermsAndConditionsExtractionRequest",
            "ContentFieldNames": [
                "RIC",
                "ISIN"
            ],
            "IdentifierList": {
                "@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
                "InstrumentIdentifiers": [
                    { "Identifier": "US4592001014", "IdentifierType": "Isin" },
                    { "Identifier": "GB0005405286", "IdentifierType": "Isin" }
                ],
                "ValidationOptions": null,
                "UseUserPreferencesForValidationOptions": false
            },
            "Condition": null
        }
    }


    This is expected output:

    {
        "@odata.context": "https://hosted.datascopeapi.reuters.com/RestApi/v1/$metadata#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.ExtractionResult",
        "Contents": [
            {
                "IdentifierType": "Isin",
                "Identifier": "US4592001014",
                "RIC": "IBM.N",
                "ISIN": "US4592001014"
            },
            {
                "IdentifierType": "Isin",
                "Identifier": "GB0005405286",
                "RIC": "HSBA.L",
                "ISIN": "GB0005405286"
            }
        ],
        "Notes": [
            "Extraction Services Version 14.2.41795 (d0fe3ba7b1b1), Built Aug 18 2020 17:24:47\r\nUser has overridden estimates broker entitlements.\r\nProcessing started at 2020-09-18 11:18:46.\r\nUser ID: 9001609\r\nExtraction ID: 476478631\r\nSchedule: _OnD_0x07412071b636dd27 (ID = 0x07412071b806dd27)\r\nInput List (2 items): _OnD_0x07412071b636dd27 (ID = 07412071b6d6dd27) Created: 2020-09-18 11:18:44 Last Modified: 2020-09-18 11:18:44\r\nSchedule Time: 2020-09-18 11:18:44\r\nReport Template (8 fields): _OnD_0x07412071b636dd27 (ID = 0x07412071b656dd27) Created: 2020-09-18 11:18:44 Last Modified: 2020-09-18 11:18:44\r\nProcessing completed successfully at 2020-09-18 11:18:46, taking 0.349 Secs.\r\nExtraction finished at 2020-09-18 03:18:46 UTC, with servers: x11n05, QSHC16 (0.0 secs), QSSHA1 (0.0 secs)\r\nUsage Summary for User 9001609, Client 65500, Template Type Terms and Conditions\r\nBase Usage\r\n        Instrument                          Instrument                   Terms          Price\r\n  Count Type                                Subtype                      Source         Source\r\n------- ----------------------------------- ---------------------------- -------------- ----------------------------------------\r\n      2 Equities                                                         N/A            N/A\r\n-------\r\n      2 Total instruments charged.\r\n      0 Instruments with no reported data.\r\n=======\r\n      2 Instruments in the input list.\r\n"
        ]
    }

Answers

  • Hi @everton.solon

    You can use this endpoint:

    POST /RestApi/v1/Extractions/ExtractWithNotes HTTP/1.1
    Host: hosted.datascopeapi.reuters.com
    Prefer: respond-async
    Content-Type: application/json
    Authorization: Token <your valid token>
    {
      "ExtractionRequest": {
        "@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.EndOfDayPricingExtractionRequest",
        "ContentFieldNames": [
          "RIC",
          "ISIN"
        ],
        "IdentifierList": {
          "@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
          "InstrumentIdentifiers": [
              { "Identifier": "US4592001014", "IdentifierType": "Isin" },
              { "Identifier": "GB0005405286", "IdentifierType": "Isin" }
          ]
        },
        "Condition": null
      }
    }

    And this is the output:

    {
        "@odata.context": "https://hosted.datascopeapi.reuters.com/RestApi/v1/$metadata#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.ExtractionResult",
        "Contents": [
            {
                "IdentifierType": "Isin",
                "Identifier": "US4592001014",
                "RIC": "IBM.N",
                "ISIN": "US4592001014"
            },
            {
                "IdentifierType": "Isin",
                "Identifier": "GB0005405286",
                "RIC": "HSBA.L",
                "ISIN": "GB0005405286"
            }
        ],
        "Notes": [
            "Extraction Services Version 14.2.41795 (d0fe3ba7b1b1), Built Aug 18 2020 17:24:47\r\nHoliday Rollover of Universal Close Price waived.\r\nUser has overridden estimates broker entitlements.\r\nProcessing started at 2020-09-16 08:02:43.\r\nUser ID: 9001609\r\nExtraction ID: 475860124\r\nSchedule: _OnD_0x07405cedd976dc57 (ID = 0x07405ceddbb6dc57)\r\nInput List (2 items): _OnD_0x07405cedd976dc57 (ID = 07405cedda46dc57) Created: 2020-09-16 08:02:41 Last Modified: 2020-09-16 08:02:42\r\nSchedule Time: 2020-09-16 08:02:42\r\nReport Template (8 fields): _OnD_0x07405cedd976dc57 (ID = 0x07405cedd996dc57) Created: 2020-09-16 08:02:41 Last Modified: 2020-09-16 08:02:41\r\nProcessing completed successfully at 2020-09-16 08:02:43, taking 0.457 Secs.\r\nExtraction finished at 2020-09-16 00:02:43 UTC, with servers: x01a03, QSHC16 (0.0 secs), QSSHA1 (0.2 secs)\r\nUsage Summary for User 9001609, Client 65500, Template Type EOD Pricing\r\nBase Usage\r\n        Instrument                          Instrument                   Terms          Price\r\n  Count Type                                Subtype                      Source         Source\r\n------- ----------------------------------- ---------------------------- -------------- ----------------------------------------\r\n      2 Equities                                                         N/A            N/A\r\n-------\r\n      2 Total instruments charged.\r\n      0 Instruments with no reported data.\r\n=======\r\n      2 Instruments in the input list.\r\nNo TRPS complex usage to report -- 2 Instruments in the input list had no reported data.\r\n"
        ]
    }
  • Hi @chavalit.jintamalit


    Using this approach, I received the following message from DSS:

    No permission for template "EndOfDayPricingReportTemplate".


    I tried the following part of the code because my user account has permission for the "Terms and Conditions" template, but I haven't received any lines:


    var extractionRequest = new TermsAndConditionsExtractionRequest
    {
        IdentifierList = InstrumentIdentifierList.Create(
            new[] { new InstrumentIdentifier { Identifier = "ABCDEFGHIJKL", IdentifierType.Isin } }, null, false),
        ContentFieldNames = new[] {"RIC", "ISIN"},
        Condition = new TermsAndConditionsCondition
        {
            IssuerAssetClassType = IssuerAssetClassType.AllSupportedAssets,
            ExcludeWarrants = false,
            StartDate = NULL, 
            FixedIncomeRatingSources = FixedIncomeRatingSource.StandardAndPoors,
        }
    };

    Obs: Identifier = "ABCDEFGHIJKL" is not the real identifier in this example.

    Do you know if this template could be useful for me? If so, what do I need to do to recover the data?