Differences in instrument validation between SOAP and RestApi

Hi, we are migrating from SOAP to RestAPi and found one difference in validation.
When I check if one CUSIP is correct, I am getting the result for slightly modified identifier.
e.g. asking for 31932817, the result is for 319328175 (another example is 31932810 and 319328100)
{
"InputsForValidation": [
{
"Identifier": "31932817",
"IdentifierType": "Cusip"
}
],
"KeepDuplicates": true
}
response:
{
"@odata.context": "https://hosted.datascopeapi.reuters.com/RestApi/v1/$metadata#ThomsonReuters.Dss.Api.Extractions.SubjectLists.InstrumentsValidateIdentifiersResult",
"ValidatedInstruments": [
{
"Identifier": "319328175",
"IdentifierType": "Cusip",
"Source": "",
"Key": "VjF8MHgwMDAwMDAwMDAwMDAwMDAwfDB4MDAwMDAwMDAwMDAwMDAwMHx8fHx8fHx8",
"Description": "",
"InstrumentType": "MortAggregate",
"Status": "NotFound"
}
],
"ValidationResult": {
"ValidInstrumentCount": 1,
"OpenAccessSegments": [],
"StandardSegments": [],
"ValidationDuplicates": [],
"Messages": [
{
"Severity": "Info",
"Message": "CSP, 319328175 (not found)"
}
]
}
}
in SOAP implementation the result was exactly for the same ticker (response matched with request).
Can you help me understand why this happens? is it something common? is it only for CUSIPs or ISIN or RICs as well?
Thank you
Michał
Best Answer
-
It looks similar to this question: DSS REST API extraction automatically flips the last character of my CUSIP code.
It relates to the User Preferences settings in DSS.
If I set only Allow Import of Unsupported Instruments into Instrument Lists, it returns:
{
"Identifier": "319328175",
"IdentifierType": "Cusip",
"Source": "",
"Key": "VjF8MHgwMDAwMDAwMDAwMDAwMDAwfDB4MDAwMDAwMDAwMDAwMDAwMHx8fHx8fHx8",
"Description": "",
"InstrumentType": "MortAggregate",
"Status": "NotFound"
}
If I set both Allow Import of Unsupported Instruments into Instrument Lists and Allow Import of Historical Instruments, it returns:
{
"Identifier": "31932817",
"IdentifierType": "Cusip",
"Source": "",
"Key": "VjF8MHgwMDAwMDAwMDAwMDAwMDAwfDB4MDAwMDAwMDAwMDAwMDAwMHx8fHx8fHx8",
"Description": "",
"InstrumentType": "MortAggregate",
"Status": "NotFound"
}0
Categories
- All Categories
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 682 Datastream
- 1.4K DSS
- 613 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 248 ETA
- 552 WebSocket API
- 37 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.8K Refinitiv Data Platform
- 625 Refinitiv Data Platform Libraries
- 5 LSEG Due Diligence
- 1 LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 191 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 83 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛