HistoricalPricing.GetSummaries reponse IsSuccess returns "true" even if there is no data due to a...

... permission error.
Connecting via RDP platform Session.
Modified example 2.0.0:
var response = HistoricalPricing.GetSummaries(new HistoricalPricingSummaries.Params().Universe("DTEGn.DE")
.WithInterval(HistoricalPricingSummaries.Interval.P1D)
.WithCount(10000));
if (!response.IsSuccess)
throw new Exception($"GetSummaries error: {response.Status.ToString()}");
IsSucces is "true" but raw data shows:
{[
{
"universe": {
"ric": "DTEGn.DE"
},
"status": {
"code": "TS.Interday.UserNotPermission.70112",
"message": "User does not have permission for this universe."
}
}
]}
Best Answer
-
Hi @martin.grunwald,
Based on the many tests that I have performed against multiple data services, the general theme is that if there are issues with the universe/instrument specification, such as invalid RIC or not permissioned RIC, a valid HTTP code will be returned but will carry some sort of status/error information within the body. Invalid HTTP codes returned typically happen when invalid parameters or missing required parameters are provided.
While the Historical services presently only provides one instrument as input, many others provide multiple instruments. I believe the rationale is that if you request for a service with 30 instruments, one of which is invalid, your whole request should not be rejected. Instead, the service will provide you with valid data for 29 of them but let you know the reason why the 30th failed. The Historical service likely wants to stay consistent with this approach, especially if it changes sometime in the future to allow multiple instruments as input.
0
Answers
-
So if understand you correctly you say the behavoir is as intended. How would you sugest I find out if a request was successful or what kind of error occurred?
0 -
Yes, the behavior is as intended. The challenge is that each service unfortunately doesn't handle errors in a consistent way. Because each service may be completely different and organize their data structure responses differently, this may be one of the challenges. With the Historical pricing interface, the status block will provide errors and warnings. It does contain a code that appears to be a hierarchy of details, i.e. "TS.Interday.UserNotPermission.70112" or "TS.Intraday.Warning.95004", etc. If you want more details related to the actual service, I would open a separate ticket with the Refinitiv Helpdesk. They will reach out to the actual service team which will provide a better picture and explanation of their status codes.
0 -
Hi @martin.grunwald,
If you haven't already, you can also refer to the reference guide for the Historical Pricing endpoint: https://amers1.apps.cp.thomsonreuters.com/Apps/APIDocs/#/details/L2RhdGEvaGlzdG9yaWNhbC1wcmljaW5nL3Yx/L3ZpZXdzL2ludGVyZGF5LXN1bW1hcmllcy97dW5pdmVyc2V9/GET/README
While it won't answer every question, it does provide some explanation around how the service handles issues/errors/warnings, etc.
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.4K 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
- 559 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
- 280 Open PermID
- 45 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 717 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 中文论坛