You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
There seem to be an inconsistency concerning timezones. Different parts of the API apparently use different timezones when using timestamps.
To Reproduce
Steps to reproduce the behavior:
Request a calendar object from the api (Link) and look at the response.
Request market data and compare the timestamps (and there respective price values) of the response with market data from a third source (in my case Tradingview).
Expected behavior
Both responses should use the same timezone for the timestamps of their response. As you see below, apparently they don't.
Screenshots
The requested calendar object seem to indicate that the UTC-4 timezone is used.
These are charts for symbol "QQQ" on 2nd Nov 2022. Comparing the requested market data and the data from tradingview (which in my case uses UTC +1), it seems like the market data from the Alpaca API uses timestamp from timezone UTC +0. Is that correct or am i missing something?
The text was updated successfully, but these errors were encountered:
Describe the bug
There seem to be an inconsistency concerning timezones. Different parts of the API apparently use different timezones when using timestamps.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Both responses should use the same timezone for the timestamps of their response. As you see below, apparently they don't.
Screenshots
The requested calendar object seem to indicate that the UTC-4 timezone is used.
These are charts for symbol "QQQ" on 2nd Nov 2022. Comparing the requested market data and the data from tradingview (which in my case uses UTC +1), it seems like the market data from the Alpaca API uses timestamp from timezone UTC +0. Is that correct or am i missing something?
The text was updated successfully, but these errors were encountered: