GetIntradayTimeSeries_5: error handling
It seems that the historical series requests in RKD do not return any error codes in response and every error condition should be handled as an exception: FaultException, CommunicationException etc,
Looking into the exception's FaultReason produces the text like ''Backend error: 'NOT_AUTHORIZED'".
Is there an exhaustive list of "reasons" or at least the set of fault categories that can be matched in the FaultReason.text or Exception.Message for the lack of a better alternative?
Best Answer
-
Hi Patrick,
Not authorized would indicate your RKD API user ID is not permission to get the data for time series service and it needs to be permission to fetch the data subject to subscription of relevant packages.
Other type of erros can include -
Access_denied
unable to find company ID
Not_authorized
Thanks
Muzammil Shareif
0
Answers
-
Hi @PatrickZ
Additionally, the list of common errors is as follows:
Time Series Service
Reason: when Invalid Symbol/RIC is used in the request.
- Error Message: ReutersKnowledge.Web.Services.RkapiException: Invalid RIC specified. Backend error code 'ERR_NOSUCHRIC'
Reasons: RIC is not entitled/ permissioned.
- Error Message: ReutersKnowledge.Web.Services.RkapiException: Backend error: 'NOT_AUTHORIZED' .
Token Management Service
Reason: When invalid credentials are passed in the request.
- Error Message: ReutersKnowledge.Web.Services.RkapiException: Invalid user name or password.
All RKD Services
Reason: Throttling Error
- Error Message: ReutersKnowledge.Web.Services.RkapiException: The maximum number of requests for your application ID, XX per second, has been exceeded. Service retrieval will be re-enabled once your usage drops below the threshold
Hope this helps.
0 -
Thanks! It gives some info, but I am looking for the documented and exhaustive list.
Unfortunately, unlike the Quote List service where there is the StatusMsg enum and the value is returned in the response, in the Time Series, the error handling had to be done using the exceptions.
The one that you mentioned are obvious, but there should be something documented for the backend....0 -
Hello @PatrickZ
I highly recommend you contact the RKD support team directly to help you with the document/error list in more detail. You can submit the ticket to the team via the https://my.refinitiv.com/content/mytr/en/productsupport.html website.
Please choose the "Refinitiv Knowledge Direct API" product.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 37 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
- 13 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 5 Trading API
- 2.9K Elektron
- 1.4K EMA
- 256 ETA
- 563 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
- 283 Open PermID
- 47 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 755 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 中文论坛