Hello @Rilecs
I can replicate the same behavior using https://community.developers.lseg.com/home/leaving?allowTrusted=1&target=https%3A%2F%2Fdevelopers.lseg.com%2Fen%2Fapi-catalog%2Flseg-data-platform%2Flseg-data-library-for-python version 2.1.1 and Desktop (Workspace) session. When I enable the library log file on the lseg-data.config.json file, log file shows that the Workspace backend server sent data from 2026-06-02 to 2026-06-10 to the library.
Request id 2 url = http://localhost:9001/api/rdp/data/historical-pricing/v1/views/interday-summaries/LCOc1?interval=P1D &start=2026-06-01T00%3A00%3A00.000000000Z&end=2026-06-10T00%3A00%3A00.000000000Z &fields=SETTLE%2CDATE method = GET headers = {'request-timeout': '20', 'x-tr-applicationid': 'LD-PYTHON-LIB', 'Authorization': 'Bearer token'} [2026-06-11T10:47:46.855657+07:00] - [sessions.desktop.workspace.0] - [DEBUG] - [25748 - HistoricalRequestThread_0] - [http_service] - [request] - HTTP Response id 2 status_code = 200 text = [{"universe":{"ric":"LCOc1"},"interval":"P1D","summaryTimestampLabel":"endPeriod","adjustments": ["exchangeCorrection","manualCorrection","CCH","CRE","RTS","RPO"],"defaultPricingField":"SETTLE","headers" :[{"name":"DATE","type":"string"},{"name":"SETTLE","type":"number","decimalChar":"."}],"data":[["2026-06-10",93.1], ["2026-06-09",91.45], ["2026-06-08",94.25], ["2026-06-05",93.09], ["2026-06-04",95.03], ["2026-06-03",97.81], ["2026-06-02",96]],"meta":{"blendingEntry":{"headers":[{"name":"DATE","type":"string"} ,{"name":"SETTLE","type":"number","decimalChar":"."}],"data":[["2026-06-10",93.1]]}}}]
However, if I change the code to request data from 2026-05-31 to 2026-06-10, it returns 2026-06-01 data. Please ask the client to try it.
@Rilecs
I think this is because the API adds time components to the start and end dates.
http://localhost:9001/api/rdp/data/historical-pricing/v1/views/interday-summaries/LCOc1?interval=P1D &start=2026-06-01T00%3A00%3A00.000000000Z&end=2026-06-10T00%3A00%3A00.000000000Z
I will contact the product team to verify this.
Hi @Jirapongse do we have any update on this with the product team? Thank you!
I am still waiting for the response from the product team.
Currently, please use the workaround mentioned by my colleague.
Hi @Jirapongse , please see response from the client,
I have made my code deal with the shifted dates (e.g. missing start date). Before you guys correct it, let me know. I need to rework the code. At this moment, it might be more convenient if this is not corrected.
Please advise if this will be corrected so we can update the client. Thank you!
I’ve received an update from the product team confirming that the issue will be fixed; however, the release date has not yet been defined.
