Best Template for Option/Futures reference data
Hi,
I am dealing with reference data for options and futures and wanted to know, which template is the preferred one to use:
- HistoricalReferenceExtractionRequest
- TermsAndConditionsExtractionRequest
Both are covering fields I am interested in, like Expiration Date - Strike Price - Put Call Flag. This is a daily job, that requests the current data, no historical instruments.
I assume the data should be the same on both templates.
-----
So far I was only able to request data using the HistoricalReferenceExtractionRequest template.
If anyone has an example how I can for example request this reference data for the 0#SPXW*.U Chain RIC I would be very glad - I did not found any tutorial covering this asset class in the TermsAndConditionsExtractionRequest.
Kind regards,
Max
Best Answer
-
Hi @richter
The HistoricalReference provides historical reference data for a specified date range, while the TermsAndConditions provides current reference data. As you want to request current data, the TermsAndConditions should be more preferable. You can find tutorial for TermsAndConditionsExtractionRequest in User Guide for TickHistory 12.1 REST API or tutorial of DataScope Select.
Below is the sample of request.
{
"ExtractionRequest": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.TermsAndConditionsExtractionRequest",
"ContentFieldNames": [
"RIC", "Expiration Date","Strike Price", "Put Call Flag"
],
"IdentifierList": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers": [
{ "Identifier": "0#SPXW*.U", "IdentifierType": "ChainRIC" }
]
}
}
}If you still are not able to request data using TermsAndConditionsExtractionRequest, please share your request and response.
0
Answers
-
thank you for the snippet that worked like a charm!
Is it correct that TermsAndConditionsExtractionRequest (~15 seconds) runs much faster than the HistoricalReferenceExtractionRequest (~5 minutes) request?
-- Max
0 -
@richter
I have found the same result. Data of the HistoricalReference and TermsAndConditions template should be extracted from difference source. However, I cannot confirm whether this is expected extraction time for HistoricalReference. You can contact TRTH support team via ContactUs. In the product field, select Thomson Reuters Tick History v2.
0
Categories
- All Categories
- 6 AHS
- 39 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 60 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛