Eikon Python Data API migration to lseg-data. get_history() request empty result

Hello,
The second problem with get_history(): sometimes, for some requests the function returns nothing. Empty DataFrame. There is no way to get any details on what happened.
The behavior is not consistent. Right now I see an empty DataFrame for this request:
dataFrame = ld.get_history( universe= ["INDJ25"], fields=['ACVOL_UNS', 'OPEN_PRC', 'TRDPRC_1', 'HIGH_1', 'LOW_1'], start="2025-04-08", end="2025-04-09", interval="1D", header_type=ld.HeaderType.NAME)
The logs:
HTTP Request id 2
url = http://localhost:9000/api/rdp/data/historical-pricing/v1/views/interday-summaries/INDJ25?interval=P1D&start=2025-04-08T00%3A00%3A00.000000000Z&end=2025-04-09T00%3A00%3A00.000000000Z&fields=ACVOL_UNS%2COPEN_PRC%2CTRDPRC_1%2CHIGH_1%2CLOW_1%2CDATE
HTTP Response id 2
status_code = 200
text = [{"universe":{"ric":"INDJ25"},"interval":"P1D","summaryTimestampLabel":"endPeriod","adjustments":["exchangeCorrection","manualCorrection","CCH","CRE","RTS","RPO"],"defaultPricingField":"SETTLE","qos":{"timeliness":"delayed"},"headers":[{"name":"DATE","type":"string"},{"name":"TRDPRC_1","type":"number","decimalChar":"."},{"name":"OPEN_PRC","type":"number","decimalChar":"."},{"name":"HIGH_1","type":"number","decimalChar":"."},{"name":"LOW_1","type":"number","decimalChar":"."},{"name":"ACVOL_UNS","type":"number","decimalChar":"."}],"data":[]}]
print(dataFrame) returns:
Empty DataFrame
Columns: []
Index: []
First question is: why no data in http response?
Second: why dataFrame is empty? How can I recognize that the response was good or bad if nothing is returned?
The example of "bad" request : if I include 'VWAP' in the requested fields, the log shows
"status":{"code":"TSCC.QS.UserRequestError.90006","message":"The universe does not support the following fields: [VWAP]."}}
but the dataFrame is empty. And I don't see a way to extract this info.
Answers
-
Thank you for reaching out to us.
It may relate to this question.
Please try this one.
response1 = historical_pricing.summaries.Definition( "INDJ25", interval=Intervals.DAILY, start = '2025-04-09', end = '2025-04-10', fields=['ACVOL_UNS', 'OPEN_PRC', 'TRDPRC_1', 'HIGH_1', 'LOW_1'], extended_params={"summaryTimestampLabel":"startPeriod"} ).get_data() response1.data.df
0 -
Thank you for your response. I will test this more and let you know. I created 2 different posts because I saw this as 2 separate problems. I will post an update later.
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
- 685 Datastream
- 1.4K DSS
- 615 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 252 ETA
- 556 WebSocket API
- 38 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 652 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
- 104 UPA
- 193 TREP Infrastructure
- 228 TRKD
- 917 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛