I’ll explain the situation. I want to request many transactions asking an indexer them. So I’ll iterate requesting every time changing the next token field of the request. I wanted to use a multithreaded approach. But of course I don’t have the next token so I cannot run the requests indipendenlty. Is there a method to precalculate the next_page token giving some specific inputs (such as the limit of the batch response)
I don’t think you can easily do that.
However, what you can do is to split the range of rounds you are interested in (that is first transaction round to last transaction round for the account) and make queries to each sub-range in different threads.
Oh ok that’s a really great idea, thanks!