Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inconsistency with timezones #241

Open
Scrashdemix opened this issue Nov 3, 2022 · 0 comments
Open

Inconsistency with timezones #241

Scrashdemix opened this issue Nov 3, 2022 · 0 comments

Comments

@Scrashdemix
Copy link

Scrashdemix commented Nov 3, 2022

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:

  1. Request a calendar object from the api (Link) and look at the response.
  2. 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
grafik
The requested calendar object seem to indicate that the UTC-4 timezone is used.

grafik
grafik
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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant