Is it possible to do a Datascope request using PermID within the REST API?

waynes

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

Christiaan Meihsl

@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.

nityanand.koppad

@waynes

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.

Christiaan Meihsl

@waynes,

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.

nityanand.koppad

@waynes

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/&gt; .
@prefix tr-common: <http://permid.org/ontology/common/&gt; .
@prefix xsd:   <http://www.w3.org/2001/XMLSchema#&gt; .
<https://permid.org/1-55838323096&gt;
        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&gt; ;
        tr-fin:isQuotedIn         <https://permid.org/1-500110&gt; 

waynes

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 ?

nityanand.koppad

@waynes

RIC will always remain primary and proprietary identifier and we encourage customers to use RIC.

Please reach to Refinitiv Helpdesk for further clarifications

Christiaan Meihsl

@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.

Christiaan Meihsl

https://community.developers.refinitiv.com/discussion/comment/39550#Comment_39550

@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.