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

Overview |  Quickstart |  Documentation |  Downloads |  Tutorials

question

Upvotes
Accepted
3 5 5 8

PriceHistoryExtractionRequest IdentifierValidationErrors

Hi, I am testing PriceHistory Extraction API (/RestApi/v1/Extractions/ExtractRaw)

Why would we receive "IdentifierValidationErrors". From my testing, it seems that this may only be the case when we send over an unrecognized RIC to the service. But are there other such scenarios for receiving a validation error response?

My Sample response

{
"IdentifierValidationErrors": [
        {
            "Identifier": {
                "@odata.type": "#ThomsonReuters.Dss.Api.Content.InstrumentIdentifier",
                "Identifier": "IEFA",
                "IdentifierType": "Ric",
                "Source": ""
            },
            "Message": "Not found"
        }
]
}
dss-rest-apidatascope-selectdssrics
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.

@elvis.fernandez, thank you for your participation in the forum. Is the reply below satisfactory in resolving your query? If yes please click the 'Accept' text beneath the reply. This will guide all community members who have a similar question. Otherwise please post again offering further insight into your question. Thanks, AHS

Please be informed that a reply has been verified as correct in answering the question, and has been marked as such.

Thanks,

AHS

1 Answer

· Write an Answer
Upvotes
Accepted
13.7k 26 8 12

@elvis.fernandez,

RIC IEFA was quoted between January 1996 and July 1998. As it is not quoted anymore it is considered as a historical instrument. These will generate a "Not found", except if you specify that you want to allow historical instruments.

The setting to allow historical instruments can be set in the GUI preferences screen, but that only applies to instruments imported into lists, that are then used in scheduled requests.

For on demand requests you need to specify that you allow historical instruments in the query itself, using parameter ValidationOptions, like this:

"IdentifierList": {
  "@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
  "InstrumentIdentifiers": [
    { "Identifier": "IEFA", "IdentifierType": "Ric" }
  ],
  "ValidationOptions": { "AllowHistoricalInstruments": true },
  "UseUserPreferencesForValidationOptions": false
},

As you did not post your request I am guessing that this is what's missing. If this does not solve the issue, then please post the entire request body so we can investigate further.

To clarify this I added a section on instrument validation in the DSS Tutorials Introduction, and updated DSS REST tutorial 4 to illustrate this.

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.

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

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