Refinitiv.Data .NET library passes DateTime in incorrect format to interday-summaries endpoint

GoGoGroundhog

This is referring to my recent report:

Erratic response for interday history request (start date sometimes not included) - LSEG Developer Community

I got an answer from the Historical Pricing API Support Team:

After investigating the issue, we found that the problem arises because the request you are submitting is using an incorrect date format for start/end parameters – the correct date format is  yyyy-mm-dd ex. 2024-12-03. The API is currently unable to process the data correctly due to this format mismatch.

We are using the Refinitiv.Data .NET library which does the call under the hood. We are passing in a DateTime to Refinitiv.Data.Content.HistoricalPricing.SummariesDefinition.Start(DateTime date) method. Apparently this translates the given DateTime object into an incompatible string representation.

Jirapongse

@GoGoGroundhog

Thank you for reaching out to us.

I found that the Start and End parameters also accept a string.

Therefore, you can connect the DateTime to a compatible date string representation.