Unable to resolve RIC Root

I'm trying to use the DataScope select API to extract Tick History data. I'm successfully able to make a request, however, I get the following error message in the response body:
Quota Message: ERROR: Unable to resolve RIC Root for (RIC, TRGBNBPD1)
I'm not getting any of the requested Tick History data back in the response, presumably due to this error.
The full response is as follows:
@{'@odata.context': 'https://selectapi.datascope.refinitiv.com/RestApi/v1/$metadata#RawExtractionResults/$entity', 'JobId': '0x0820f6748d8e238c', 'Notes': ['Extraction Services Version 16.1.44123 (ed92f5e3e332), Built Aug 10 2022 01:55:41\nUser ID: 9032209\nExtraction ID: 2000000435345061\nCorrelation ID: CiD/9032209/0x0000000000000000/REST API/EXT.2000000435345061\nSchedule: 0x0820f6748d8e238c (ID = 0x0000000000000000)\nInput List (1 items): (ID = 0x0820f6748d8e238c) Created: 08/15/2022 10:09:54 Last Modified: 08/15/2022 10:09:54\nReport Template (13 fields): _OnD_0x0820f6748d8e238c (ID = 0x0820f6748d9e238c) Created: 08/15/2022 10:08:51 Last Modified: 08/15/2022 10:08:51\nSchedule dispatched via message queue (0x0820f6748d8e238c), Data source identifier (C2C1A41E173A4B77BD9C1E7C70CE5650)\nSchedule Time: 08/15/2022 10:08:51\nProcessing started at 08/15/2022 10:08:51\nProcessing completed successfully at 08/15/2022 10:09:54\nExtraction finished at 08/15/2022 10:09:54 UTC, with servers: tm01n01, TRTH (58.674 secs)\nInstrument <RIC,TRGBNBPD1> expanded to 1 RIC: TRGBNBPD1.\nTotal instruments after instrument expansion = 1\n\nQuota Message: ERROR: Unable to resolve RIC Root for (RIC, TRGBNBPD1)\nManifest: #RIC,Domain,Start,End,Status,Count\nManifest: TRGBNBPD1,Market Price,2022-08-10T06:07:38.043933160Z,2022-08-11T15:49:58.488198065Z,Active,295\n']}
Many thanks for your help!
Best Answer
-
The error is related to a quota of TRTH users. Moderators in this forum are dedicated to technical API-related queries. We do not have access to user administration. This issue would best be investigated by TRTH support. Please a query to the TRTH support via MyRefinitiv.
However, for this case, I've submitted case number 11503908 on your behalf, you'll be contacted by the support team directly regarding this issue.
0
Answers
-
Thanks Raksina, I really appreciate the help.
0 -
According to the notes file, you should be able to get data.
@{'@odata.context': 'https://selectapi.datascope.refinitiv.com/RestApi/v1/$metadata#RawExtractionResults/$entity', 'JobId': '0x0820f6748d8e238c', 'Notes': ['Extraction Services Version 16.1.44123 (ed92f5e3e332), Built Aug 10 2022 01:55:41\nUser ID: 9032209\nExtraction ID: 2000000435345061\nCorrelation ID: CiD/9032209/0x0000000000000000/REST API/EXT.2000000435345061\nSchedule: 0x0820f6748d8e238c (ID = 0x0000000000000000)\nInput List (1 items): (ID = 0x0820f6748d8e238c) Created: 08/15/2022 10:09:54 Last Modified: 08/15/2022 10:09:54\nReport Template (13 fields): _OnD_0x0820f6748d8e238c (ID = 0x0820f6748d9e238c) Created: 08/15/2022 10:08:51 Last Modified: 08/15/2022 10:08:51\nSchedule dispatched via message queue (0x0820f6748d8e238c), Data source identifier (C2C1A41E173A4B77BD9C1E7C70CE5650)\nSchedule Time: 08/15/2022 10:08:51\nProcessing started at 08/15/2022 10:08:51\nProcessing completed successfully at 08/15/2022 10:09:54\nExtraction finished at 08/15/2022 10:09:54 UTC, with servers: tm01n01, TRTH (58.674 secs)\nInstrument <RIC,TRGBNBPD1> expanded to 1 RIC: TRGBNBPD1.\nTotal instruments after instrument expansion = 1\n\nQuota Message: ERROR: Unable to resolve RIC Root for (RIC, TRGBNBPD1)\nManifest: #RIC,Domain,Start,End,Status,Count\nManifest: TRGBNBPD1,Market Price,2022-08-10T06:07:38.043933160Z,2022-08-11T15:49:58.488198065Z,Active,295\n']}
You should see 295 rows of data from 2022-08-10T06:07:38.043933160Z to 2022-08-11T15:49:58.488198065Z.
To get the data, you need to use this https://selectapi.datascope.refinitiv.com/RestApi/v1/Extractions/RawExtractionResults('0x0820f6748d8e238c')/$value endpoint. 0x0820f6748d8e238c is the JobId.
0 -
Hi @michael.golden ,
I have learned that the case is resolved with the following answer:
API Codes shared with client directly
Could you please accept if the issue is resolved, otherwise post another question if the issue still exists.
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
- 716 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 中文论坛