Immediate extraction using existing Instrument Lists and Report Templates using REST APIs

From the tutorials, I see that it is possible to perform a direct EOD data fetch sending the required fields and identifier lists. Also, it describes how to schedule an extraction through the REST APIs using existing instrument lists and report templates. But is it possible to use existing instrument lists and report templates to make a direct extraction call? That is, be able to get the data directly from the request, rather than an extraction file be generated. If so, could someone point to an example?
Thanks!
Best Answer
-
The easiest way to retrieve data directly and immediately is by using the OnDemand API calls.
You can refer to an existing instrument list in an OnDemand extraction API call, but not to an existing report template (but that is not really required).
Instrument list
If you are not using the .Net SDK, you can simply follow the explanations in the REST API Tutorial 9. We do not deliver downloadable sample code for this, but you do not really need any as it is just a very simple modification of the OnDemand extraction. You can easily apply the described change to the OnDemand extractions in all the other REST API Tutorials.
Report template
An OnDemand extraction defines the report template by the data type defined in the extraction request itself, so you cannot refer to a custom one you predefined and saved on the server.
All you really need to do is specify the content field names in the extraction request, this is quite easy.
0
Answers
-
You can use below example for immediate scheduling,
{
"Name":
"example-eod1",
"TimeZone": "Central Standard Time",
"Recurrence": {
"@odata.type":
"#ThomsonReuters.Dss.Api.Extractions.Schedules.SingleRecurrence",
"ExtractionDateTime":
"2017-03-30T01:31:16.463+05:30","IsImmediate":
true},
"Trigger": {
"@odata.type":
"#ThomsonReuters.Dss.Api.Extractions.Schedules.ImmediateTrigger",
"LimitReportToTodaysData": true},
"ListId": "0x05a932aa203b3036",
"ReportTemplateId": "0x0588adc24c6b2f86"}
0 -
Hi Nityanand,
Thanks for the reply!
But what you suggest would only create a schedule to be executed right? Which would in turn produce an extraction file. And it would require more REST calls to then fetch the contents of this file. Would it be possible to get the response in my initial call itself?
0 -
Thanks Christiaan, that is what I wanted to know.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 37 Alpha
- 167 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 713 Datastream
- 1.5K DSS
- 639 Eikon COM
- 5.3K Eikon Data APIs
- 20 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 12 Trading API
- 3K Elektron
- 1.5K EMA
- 260 ETA
- 574 WebSocket API
- 42 FX Venues
- 16 FX Market Data
- 2 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 26 Messenger Bot
- 5 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 285 Open PermID
- 47 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 25 RDMS
- 2.3K Refinitiv Data Platform
- 20 CFS Bulk File/TM3
- 939 Refinitiv Data Platform Libraries
- 6 LSEG Due Diligence
- 1 LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 12 World-Check Customer Risk Screener
- World-Check On Demand
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 46 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
- 126 Open DACS
- 1.1K RFA
- 108 UPA
- 197 TREP Infrastructure
- 232 TRKD
- 925 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 107 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛