Allow transfers_v2 endpoint to be sorted

The transfers_v2 api is lacking the ability to sort based on blockheight similar to the way transactions_v2 can with block-signed-at-asc=true. This makes it hard to ensure that you receive all transfers for an address like what you can do with transactions.

Example of how it could look:
https://api.covalenthq.com/v1/1/address/0x25f2226b597e8f9514b3f68f00f494cf4f286491/transfers_v2/?&contract-address=0x7fc66500c84a76ad7e9c93437bfc5ac33e2ddae9&block-signed-at-asc=true&page-number=0&starting-block=13500000

Thanks!

1 Like

Thanks for the feedback!
It can be done using Primer. We are creating a general set of operators that can be used for it
Please refer https://www.covalenthq.com/docs/tools/primer-query