Jason Posted June 24, 2023 Report Share Posted June 24, 2023 I am experimenting with the API access and it seems that it's returning the candle data with a time offset and it's not obvious to me why. This is the command I am using through the WSTester: { "cmd": "getCandles", "reqID": "1234", "startDate": "2023-06-23", "candleSize": "2", "regHoursOnly": "true", "sym": "AMD" } The data for the first candle is: { "t": "2023-06-23T13:30:00.000", "o": 109.31, "h": 110.42, "l": 109.13, "c": 110.27, "v": 1436842.0 } This data is correct for the first 2m candle as shown through the MT UI chart but obviously does not correspond to the 2m candle at 1:30pm. I have looked into the ISO date and time format being used without any clarification. Quote Link to comment Share on other sites More sharing options...
Mike Medved Posted June 24, 2023 Report Share Posted June 24, 2023 2023-06-23T13:30:00.000 - that's UTC time. Currently 4 hours difference from Eastern. So that would be 9:30 Eastern. Quote Link to comment Share on other sites More sharing options...
Jason Posted June 24, 2023 Author Report Share Posted June 24, 2023 Ah, thank you. For some reason was thinking the time was represented according to my system settings. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.