We currently use Get Content Versions and expand by
content to get the history of a document, including the content.
The version 2 of the REST API does not allow expanding the content. In this case, if we want to show 200 entries of the history of a document, we need to make 200 parallel requests to the get content endpoint.
This looks like error-prone. We need to manage the errors for all the requests to retry them if they fail. Also, we wonder if this can hit any kind of rate limiting in the API.
Will be any other way to get the content of the versions in v2 REST API?
Is making hundreds of parallel request acceptable for the RESP API?