OHLC public method bug?
https://www.kraken.com/help/api#get-ohlc-datahttps://api.kraken.com/0/public/OHLC?pair=XBTCZEUR&interval=60&since=1381449600
api asked for data
since=1381449600returns data starting from
1413583200the param
since is ignored.
Also...
could you consider to move your api docs to github? it will allows better integration with all apps which are accessing your API. It is also well versioned. Some markets already did that.
We'll consider the github idea - thanks for the suggestion.
The other thing isn't a bug. OHLC data does not go back beyond a certain number of frames and depending on the interval it won't go back past 24 hours. The "since" value here is mainly used to received incremental updates. Choosing a longer interval will yield OHLC data going further back.
You can build your own OHLC from the trades data. Start with "since" of 0 to get trade data from the beginning.
https://api.kraken.com/0/public/Trades?pair=XXBTZEUR&since=0Then from the returned data, grab the "last" time ID (i.e. ... ,"last":"1383839436659595694"}})
and use that ID for the "since" value in the new poll:
https://api.kraken.com/0/public/Trades?pair=XXBTZEUR&since=1383839436659595694and so on until you've fetched all the trade data.
If that doesn't clear things up, let me know.
Dargo,
I'm already familiar with processing of raw tick trades to OHLC. The since param in trades is valuable as it helps to enforce data integrity, I use it every few minutes
I've asked for the method OHLC because it would allow to DIRECT usage by js charting libraries.
So regarding the OHLC method, as I understand, the since param cannot be used to get deep historical OHLC but only quite recent OHLC data?
It's a bit limitation comparing to since parameter in trades method, which obviously overloads the market API much heavier (due to the volume of rows) than OHLC data would overload.
