End Period doesnt work

Hi team, I am from the Specialist - helpdesk team and I have a client who raised a query to us and said that the "summaryTimestampLabel":"endPeriod" doesnt work on his end. Can you check? Thanks!
For context, his verbatim below:
It does not seem to work (i.e., I still get a start of period data), but I can handle this in my program.
However, what feels really annoying is that I don't get the most recent data when using any of the APIs.
I ran my code at 11:40am so I expect to get the data of 11am (Paris time) and of the preceding hours (10am, 9am, etc).
I indeed get the data of 10am, 9am, etc, but for the 11am, I get the data of 11:40am.
The end of period you mentioned would be good to fix this (if it works).
Sample code from user:
import lseg.data as lseg
lseg.open_session()
from lseg.data.content import historical_pricing
from lseg.data.content.historical_pricing import Intervals
rics = ['EUR=']
fields = ['BID']
start = py_utils.datetime_checker('2025-06-18 03:00:00')
end = py_utils.datetime_checker('2025-06-18 12:00:00')
response = historical_pricing.summaries.Definition(
universe=rics,
fields=fields,
start=start - timedelta(hours=2),
end=end - timedelta(hours=1),
interval=Intervals.HOURLY,
extended_params={"summaryTimestampLabel": "endPeriod"}
).get_data()
df = response.data.df
df.drop_duplicates(inplace=True)
df.index = df.index + timedelta(hours=1)
Answers
-
Thank you for reaching out to us.
The summaryTimestampLabel parameter controls the timestamp label in the response to be either at the start summarization period or at the end of summarization period. The parameter is available in the intraday-summaries and interday-summaries APIs and its possible values are as follows:
- startPeriod indicates that the data returned is labelled at the start of summarization period.
- endPeriod indicates that the data returned is labelled at the end of summarization period.
It is not used to get the most recent data.
The following picture compares the results when setting the summaryTimestampLabel parameter to 'startPeriod' and 'endPeriod' respectively.
With the 'startPeriod', the 1.1507 price value belongs to the 2025-06-18 11:00:00 timestamp while with the 'endPeriod', the same price (1.1507) belongs to the 2025-06-18 12:00:00.
I understand that the client would like to retrieve the recent data. You need to contact the Historical Pricing API team to verify when the recent data is available in the historical database.
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
- 687 Datastream
- 1.4K DSS
- 623 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
- 255 ETA
- 557 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
- 276 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
- 690 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
- 105 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 91 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛