Instrument search - "PreferredIdentifierType": "OrgId"

By using the API for an Instrument Search [below request payload] the identifier type in the output is "NONE", this seems wrong and should be 'OrgId' as:
- the request has OrgID as preferred identifier
- identifier is an OrgID in the output
API Request –
URL - https://selectapi.datascope.refinitiv.com/RestApi/v1/Search/InstrumentSearch
API Request-
{
"SearchRequest": {
"InstrumentTypeGroups": [
"GovCorp"
],
"IdentifierType": "Isin",
"Identifier": "XS2848666900",
"PreferredIdentifierType": "OrgId"
}
}
API Response –
{
"@odata.context": "https://selectapi.datascope.refinitiv.com/RestApi/v1/$metadata#Collection(DataScope.Select.Api.Content.ValidatedInstrument)",
"value": [
{
"Identifier": "112740611",
"IdentifierType": "NONE",
"Source": "EJV",
"Key": "VjF8MHgwMDEwNTU5YWE0MDIxMDY5fDB4MDAxMDU1NmY2MDYxMTAzYnxFSlZ8R0NCRHxDT1JQfENGSU58R3xFfHxHT1JQ",
"Description": "C 10.000 09/25/24",
"InstrumentType": "GovCorpBond",
"Status": "Valid"
},
{
"Identifier": "112740611",
"IdentifierType": "NONE",
"Source": "EJV",
"Key": "VjF8MHgwMDEwNTU5YWE0MDIxMDY5fDB4MDAxMDU1OTJkNjAzMTAxMnxFSlZ8R0NCRHxDT1JQfENGSU58R3xFfHxHT1JQ",
"Description": "C 10.000 09/25/24",
"InstrumentType": "GovCorpBond",
"Status": "Valid"
}
]
}
However, when I do the exact same search in GUI, I can see the Identifier Type as OrgId.
As per “DSS REST API Reference Tree” when provided OrgId as preferred type below is the result, out put provides "NONE".
Is this a bug which can be fixed, or this is how the product is designed? If this is how the product is designed why is the behaviour different in GUI and API?
Can we assume that for this type of request (preferred identifier set as OrgID) NONE can be understood as 'OrgId'? As per my understanding it might be interpreted as the orgID, but it cannot be definitively stated that it "always will be" the orgID. Correct?
Best Answer
-
Thank you for reaching out to us.
It looks like to be a problem in the DSS REST API. Please contact the DSS support team directly via MyAccount to investigate this issue.
0
Answers
-
@Jirapongse Thank you. Development team has identified this as a bug and raised a JIRA to have a fix in place.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 690 Datastream
- 1.5K DSS
- 629 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 560 WebSocket API
- 39 FX Venues
- 15 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 25 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 281 Open PermID
- 46 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 724 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- 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
- 27 DACS Station
- 121 Open DACS
- 1.1K RFA
- 106 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 95 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛