Is it possible to do a Datascope request using PermID within the REST API?
I - we have been experimenting with doing a security search using the Rest API and on demand extraction in Datascope. Traditionally we have done this lookup using the RIC as the identifier, but we're trying to see if it can be done by Perm ID instead. We are passing in the identifier type along with the instrument, but I don't see an option there for PermID.
For example:
new InstrumentIdentifier { Identifier = "IBM.N", IdentifierType = IdentifierType.Ric }
I thought that perm ID was the recommended way to do something like this going forward.
Thanks,
Wayne
Best Answer
-
@waynes, sorry for the late response, I was on vacation.
DSS will not support queries using PermId in 2019, you should continue using RICs as you have up to now.
0
Answers
-
You are correct, there are ways forward to use PermID
new InstrumentIdentifier { Identifier = "55838323096", IdentifierType = IdentifierType.Pid }
I am not sure which PermID's are supported as of today but there are multiple types, the one I believe is QuotePermID but yet I see no identifier found in DSS request.
0 -
I recommend you continue using RICs with DSS (and TRTH).
Even if several API calls allow you to retrieve the Issuer PermID, Issue PermID or Quote PermID, that does not mean you can use them to retrieve data.
I have just tried an EoD request using several PermIDs (4295904307 = IBM, 8589934326 = BNPP.PA, 4295896661 = VOD.L), they all returned an error:
{
"@odata.context": "https://hosted.datascopeapi.reuters.com/RestApi/v1/$metadata#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.ExtractionResult",
"Contents": [
{
"IdentifierType": "Pid",
"Identifier": "4295896661",
"Error": "Not found"
}
],
"Notes": [
"All identifiers were invalid. No extraction performed."
]
}Also note that Identifier Type Pid is not supported for an InstrumentSearch.
0 -
We also have another alternative using PermID.org API, please refer the developer community page that explains how you can extract the RIC
GET https://permid.org/1-55838323096?format=turtle&access-token=KmbzKKusmYkbbetbZrk8doKfPJnrxh5S
RESPONSE
@prefix tr-fin: <http://permid.org/ontology/financial/> .
@prefix tr-common: <http://permid.org/ontology/common/> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
<https://permid.org/1-55838323096>
a tr-fin:Quote ;
tr-common:hasName "INTERNATIONAL BUSINESS MACHINES ORD"^^xsd:string ;
tr-common:hasPermId "55838323096"^^xsd:string ;
tr-fin:hasExchangeCode "NYS"^^xsd:string ;
tr-fin:hasExchangeTicker "IBM"^^xsd:string ;
tr-fin:hasMic "XNYS"^^xsd:string ;
tr-fin:hasRic "IBM.N"^^xsd:string ;
tr-fin:isQuoteOf <https://permid.org/1-8590927768> ;
tr-fin:isQuotedIn <https://permid.org/1-500110>0 -
Thanks. Does anyone know what Reuters plan is for this identifier? My impression was that this was meant to ultimately replace RIC as a more durable way to requests instruments. The OpenPerm website is up and seems to be working, but it seems like support hasn't been rolled out to all of the other products yet. Is this in the works still and should we play to eventually move our requests to use PermIDs? Or are RICs here to stay ?
0 -
RIC will always remain primary and proprietary identifier and we encourage customers to use RIC.
Please reach to Refinitiv Helpdesk for further clarifications
0 -
@waynes, RICs are currently central to many of our products, including DSS. But your query is about our future plans. I have therefore escalated this particular query to DSS product management, as this is a strategic query rather than a technical query. I hope to post their answer here soon.
0 -
@waynes, I'm still in discussions with the product management team, but to give you a status and a view on the roadmap, there is currently little demand for PermId, and no plan for DSS (and TRTH) to support queries using PermId in 2019.
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
- 697 Datastream
- 1.5K DSS
- 632 Eikon COM
- 5.2K Eikon Data APIs
- 12 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 4 Trading API
- 2.9K Elektron
- 1.4K EMA
- 256 ETA
- 562 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
- 745 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
- 122 Open DACS
- 1.1K RFA
- 107 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 97 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛