REST API error message for ISIN DU00000COCHA reflecting as ISIN DU00000COCH3

Hi,

Wanted to check on the below issue where using DSS REST API for ISIN DU00000COCHA, getting the error message reflecting as ISIN DU00000COCH3 not found under Terms and Conditions Report Template.

I am using DSS Rest API extraction and Identifier List is having ISIN as DU00000COCHA which is a Dummy ISIN, however in the output error message I should be getting the same ISIN, Instead DSS Rest API is returning error message as ISIN DU00000COCH3 not found. I have tried using different permutation and combinations replacing ISIN values with B, C, D and also replacing it by 1,2, 4, 5, 6 all error message is returning the value of ISIN DU00000COCH3 not found.

This seems quite weird when we send ISIN DU00000COCHA to an enpoint of Rest API (given below) and the response is that DU00000COCH3 is not found.

Is it a normal behavior, is there any business rule behind?

Here is the Rest API code and error message:

body:

{

"ExtractionRequest": {

"@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.TermsAndConditionsExtractionRequest",

"ContentFieldNames": [

"ISIN"

"IdentifierList": {

"@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",

"InstrumentIdentifiers": [

{

"Identifier": "DU00000COCHA",

"IdentifierType": "Isin"

}

]

}

… and response (HTTP 200 OK):

{

"@odata.context": https://selectapi.datascope.refinitiv.com/RestApi/v1/$metadata#DataScope.Select.Api.Extractions.ExtractionRequests.ExtractionResult,

"Contents": [

{

"IdentifierType": "Isin",

"Identifier": "DU00000COCH3",

"Error": "Not found"

}

"Notes": [

"All identifiers were invalid. No extraction performed."

]

}

Find more posts tagged with

error

isin

datascope-select

terms-and-conditions

#technology

Accepted answers

Jirapongse

@raghunath.puttarangaiah0

I found that if I set the AllowHistoricalInstruments to True.

 "IdentifierList": {
            "@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
            "InstrumentIdentifiers": [
                {
                    "Identifier": "DU00000COCHA",
                    "IdentifierType": "Isin",
                    "UserDefinedIdentifier": "DU00000COCHA"
                }
            ],
            "ValidationOptions": {
                "AllowHistoricalInstruments": true
            }
        }

The response will contain "DU00000COCHA".

"Contents": [
        {
            "IdentifierType": "Isin",
            "Identifier": "DU00000COCHA",
            "Error": "Not found",
            "UserDefinedIdentifier": "DU00000COCHA"
        }
    ],

However, you need to contact the DSS support team directly to verify this behavior.

All comments

Jirapongse

@raghunath.puttarangaiah0

Thank you for reaching out to us.

I checked and found that the final number of the ISIN code is called a “single check-digit”. For more information, please refer to this website.

I also checked this ISIN (DU00000COCHA) on this website and it showed the following.

Therefore, that last digit of that ISIN is incorrect.

raghunath.puttarangaiah0

Hello @Jirapongse,

Thanks a lot for the above response, however when we enter any ISIN on the API code, it should respond back with the same queried ISIN or will the DSS API rectify as stated above and provide the correct ISIN, even though we enter an Incorrect ISIN. Is this how the response functions for all incorrect ISIN's.

Also if this is the normal behavior, or is there any business rule behind this?

Regards,

Raghunath.K.P.

Jirapongse

@raghunath.puttarangaiah0

If you need to get the incorrect ISIN in the reponse, you can use the UserDefinedIdentifier field.

                {
                    "Identifier": "DU00000COCHA",
                    "IdentifierType": "Isin",
                    "UserDefinedIdentifier":"DU00000COCHA"
                }

The reponse will look like this:

{
            "IdentifierType": "Isin",
            "Identifier": "DU00000COCH3",
            "Error": "Not found",
            "UserDefinedIdentifier": "DU00000COCHA"
        }

raghunath.puttarangaiah0

@Jirapongse,

Thanks for the above information, but does DSS API always correct and display the ISIN if its incorrect and does this apply for all ISIN.

Jirapongse

@raghunath.puttarangaiah0

I found that if I set the AllowHistoricalInstruments to True.

 "IdentifierList": {
            "@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
            "InstrumentIdentifiers": [
                {
                    "Identifier": "DU00000COCHA",
                    "IdentifierType": "Isin",
                    "UserDefinedIdentifier": "DU00000COCHA"
                }
            ],
            "ValidationOptions": {
                "AllowHistoricalInstruments": true
            }
        }

The response will contain "DU00000COCHA".

"Contents": [
        {
            "IdentifierType": "Isin",
            "Identifier": "DU00000COCHA",
            "Error": "Not found",
            "UserDefinedIdentifier": "DU00000COCHA"
        }
    ],

However, you need to contact the DSS support team directly to verify this behavior.

raghunath.puttarangaiah0

Hello @Jirapongse,

Thanks a lot for the above work around, guess this answers the question. Appreciate your help and quick response on the query.

Have a nice day ahead and Happy weekend!!

Regards,

Raghunath.K.P.

EXPLORE OUR SITES