-
Notifications
You must be signed in to change notification settings - Fork 236
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
Adding the 'since: 0' parameter to the query_public
function doesn't give any additional data
#44
Comments
query_public
function doesn't give any additional dataquery_public
function doesn't give any additional data
Does the Update: From what I've seen, Kraken's |
Kraken's API docs on
And in the result there'll be:
The documentation explicitly references the EDIT: The only "sane" way to use |
As to the original issue:
Have you estimated the size of that response?.. With the default one-minute interval, and considering that the ETH/XBT pair was opened on 2015-08-08 (about two years ago), that'd be around With an (optimistic) size of 100 bytes per entry, that's about 100.25 MiB of response data. |
See Edit the |
Based on a initial testing, the 'since' with 'timestamp' has worked for me. What I've found weird is that the timestamp must be in local timezone, and the 'time' |
Thanks guys, that was a great help! I did not understand that it has to be a local timezone in the Unix timestamp. Also, thx @veox for the example! :) |
Versions
What are you trying to achieve?
I am trying to pull the entire historic data of all OHCL using the query_public keyword, to get all the trades from the beginning of time:
What do you expect to happen?
I expect to get the entire OHCL data from the beginning of time.
What happens instead?
I get the same OHCL data as if I would not try to add the 'since' parameter. In short, the result is equivalent to
such that only a frame of the newest 700 samples is returned
The text was updated successfully, but these errors were encountered: