i have a question regarding the public api:
is it maybe possible, that the result from trades.json are sent in the opposite order? I think it's pretty strange, that you always get the oldest orders first, and then you will need to resend that request like 100 times, always with the latest tid from the previous request. Or maybe add another parameter so you can choose the order (newest/oldest)?
is it maybe possible, that the result from trades.json are sent in the opposite order? I think it's pretty strange, that you always get the oldest orders first, and then you will need to resend that request like 100 times, always with the latest tid from the previous request. Or maybe add another parameter so you can choose the order (newest/oldest)?
bump
The behaviour is intentional. Previously we had returned all transactions within the last 7 days. With increasing transaction volume, these API calls were returning up to 1 MB per call, obviously not the most performant way. Therefore we changed it that you should provide the ID of the last transaction that you know and we return all transactions after that ID. To limit resource consumption we return only max. 1000 trades. Thus if there are more than 1000 trades between two of your API calls you will need to call the function repeatedly always with the last ID of each return. This is quite a common approach to withdrawing transaction data from sites that have large transactions.
