I’ve discovered an irritating bug with the candles endpoint.
It’s now mandatory to specify the start and end unix timestamp. With Coinbase Pro if you didn’t specify it you just got the last 300 entries. There is validation on the endpoint now that prevents you from specifying a time frame larger than 300 x granularity.
The ONE_MINUTE, FIVE_MINUTE, and ONE_DAY are missing entries.
For example, right now for BTC-GBP you can only get the last 128 minutes and 256 five minutes. You can’t increase the start and end to make sure you get the max 300 entries. It will throw an error to say the time frame is too long even though you are under the 300 limit.
“start and end argument is invalid - number of candles requested should be less than 300”
For the ONE_DAY it’s slightly different because it won’t give you 300 days. It gives you 299 because you are on the current day.
It should give you 300 entries regardless. This wasn’t a great change from Coinbase Pro. Those start and end should not be mandatory and the validation should be on getting 300 entries back, not based on the timeframe.
If the devs are reading these forums… please fix this.