How to get minute wise data of past 3 years of SPX
I have been exploring DSS for the past few days. I've skimmed through the REST API tutorials which use postman and have so far been successful. I am currently trying to write a python script to extract minute-wise data of the past 3 years of SPX futures and options and with the help of Article.RDP.DSS.RKD.Python.GenerateCodeUsingPostman/dss-generate-python-code-using-postman.ipynb at main · LSEG-API-Samples/Article.RDP.DSS.RKD.Python.GenerateCodeUsingPostman · GitHub and Getting a list of all RIC codes for Equity Index Options - Forum | Refinitiv Developer Community , I've managed to get some data but it is not minutewise and not that comprehensive.
Any help would be greatly appreciated.
Best Answer
-
Thank you for reaching out to us.
As far as I know, the DSS is unable to provide intraday historical data. You need to use Tick History product to extract intraday historical data.
The Tick History has the TickHistoryIntradaySummariesExtractionRequest extraction which summarizes market data into discrete time series intervals ranging from one second to one hour. You can refer to the REST API Tutorial 6: On Demand intraday bars extraction tutorial for more information.
1
Answers
-
I have implemented this, and it is returning an empty string when retrieving the data. I suspect I might have used the wrong headers. so here is a code snippet of the same.
retrieve_data_headers = {
"Prefer": "respond-async",
"Content-Type": "Accept-Encoding: gzip, deflate",
"Authorization": f"Token {dss_token_response_json['value']}"
}0 -
To download the content, the headers look like this:
It uses with the RawExtractionResults endpoint.
You can check the Notes when the extraction is completed.
For example, I don't have permission to access the .SPX RIC.
1 -
Thank you so much @Jirapongse for your timely response. I have so far been able to extract data of SPY ETF using "SPY" as the ric. However, when I try to use "0#SPY*.U" as the ric for SPY options, I get an "invalid identifier" error. Any help regarding this would be greatly appreciated.
0 -
0#SPY*.U is a chain RIC so you need to use this:
"IdentifierList": {
"@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers": [{
"Identifier": "0#SPY*.U",
"IdentifierType": "ChainRIC"
}],1
Categories
- All Categories
- 6 AHS
- 37 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
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛