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

alignmentTimezone issue #45

Open
IFFranciscoME opened this issue Mar 28, 2017 · 1 comment
Open

alignmentTimezone issue #45

IFFranciscoME opened this issue Mar 28, 2017 · 1 comment

Comments

@IFFranciscoME
Copy link

When one tries to retrieve historical prices and the parameter: alignmentTimezone is set to wherever admitted value, the resulting time stamp at the response is always GMT. I have used a this python wrapper and another R wrapper for your REST API and even on the web url, the result is the same, no matter what alignmentTimezone is set, the result is GMT. What i am missing ?

Thanks for your technology and support. Great broker you are.

@dmpettyp
Copy link

To be clear, you are using the v1 REST API right? Most of my knowledge is with the v3 API but should be applicable in both cases.

Setting the alignmentTimezone will always result in GMT timestamps, but the alignment (start time) of the candles should change appropriately.

For example, asking for GMT aligned daily candles might yield:

1490115600 mid 1.08154 1.0825 1.0776 1.0806 41243
1490202000 mid 1.08061 1.08166 1.0768 1.07876 38884

Here, 1490115600 Is equivalent to: 03/21/2017 @ 5:00pm (UTC)

Asking for EST aligned daily candles might yield:

1490047200 mid 1.07373 1.08194 1.0719 1.08069 44632
1490133600 mid 1.08077 1.0825 1.0776 1.07931 40430

Here, 1490047200 Is equivalent to: 03/20/2017 @ 10:00pm (UTC) which is 5:00pm EST

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

2 participants