Adding `limit` and pagination for `getTransactionsByAddress`

Hi,

I have been looking at the API for usage, and noticed that it’s hard to paginate with the coinbaseCloud_getTransactionsByAddress endpoint.

For example, there’s no way to limit the amount of transactions fetched, which means that the fetching strategy will be getting ~1000 every time to ensure there’s enough transactions as response.

And, there’s no clear way of paginating on exactly the next transaction. Would be great to have a way of paginating and limiting the amount of transactions returned. Thanks.

Hello @nijynot! Thank you for taking an interest in trying out Coinbase Cloud. For the details regarding your concern, we will check on this for you with our team. We will get back to you once we have more information. Keep in touch!

4 Likes

Another point, it’s not possible to paginate in the opposite direction.

Right now, it’s only possible to paginate from latest block to 0, and that direction only.

Hi @nijynot! Thank you so much for the feedback you provided. We appreciate it if you can share this in the Feedback Section of the Forum as most new features and improvements to Coinbase come directly from feedback like yours, so it’s very valuable to us. Thank you and welcome to the community!

3 Likes

Hi @nijynot, thanks for your feedback. Appreciate it!

I’m happy to share that after evaluating your ticket, our Cloud product and engineering team has made following changes:

  • We now use the ranged pagination approach, which allows users to define a “PageNumber” and a “PageSize” for paginating the results. With this approach, users are able to set the result limit and paginate on exactly the next transaction.
  • We also allow users to define a “sort” parameter to sort the results by block height in ascending or descending order.

Let us know if you have any other questions. Thanks!