PermIDs in online reports news RDP API

Your documentation suggests that we use PermIDs for companies as an alternative to RICs, since PermIDs are more stable than RICs and it is also possible for multiple RICs to correspond to a single company. So, we plan to use PermIDs instead of RICs when we parse the subjects of a news response. However, I can see that in the online reports response there are no PermIDs but only RICs. This blocks us from replacing RICs with PermIDs when parsing the online reports response. Is there something that I am missing? Can you please provide a solution to the above issue?
Best Answer
-
Hi @pevangelidis,
Thanks for your patience, please see the response below I got from support team:
- Online Reports are only callable by ReportID within the Online Report API endpoint. There is no RIC or PermID filtering capability on this call for a report.
- Once a Report is called and returned, the individual message components of that report can then be called, where the results will contain metadata that can include RIC(s) but not PermIds.
- The means by which Refinitiv receives and provides the individual components do not traverse our metadata enrichment process and hence PermId is not appended.
- The recommendation to rely on PermId for company organization identification is particular to text news and not to Online Reports. Refinitiv can advise that the RICs returned in the Online Report sub-stories can be mapped to PermId using the symbology lookup endpoint https://api.refinitiv.com/discovery/symbology/v1/lookup.
- We will look to update documentation to make this behavior and process more transparent.
Symbology endpoint in the playground highlights this as an example, below should provide a viable solution to resolve RIC to PermId from OLR embedded messages.
{
"from": [
{
"identifierTypes": [
"RIC"
],
"values": ["AMUN.PA", "LSEG.L"]
}
],
"to": [
{
"objectTypes": [
"organization"
],
"identifierTypes": [
"PermID"
]
}
],
"reference": [
"name",
"status",
"classification"
],
"type": "auto"
}Let me know if this was helpful or you have any further queries
0
Answers
-
For the clarification of the content, as this forum is dedicated to software developers using Refinitiv APIs and the moderators on this forum do not have deep expertise in every bit of content available through Refinitiv products, which is required to answer content questions such as this one.
The best resource for content questions is the Refinitiv Helpdesk, which can be reached by either calling the Helpdesk number in your country or submitting a new ticket to the support team via MyRefinitiv.
However, for this case, ticket number 11145283 was raised on your behalf and the support team is going to email you soon for clarification of this.
0 -
Hi @pevangelidis,
Meanwhile, can you please provide me with a screenshot to get a better understanding of how you are using OLR with RIC and PERMIDs?
0 -
Hello @Shadab Hussain ,
This is the "subject" field of an online report with id "tag:reuters.com,2022:newsml_KCN2MC0ZP". As you can see we cannot use e.g. "P:5000034874" to match "Amundi SA" but only "AMUN.PA" which is a RIC and according to the documentation less stable.
0 -
Thanks for sharing this @pevangelidis, I have shared the response with Support team. I will keep you posted. Meanwhile, did you try any code from your side? If, yes can you share the code snippet?
0 -
Hello @Shadab Hussain,
It seems that the symbology lookup endpoint will work for us if we want to use permids instead of RICs. Thank you for your response.
0 -
@pevangelidis, do let us know if you have any further queries. We would be happy to help.Yes0
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
- 695 Datastream
- 1.5K DSS
- 631 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
- 255 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
- 736 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
- 96 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛