Please can you explain why there is a lag on receiving EIA stats data via a script i have written?

Hi team, I am posting on behalf of an external client for the query below, please help and prioritize:
Please can you explain why there is a lag on receiving EIA stats data via a script i have written using the appkey?
from lseg.data.content import historical_pricing as hp
from datetime import date
import os
crude_rics = ["C-STK-T-EIA"]
2. Date rangestart_date = "2020-01-01"
end_date = str(date.today())
response = hp.summaries.Definition(
universe=crude_rics,
interval=hp.Intervals.WEEKLY,
start=start_date,
end=end_date
).get_data()
raw_df = response.data.df
print("Latest date returned:", raw_df.index.max())
print("Today's date:", date.today())
comm_last_df = raw_df[["COMM_LAST"]].copy()
comm_last_df.columns = ["TotalCrude"]
os.makedirs("../data", exist_ok=True)
comm_last_df.to_csv("../data/crude_total_stocks.csv")
print("Saved:", os.path.exists("../data/crude_total_stocks.csv"))
I can confirm that there should be values for 1st of August but it seems that the script above pulls a week late.
Answers
-
Thank you for reaching out to us.
Currently, I could retrieve the data properly.
The library retrieves data from the Historical Pricing API. You can verify this issue by running the following formula in the LSEG Workspace Excel or contacting the Historical Pricing API support team directly when the problem occurred.
=@RDP .HistoricalPricing("C-STK-T-EIA","COMM_LAST","START:01-Jan-2020 END:07-Aug-2025 INTERVAL:P1W SOURCE:RFV",,"CH:Fd RH:Timestamp",B2)
0 -
Thanks for the response. I can see on excel as well that this is working fine. But it looks like the script of the client doesn't pull the same dates.
I have checked the entitlements and it seems good.
0 -
Currently, the API works fine too.
This issue is similar to the case (14802400).
0 -
Here's what the client had mentioned:
"Thanks for your help. My script worked by 17.20 when I checked again. The issue was that it didn't work at 15.30 (UK time) which is when I need it, so that I have live information for analysis.
So if there is a fault in my script that means there is a lag from 15.30 to 17.20 that you can spot that means I am not getting it instantaneously that would be great. Or is this due to my permissions? For context using a similar script and trying from the EIA website directly the week before also presented with a lag. Is that a nuance of using APIs?"
0 -
You need to check with the Historical Pricing API team when the data was released.
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
- 702 Datastream
- 1.5K DSS
- 633 Eikon COM
- 5.2K Eikon Data APIs
- 14 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 6 Trading API
- 2.9K Elektron
- 1.5K EMA
- 257 ETA
- 566 WebSocket API
- 40 FX Venues
- 16 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
- 283 Open PermID
- 47 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 24 RDMS
- 2.1K Refinitiv Data Platform
- 823 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
- 122 Open DACS
- 1.1K RFA
- 107 UPA
- 195 TREP Infrastructure
- 232 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 100 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛